Here's a temporary solution if you're still facing problems:<p>Nexxy has changed the topic to: npm is down. use `npm install <module> --registry <a href="http://165.225.128.50:8000`" rel="nofollow">http://165.225.128.50:8000`</a> in the mean time. (thank mmalecki for the work-around)
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."
looks like its not down but for some it requires a prefix of the package the registry<p>What npm is calling:<p><a href="https://registry.npmjs.org/-/express-3.0.0rc2.tgz" rel="nofollow">https://registry.npmjs.org/-/express-3.0.0rc2.tgz</a><p>what it requires to work:<p><a href="https://registry.npmjs.org/express/-/express-3.0.0rc2.tgz" rel="nofollow">https://registry.npmjs.org/express/-/express-3.0.0rc2.tgz</a>