next.js

b168c37c - Fix chunk hash logic in hot-reloader for server components (#43778)

Fix chunk hash logic in hot-reloader for server components (#43778) 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, so `serverOnlyChanges` 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](https://vercel.slack.com/archives/C035J346QQL/p1670343453333079). NEX-30 ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Feature - [ ] Implements an existing feature request or RFC. Make sure the feature request has been accepted for implementation before opening a PR. - [ ] Related issues linked using `fixes #number` - [ ] [e2e](https://github.com/vercel/next.js/blob/canary/contributing/core/testing.md#writing-tests-for-nextjs) tests added - [ ] Documentation added - [ ] Telemetry added. In case of a feature if it's used or not. - [ ] Errors have a helpful link attached, see [`contributing.md`](https://github.com/vercel/next.js/blob/canary/contributing.md) ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm build && pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)