Navigation to another page that not yet built the full page reload invoked because of HMR with messages like:
[HMR] The following modules couldn't be hot updated: (Full reload needed)
This is usually because the modules which have changed (and their parents) do not know how to hot reload themselves. See https://webpack.js.org/concepts/hot-module-replacement/ for more details.
[HMR] - ./packages/openland-api/MyOrganizationsQuery.ts
[HMR] - ./packages/openland-x-graphql/graphqlCompose.tsx
[HMR] - ./packages/openland-x-graphql/typed.ts
[HMR] - ./packages/openland-web/api/withOrganization.ts
VM6892 main.js:35768 [HMR] Reloading page
This messages are about dependencies of current page, not the one i tried to navigate. For sure this files wasn't changed.
My setup is a little bit unusual:
page.ts|tsxIt should not refresh current page since nothing was changed.
Please provide a full reproduction, preferably a minimal app in a GitHub repository. It's impossible to debug this without it 馃檹
I'm seeing this as well and it's even more frustrating as it doesn't actually list any modules, just says "undefined" like so:
[HMR] The following modules couldn't be hot updated: (Full reload needed)
This is usually because the modules which have changed (and their parents) do not know how to hot reload themselves. See https://webpack.js.org/concepts/hot-module-replacement/ for more details.
[HMR] - undefined
[HMR] Reloading page
Trying to build up a standalone repro case to narrow it down, but haven't been able to so far. Working on it.
I was able to reproduce my case above once I added the with-polyfills example code.
After removing everything else from my code, the method recommended in the with-polyfills example alone was enough to trigger the message and reload behavior for me.
@timneutkens there is small issue that seems related:
A webpackHotUpdate is not defined error is thrown (reproducible with the with-polyfills example using Next.js canary)

During development this doesn't seem to be an issue, but if i want to run my tests in Cypress it becomes a problem.
Most helpful comment
I was able to reproduce my case above once I added the with-polyfills example code.
After removing everything else from my code, the method recommended in the
with-polyfillsexample alone was enough to trigger the message and reload behavior for me.