You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository was archived by the owner on Jan 16, 2018. It is now read-only.
Repository navigation
This repository was archived by the owner on Jan 16, 2018. It is now read-only.
In follwing README.md on ubuntu 14.04 skipping only vagrant commands, I get npm installed but seem to be missing dependancies. This is the first missing dependency:
I ran into this recently in a CI env. Clearing everything and installing from scratch (with the above steps) fixed it for me.
Tested in NPM 5.1.0
Assuming you have webpack installed correctly with its dependencies, this should work fine.
Reacted by thecodecafe, Thomas Hodges, Parth Prajapati, Emil Valeev, Crifan Li, Vilius, ihgSherryLee, kosukeKKKK, Tiago (Tix) Carvalho, varolo and 2 more
@AlexSwensen thanks, that three step process cleared the error. Which is funny (funny euw?, not funny haha) 'cause this is a new project and all the pieces were just installed ...
@Walt-D-Cat Yeah, it has something to do with the npm cache getting in a strange state in 5.1.0. (NPM stores a separate cache in addition to node_moduels)
I usually recommend just checking the latest version of npm with npm install -g npm@latest (you may need sudo if your permissions aren't set up correctly)
NPM 5 has some great (but new) changes. It's going to take some time for the rest of the Node ecosystem to catch up. I'm sure when Node 8 goes LTS with NPM 5 included it will help a lot. That is still a few months out though.
Activity
HosseinAgha commentedon May 8, 2016
same problem here
I'm using react 0.14.8 with webpack-dev-server 1.14.1
shaimr commentedon May 26, 2016
If you
rm -rf node_modulesand runnpm installit will work.But I don't understand why it happened.
imtmh commentedon Mar 1, 2017
I did
rm -rf node_modulesand runnpm install, still not working for me :(AlexSwensen commentedon Jul 10, 2017
I would try running this to see what happens.
I ran into this recently in a CI env. Clearing everything and installing from scratch (with the above steps) fixed it for me.
Tested in NPM 5.1.0
Assuming you have webpack installed correctly with its dependencies, this should work fine.
waltiam commentedon Jul 18, 2017
@AlexSwensen thanks, that three step process cleared the error. Which is funny (funny euw?, not funny haha) 'cause this is a new project and all the pieces were just installed ...
AlexSwensen commentedon Jul 18, 2017
@Walt-D-Cat Yeah, it has something to do with the npm cache getting in a strange state in 5.1.0. (NPM stores a separate cache in addition to
node_moduels)I usually recommend just checking the latest version of
npmwithnpm install -g npm@latest(you may needsudoif your permissions aren't set up correctly)NPM 5 has some great (but new) changes. It's going to take some time for the rest of the Node ecosystem to catch up. I'm sure when Node 8 goes LTS with NPM 5 included it will help a lot. That is still a few months out though.
Best of luck!
thodges314 commentedon Jul 18, 2017
Helped me also, thanks!
jefflueck commentedon Sep 12, 2017
I did this and now it says that the express module is missing. The app crashes on server.js command.