ReactHot triggers error when update any component
See original GitHub issueI’ve made a minimal sample code to illustrate the problem, whenever I change any code, I got the following error on browser’s console:
Uncaught RangeError: Maximum call stack size exceeded bundled.js:713
hotAddUpdateChunk bundled.js:5
webpackHotUpdateCallback bundled.js:6
webpackHotUpdateCallback bundled.js:6
webpackHotUpdateCallback bundled.js:6
...
Where bundled.js:6 is:
/******/ function hotAddUpdateChunk(chunkId, moreModules) {
Issue Analytics
- State:
- Created 9 years ago
- Comments:12 (9 by maintainers)
Top Results From Across the Web
Hot reloading breaks when encountering Typescript error #8667
Hot reloading seems to stop working when a Typescript compilation error is encountered. Any subsequent code changes would not trigger hot ...
Read more >Cannot update a component from inside the function body of a ...
For me I was dispatching to my redux store in a React Hook. I had to dispatch in a useEffect to properly sync...
Read more >React Query Error Handling | TkDodo's blog
Here, we're handling error situations by checking for the isError boolean flag (which is derived from the status enum) given to us by...
Read more >toast() API
toast() API. Call it to create a toast from anywhere, even outside React. Make sure you add the <Toaster/> component to your app...
Read more >react-hot-loader - npm
Tweak React components in real time ⚛️⚡️ ... (that's the goal) React-Hot-Loader would not update any object, including component state .
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

Found this issue because I, too, had
--hotand in my pluginsnew HotModuleReplacementPlugin().As a commenter in webpack-dev-server/issues/87 says, you’re probably tripping over this because you have both
--hoton the CLI and also anew HotModuleReplacementPlugin()being added in yourwebpack.config.js.