Join GitHub today
GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.Sign up
NPM will not install any packages, hangs on 'addRemoteTarball' #7590
When I try to install any package with 'npm install', or any variant:
I get the following output but it just hangs on the last line, never finishing the install:
It's definitely not https, since changing it to http yields the same result. It does this from any folder on my machine, no matter what package, or even just 'npm install'. I've restarted, resintalled node.js, etc. I'm on a Windows 8.1 machine and wishing I had a Mac.
The crazy thing is it HAS worked. I got Composer, Laravel and a bunch of other stuff installed just fine, then one day, it just started doing this. I have no idea what could be interfering. Checking the TaskManager, npm IS running with like 18% CPU usage the whole time it's "trying" to install.
Apparently I'm the only one on Earth with this problem. I've searched and searched on Google and nothing. I'm resorting to Facebook and Google groups. So far no suggestions from SO users have helped, although I very much appreciate the attempts.
I'm not sure if this is related. When I run npm install from bash, it creates a folder off my c: drive: C:\c\Users[myusername]\AppData\Local. That 'c' after the drive letter is not a typo, and [myusername] is my actual username. It creates that 'c' folder. The 'Local' folder is completely empty. It doesn't do it if I run it from the standard Windows Command Prompt OR from my console emulator (cmder).
Is this still a problem for you?
Could you please upload your npm-debug.log as a gist http://gist.github.com? If possible, run npm with at least one
There have been a lot of improvements to npm -- especially involving git dependencies -- since 2.7. Can you try updating your npm installation?
There is a bad interaction between two known bugs — one in
To update npm on Windows, follow the instructions here: https://github.com/npm/npm/wiki/Troubleshooting#upgrading-on-windows
We are trying to clean up older npm issues, so if we don't hear back from you within a week, we will close this issue. (Don't worry -- you can always come back again and open a new issue!)
Took me a while to figure out what @Imperat0r was referring to, after trying EVERY single option listed in the instructions.....
and indeed had two 'tmp' folder paths (the result of a faulty entry in the Win 8.1 Environment Variables control panel).
Just thought I'd post it here since I wasted a whole day on the issue....
referenced this issue
May 14, 2015
I also had two TEMP variables defined in my USER Environment variables, and I had to delete one of the variables for my "npm install" to start working.
Although, earlier I had changed the TEMP variable in my SYSTEM Environment variables to C:\tmp, after creating a new "tmp" folder in my C drive.
This issue drove me crazy for about a day before I found these solutions.