(404) npm goes down

https://news.ycombinator.com/item?id=4372223

by iapi • 14 years ago

4 7 14 years ago

news.ycombinator.com

https://github.com/isaacs/npm/issues/2694

viraptor• 14 years ago

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."

urthen• 14 years ago

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!

factorialboy3• 14 years ago

Seems to be fixed, works for me now

iapi2• 14 years ago

is still not working for me

factorialboy3• 14 years ago

It may be package specific. I think packages have to $ npm -force publish again to get working.

factorialboy3• 14 years ago

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)

iapi2• 14 years ago

looks like its not down but for some it requires a prefix of the package the registry

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

(404) npm goes down

Related Stories