Fix chunk hash logic in hot-reloader for server components #43778
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.
Previously we were assuming that
serverOnlyChanges
is the same as "server component changes". However that's not always true, as one can change a component from server component to client component, or vice versa, where the change affects both server and client builds, soserverOnlyChanges
will be empty.This PR fixes the logic by strictly hashing and comparing modules in the server layer. Note that I intentionally skipped the test as this fix isn't complete.
NEX-30
Bug
fixes #number
contributing.md
Feature
fixes #number
contributing.md
Documentation / Examples
pnpm build && pnpm lint