-
Notifications
You must be signed in to change notification settings - Fork 26.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Hot Reload Full Refresh in v13.4.8 #53614
Comments
I'm seeing this too. Editing my header and footer components which are children of |
I also went version by version and found out that it was definitely introduced in this version. I debugged the hot-reloader server and this is where we're telling the client to reload the page: This is not new, but the client only recently started listening to that message and reloading the page. @huozhi is this something you could maybe take a look at? |
From version of 13.4.8 I have this behaviour too and is it a little anoing. If I make some changes on dialog componet and in some tabs, I must go all again. |
We cannot recreate the issue with the provided information. Please add a reproduction in order for us to be able to investigate. Why was this issue marked with the
|
@huozhi I added a repo link with a reproduction example |
@huozhi I'm happy to supply a repo privately if it's helpful. |
Hey all, I noticed this several weeks ago and thought I was losing my mind. I found this by creating a new next app: If you edit anything within That being said, if there is content rendered through something that is not |
### What When you only have `pages/` folder and custom `_app.js`, editing the `_app.js` file when unexpectedly lead to full page reload. This is because the `pages/_app` chunk is included into `pages/_document` chunk as they all pass through the `next-route-loader` which forms the router module and other userland modules including `/_app` and `/_document`. That leads to a change: whenever you modify `_app.js`, chunk hash of `/_document` will always be updated as it's built as a new chunk. Found this difference by looking at the document chunk with nextjs in early 13.4.x releases. ### How We'll check at the entries creation point to filter out `/_app` and `/_document` so that we won't have them both bundled for `_document` chunk. Then when we won't trigger the hmr path to reload the page since _document chunk hash is updated. Closes NEXT-1568 Fixes #53614
This closed issue has been automatically locked because it had no new activity for 2 weeks. If you are running into a similar issue, please create a new issue with the steps to reproduce. Thank you. |
Verify canary release
Provide environment information
Which area(s) of Next.js are affected? (leave empty if unsure)
No response
Link to the code that reproduces this issue or a replay of the bug
https://github.com/frankfka/nextjs-full-refresh-bug
To Reproduce
See README in https://github.com/frankfka/nextjs-full-refresh-bug
Describe the Bug
We noticed in our production app that an upgrade from v13.4.7 -> v13.4.8 breaks hot reload in our dialog components (we use Radix Dialogs). Hot reload still works in normal pages, but will trigger a full refresh if a dialog component is edited.
I see a number of updates to hot reload in 13.4.8, perhaps one of them could have triggered this change?
Expected Behavior
Hot reload works when editing dialog components
Which browser are you using? (if relevant)
No response
How are you deploying your application? (if relevant)
No response
NEXT-1568
The text was updated successfully, but these errors were encountered: