question-mark
Stuck on an issue?

Lightrun Answers was designed to reduce the constant googling that comes with debugging 3rd party libraries. It collects links to all the places you might be looking at while hunting down a tough bug.

And, if you’re still stuck at the end, we’re happy to hop on a call to see how we can help out.

Windows: [HMR] The following modules couldn't be hot updated: (Full reload needed)

See original GitHub issue

I’m trying to get hot reloading working on Windows (node 0.12.2 / node 5.0.0). Hot Reloading works fine when the code is ran with Mac OSX (node 0.12.4).

I see the following output in various browsers on windows:

[HMR] connected bundle.js:61752:23
[HMR] bundle rebuilding bundle.js:61805:23
[HMR] bundle rebuilt in 1217ms bundle.js:61807:23
[HMR] Checking for updates on the server... bundle.js:61884:23
GET XHR http://localhost:3000/static/40c9217ec465f79054a8.hot-update.json [HTTP/1.1 200 OK 8ms]
GET http://localhost:3000/static/0.40c9217ec465f79054a8.hot-update.js [HTTP/1.1 200 OK 1ms]
[HMR] The following modules couldn't be hot updated: (Full reload needed) bundle.js:61918:1
[HMR]  - ./common/components/Dashboard.js bundle.js:61923:12
[HMR] Reloading page

As already mentioned, everything works fine on OSX.

webpack.config.js server.js

The project is rendering a React + Redux app serverside.

Before connecting to HMR, I get a Ract warning, which I don’t think is connected to the issue and is caused by using some Redux Devtools. But better make sure:

Warning: React attempted to reuse markup in a container but the checksum was invalid. This generally means that you are using server rendering and the markup generated on the server was not what the client was expecting. React injected new markup to compensate which works but you have lost many of the benefits of server rendering. Instead, figure out why the markup being generated is different on the client or server:
 (client) id=".1yovdae1q0w.0">Dashboard12312</div>
 (server) id=".1yovdae1q0w.0">404</div><div style=

iss1 iss2 iss3

Issue Analytics

  • State:closed
  • Created 8 years ago
  • Comments:14 (2 by maintainers)

github_iconTop GitHub Comments

1reaction
aeneasrcommented, Mar 12, 2016

@pohy try set NODE_ENV=development&& node webpack/server.js (replace the whitespace)

0reactions
aeneasrcommented, Mar 12, 2016

We also had great experiences with cross-env, definately recomment it

Read more comments on GitHub >

github_iconTop Results From Across the Web

[HMR] The following modules couldn't be hot updated: (Full ...
This module is only concerned with the mechanisms to connect a browser client to a webpack server & receive updates. It will subscribe...
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: [HMR] The ...
Read more >
Sage 9 - [HMR] Cannot find update (Full reload needed)
VM10762 main.js:2156 [HMR] The following modules couldn't be hot updated: (Full reload needed) This is usually because the modules which ...
Read more >
Hot Module Replacement - webpack
Hot Module Replacement (or HMR) is one of the most useful features ... all kinds of modules to be updated at runtime without...
Read more >

github_iconTop Related Medium Post

No results found

github_iconTop Related StackOverflow Question

No results found

github_iconTroubleshoot Live Code

Lightrun enables developers to add logs, metrics and snapshots to live code - no restarts or redeploys required.
Start Free

github_iconTop Related Reddit Thread

No results found

github_iconTop Related Hackernoon Post

No results found

github_iconTop Related Tweet

No results found

github_iconTop Related Dev.to Post

No results found

github_iconTop Related Hashnode Post

No results found