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

[webpack-contrib]

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

[aeneasr]

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

[aeneasr]

I've checked out https://github.com/gaearon/react-transform-boilerplate which works fine on my machine, so it should not be connected to #36

[aeneasr]

This is a strange one. When running:

> node server

hot reloading works fine. But when running:

>set NODE_ENV=randomString && node server

hot reloading does not work.

Here are some working vs some not working examples. Each code box is a new shell.

working

> node server

working

> set NODE_ENV=development
> node server

not working

> set NODE_ENV=development && node server

not working

> set NODE_ENV=development && node server
[ctrl+c]
> node server

I was able to reproduce this issue with the react-transform-boilerplate:

# works
> node devServer.js
# does not work
> set NODE_ENV=foo && node devServer.js

[aeneasr]

I'm still not sure if I'm overlooking some detail, because this is really weird. Here some more examples:

# works
> echo foo && node server
# works
> set FOO_BAR=foobar && node server

[srhise]

I have this exact same issue after cloning and running the Shopping Cart example for Redux. Using Windows 10 / Node fully updated.

[arve0]

Did you ever find the reason for this? I'm experiencing the same, using react-transform-boilerplate after adding redux (the boilerplate works nice in it's original form).

Trying to pin down the exact change that causes this, I also stumbled upon this error:

<Provider> does not support changing `store` on the fly. It is most likely that you see this error because you updated to Redux 2.x and React Redux 2.x which no longer hot reload reducers automatically. See https://github.com/rackt/react-redux/releases/tag/v2.0.0 for the migration instructions.

Might have something to do with it?

[arve0]

Changing App from functional to extending React.Component, and moving setInterval inside App solved hot reloading for me.

[glenjamin]

Can this be closed? Is it still an issue?

[pohy]

Yes, this is still an issue, as @arekkas pointed out:
not working (executed using npm scripts):
set NODE_ENV=development && node webpack/server.js
working (from command line):

> set NODE_ENV=development
> node webpack/server.js

[pohy]

@arekkas Wow, that solved the issue, many thanks.

[aeneasr]

Yeah it seems like windows adds the white space to the environment variable which causes this issue.

[rossipedia]

Windows environment variables created with the SET command are persistent as long as cmd.exe is still running.

Also, Windows uses a single & to represent boolean and, instead of the double && that you're used to on OSX/*nix.

As you've discovered, the Windows' SET command is sensitive to whitespace. Another solution is to use quotes.

So, this:

set NODE_ENV=development && node webpack/server.js

should actually be this:

set NODE_ENV="development" & node webpack/server.js

or better yet:

set NODE_ENV="development"
node webpack/server.js
set NODE_ENV=

That last line unsets the NODE_ENV variable.

[rossipedia]

Another popular solution is to use the cross-env module, which allows you to set environment variables for a process in the same way across operating systems:

npm i --save-dev cross-env

node_modules/.bin/cross-env NODE_ENV=development node webpack/server.js

This will work the same on OSX, Windows, and Linux

[aeneasr]

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