You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Should be backend issue.
Only happen when using Node.js v14/v15.
Only happen when the build take time that about half second or more.
Only happen when development mode.
No issue when using other version of Node.js.
No issue when production and static export.
No response when routing to some page that not yet built by hot-reload server.
The .js file will keep waiting response.
But Next.js console shown
Then the url will response normally.
But when you back to the app,
The page still unable to reach without refresh.
So I need keep refresh many times to test some simple things.
Or downgrade to Node.js v12.
To Reproduce
I'm still making a repo that can 100% reproduce this issue,
But it is hard,
Coz this issue happen so randomly,
If the bundle size too small, it can't happen.
Any way,
Here are some screen record,
Hope helpful.
No response
When .js keeping no response and keep clicking the link to that page.
Keep no response after refresh
Some case, refresh is useless.
Click another link to make it work
Links
> A: Some link no yet build since server boot up
> B: The link you want to got to
Click A link first
Click B link
When B link will work
But A link will still no work
(If you want A link work, refresh and click B link first)
Expected behavior
The bundle .js file should response when built.
System information
OS: Any
Browser: Any
Version of Next.js: > 9.5.0
Version of Node.js: v14 / v15
Additional context
Remember!
All working when using Node.js v12.
All working when production and static export even if Node.js v14/v15.
Any thing and any code is working well.
I hope the above information is helpful.
Feel free to ask me for more information.
Thanks.
The text was updated successfully, but these errors were encountered:
This issue has been automatically locked due to no recent activity. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you.
vercel
locked as resolved and limited conversation to collaborators
Jan 27, 2022
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Bug report
Describe the bug
Should be backend issue.
Only happen when using Node.js v14/v15.
Only happen when the build take time that about half second or more.
Only happen when development mode.
No issue when using other version of Node.js.
No issue when production and static export.
No response when routing to some page that not yet built by hot-reload server.
The
.js
file will keep waiting response.But Next.js console shown
Then when you type the
.js
url of the issued page into browser on new tab,It still no response and waiting response.
After waiting about 1min,
Next.js console shown again
Then the url will response normally.
But when you back to the app,
The page still unable to reach without refresh.
So I need keep refresh many times to test some simple things.
Or downgrade to Node.js v12.
To Reproduce
I'm still making a repo that can 100% reproduce this issue,
But it is hard,
Coz this issue happen so randomly,
If the bundle size too small, it can't happen.
Any way,
Here are some screen record,
Hope helpful.
No response
When
![1_not-work1](https://user-images.githubusercontent.com/14261588/98162473-5f19be00-1f1c-11eb-86b6-a199f43d740b.gif)
.js
keeping no response and keep clicking the link to that page.Keep no response after refresh
Some case, refresh is useless.
![2_not-work2](https://user-images.githubusercontent.com/14261588/98162778-d2233480-1f1c-11eb-8171-e924e3dae7f7.gif)
Click another link to make it work
(If you want A link work, refresh and click B link first)
Expected behavior
The bundle
.js
file should response when built.System information
Additional context
Remember!
All working when using Node.js v12.
All working when production and static export even if Node.js v14/v15.
Any thing and any code is working well.
I hope the above information is helpful.
Feel free to ask me for more information.
Thanks.
The text was updated successfully, but these errors were encountered: