Ignore serverComponentChanges in pages (#41464)
Slightly different version of #41020 where it does not end up being an unknown event. ## Bug - [ ] Related issues linked using `fixes #number` - [ ] Integration tests added - [ ] Errors have a helpful link attached, see `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` - [ ] Integration 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` ## Documentation / Examples - [ ] Make sure the linting passes by running `pnpm lint` - [ ] The "examples guidelines" are followed from [our contributing doc](https://github.com/vercel/next.js/blob/canary/contributing/examples/adding-examples.md)
This commit is contained in:
parent
7c2fd34510
commit
7be2ef0fcf
1 changed files with 4 additions and 0 deletions
|
@ -260,6 +260,10 @@ function processMessage(e) {
|
|||
)
|
||||
return handleSuccess()
|
||||
}
|
||||
case 'serverComponentChanges': {
|
||||
// Server component changes don't apply to `pages`.
|
||||
return
|
||||
}
|
||||
default: {
|
||||
if (customHmrEventHandler) {
|
||||
customHmrEventHandler(obj)
|
||||
|
|
Loading…
Reference in a new issue