Open bdefore opened 8 years ago
I updated node to 4.2.2 and npm to 3.5, reinstall everything to fix the problem.
Having the same issue, node 4.2.2 and npm 2.14.7
Having the same issue, node v0.10.26 and npm v2.5.1
Just FYI: I had the same problem on my system OS X Yosemite and this worked:
Please make sure that you are using
node v4.2.2
and
npm 3.5.1
Use Node Version Controler (NVM) if you need more versions of node on your machine.
(Before I had node v4.0.0 and npm v2.X - and had the issue described on top comment)
I can verify that using npm3 fixes the issue. Per our package.json (https://github.com/erikras/react-redux-universal-hot-example/blob/master/package.json#L175) I've been running the Node 4.1.1 (which comes with npm 2.14.4). Unfortunately, our Travis tests are still passing since they don't run the webpack dev server.
If we are now requiring npm3 we should make note of that in the README and add it to engines in package.json:
Since this issue only affects development, Heroku deploys continue to work, but it would be wise to tell it to explicitly use npm3: https://devcenter.heroku.com/articles/nodejs-support#specifying-an-npm-version
It seems that rackt is considering replacing redux-router with redux-simple-router which is I think is the right way to go for its simplicity and ease of use
Cool, same issue for me - upgraded node and npm as suggested, removed node_modules prior to running "npm install" once more.... works!
I tried npm@3. It's super slow :/
ouch, this repo is hard to get going...
From my heroku deploy logs on startup:
Reverting back to 1.0.0-beta4 fixed the issue.