Fix HMR issue after patching the client module #43819
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Follow-up to #43778, this PR implements the logic of adding a timestamp query to all client module reference's IDs. Note that this only applies to flight renders during dev, which only affects HMR.
The reason of changing the module ID for hot reloading is, after changing a client component to a server component, the module is completely removed in the client chunk. And Webpack disposes it along with all the React refresh registered callbacks. And when changing it back to a server component, a new module instance is generated and loaded by Webpack, but the Flight client still holds the reference to the old module instance. This is basically a way to force flight to reload the modules from Webpack.
NEXT-30
Bug
fixes #number
contributing.md
Feature
fixes #number
contributing.md
Documentation / Examples
pnpm build && pnpm lint