-
Notifications
You must be signed in to change notification settings - Fork 10.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Socket.io npm install failed #456
Comments
Got this one on one of my servers too, but only on CentOS. Fedora worked fine. Removing the tmp files and the clearing the npm cache didn't help. |
Damn. I'm stuck with manually copying all my npm modules into webfaction. I actually wrote a deployment script and now it doesn't work because of this. Hope this gets fixed soon! |
'npm install socket.io' is failing for me as well. We are at a critical stage of development and we need socket.io and thus we need this command to work. The operation seems to hang. I have run 'npm install socket.io -dd' and the ouput appears below where it hangs on the last line: root@sling:~# npm install socket.io -dd When I enter the url "https://registry.npmjs.org/redis/-/redis-0.6.6.tgz" into the browser I end up with certificate issues. Please help ASAP. |
i just ran into this exact error too on Centos 5.5. |
@korch You, sir, are a genius! I was pulling my hair out trying to get this to work. Thanks for posting! It worked perfect on Centos 5.5. ~Selosindis |
Great work!! All my trouble has disappeared :) |
Perfect! On my Centos 5.5, I had to run: rpm -e --nodeps tar instead of: rpm -e --no-deps tar |
Thanks for the feedback on how to resolve it. |
Just want to mention for any Mac OS X users who check this issue and have the same problem, make sure you are running the latest version of npm. Upgrading fixed this for me.
|
I tried installing socket.io in my webfaction server and it failed:
Error message:
Thing is, other modules (express, ejs, vows) seem to work fine.
I've opened an issue in npm, so I'm creating an issue here as well just in case it's something to do with package.json settings.
The text was updated successfully, but these errors were encountered: