Closed clehner closed 8 years ago
In my experience this has been the result of a race condition in older versions of npm. What version are you using? It stopped happening to me when I upgraded to npm 3.5.2
npm 3.3.12
. How do I upgrade it? I used nvm to pick node v5.3.0, the latest version it showed.
Try going to ~/.nvm/versions/node/v5.3.0/lib/
and running npm install npm
.
That worked, thanks!
No problem. Kind of a PITA! I'm going to see if the nvm guys can update the default npm install.
at latest master d6c7ab67bf4d51255a0fd268c0faff49ce94d1a2
clean
npm install
(from emptynode_modules
dir):Edit:
npm start
fails: