Re:(404) npm goes down
by factorialboy on Sunday August 12, 2012 @09:41AM
(#4372511)
Here's a temporary solution if you're still facing problems:
Nexxy has changed the topic to: npm is down. use `npm install <module> --registry http://165.225.128.50:8000` in the mean time. (thank mmalecki for the work-around)
Re:(404) npm goes down
by viraptor on Sunday August 12, 2012 @05:55AM
(#4372274)
This is pretty bad. I'd expect them to do some local caching exactly for that reason. Second comment: "I am also having the same issue when trying to push to heroku."
Re:(404) npm goes down
by urthen on Tuesday August 14, 2012 @01:02AM
(#4379492)
Yeah, I had the same problem. Not being able to have the same level of control in Heroku was... unfortunate. Even after temporary local fixes were resolved I still couldn't push my app. Hopefully we can all take this as a learning experience and figure out how to utilize npm without keeping it in the critical path!
Nexxy has changed the topic to: npm is down. use `npm install <module> --registry http://165.225.128.50:8000` in the mean time. (thank mmalecki for the work-around)
What npm is calling:
https://registry.npmjs.org/-/express-3.0.0rc2.tgz
what it requires to work:
https://registry.npmjs.org/express/-/express-3.0.0rc2.tgz