[v3b1] "Full reload needed" error
See original GitHub issueI must be fundamentally misunderstanding how this is supposed to work. I have pared down my app to the bare minimum and it is still refusing to reload my component. My best guess is that either react-router or react-redux is breaking the chain of knowledge of how to reload somehow.
I have created a repo demonstrating my problem.
https://github.com/erikras/react-hot-loader-problem
Update: I have removed react-router and react-redux from the project and it still happens. My config must be broken.
Any help would be most appreciated. Cheers.
Issue Analytics
- State:
- Created 7 years ago
- Reactions:7
- Comments:15 (4 by maintainers)
Top Results From Across the Web
[HMR] Cannot find update (Full reload needed) #135 - GitHub
The error output is below: [HMR] Cannot find update (Full reload needed) [HMR] (Probably because of restarting the server) [HMR] Reloading ...
Read more >The following modules couldn't be hot updated: (Full reload ...
This module is only concerned with the mechanisms to connect a browser client to a webpack server & receive updates. It will subscribe...
Read more >Fixing “The following modules couldn't be hot updated”, “Full ...
I wrote a small React application to test hot loading components using webpack-hotmiddleware, and received the following error:
Read more >Webpack 5 Full Project Setup - YouTube
We'll be covering a ton of common functionalities needed in a Webpack ... React Fast Refresh in Webpack: the new hot module loading...
Read more >Hot Module Replacement - webpack
Retain application state which is lost during a full reload. ... In addition to normal assets, the compiler needs to emit an "update"...
Read more >
Top Related Medium Post
No results found
Top Related StackOverflow Question
No results found
Troubleshoot Live Code
Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free
Top Related Reddit Thread
No results found
Top Related Hackernoon Post
No results found
Top Related Tweet
No results found
Top Related Dev.to Post
No results found
Top Related Hashnode Post
No results found

UPDATE 2: I fixed it.
The problem was with my
module.hot.acceptreloads. I forgot to add.defaultafter the required modules.Thanks @erikras, you served as my Debug Rubber Duck today 😃
@gaearon was right of course 😁
The fix in my case was related to react-router. Passing
routesin as a prop to<Root />breaks HMR, but importing them directly intoRoot.jsworks.Any idea why? Routing was working as expected in the former version, and I assumed the output either way would be the same.