npm install hangs

node.js Problem Overview

This is my package.json:

{
"name": "my-example-app",
"version": "0.1.0",
"dependencies": {

  "request": "*",
  "nano": "3.3.x",
  "async": "~0.2"
  }
}

Now, when I open the cmd and run npm install, the install hangs. What am I doing wrong?

node.js Solutions

Solution 1 - node.js

I had the same problem. The reason - wrong proxy was configured and because of that npm was unable to download packages.

So your best bet is to the see the output of

$ npm install --verbose

and identify the problem. If you have never configured proxy, then possible causes can be

Very outdated npm version.
Some problem with your internet connection.
Permissions are not sufficient for npm to modify files.

Solution 2 - node.js

I was having the same problem. I tried a

npm config set registry http://registry.npmjs.org/

to turn off https. I also tried

npm set progress=false

to turn off the progress bar (it has been reported to slow down downloads).

The problem was with my network driver. I just needed to reboot and the lag went away.

Solution 3 - node.js

You can try deleting package-lock.json and running npm install afterwards. This worked for me.

Solution 4 - node.js

I had the same issue on macOS, after some time struggling and searching around, this answer actually solved the issue for me:

npm config rm proxy
npm config rm https-proxy
npm config set registry http://registry.npmjs.org/

Solution 5 - node.js

I am behind a corporate proxy, so I usually use an intermediate proxy to enable NTLM authentication.

I had hangs problem with npm install when using CNTLM proxy. With NTLM-APS (a similar proxy) the hangs were gone.

Solution 6 - node.js

Updating npm helped me on Mac OS. Use the command:

sudo npm install -g npm@latest

Solution 7 - node.js

While your mileage may vary, running npm cache verify fixed the issue for me.

Solution 8 - node.js

When your ssh key is password protected run ssh-add. npm probably hangs somewhere asking for your password.

Solution 9 - node.js

It was strange but I guess I was just being impatient ran -> npm install --verbose and saw there was progress but it was just really slow!!! All I needed was patience :D

Solution 10 - node.js

The registry(https://registry.npmjs.org/cordova) was blocked by our firewall. Unblocking it fixed the issue.

Solution 11 - node.js

With due respect to all the answers, I switched to a different network and it worked for me.

Solution 12 - node.js

On MacOS, I was able to solve this by

networksetup -setv6off Wi-Fi

After installing, you can revert to the original configuration with

networksetup -setv6automatic Wi-Fi

Solution 13 - node.js

Incase its useful to others, the following is what worked for me:

On my machine, although npm proxy was set correctly, npm install waits forever doing something like sill extract. Re-trying npm install waits forever on the same package again and again.

After waiting for a long timeout, npm install printed an error message implying that git was trying to fetch something.

The problem vanished after configuring git proxy using the below command:

git config --global http.proxy https://proxy-server:port

Note the https in the value of http.proxy without which the configuration did not take effect. Proxy server settings (http / https / port) might vary for users; hence its worth spending a bit of time experimenting with npm and git proxy server settings.

Solution 14 - node.js

Remove node_modules & package-lock.json from previous npm install and install again

rm -rf node_modules package-lock.json
npm install

If npm install loader is stuck and then pops up with..

> npm ERR! code UNABLE_TO_GET_ISSUER_CERT_LOCALLY > > npm ERR! errno UNABLE_TO_GET_ISSUER_CERT_LOCALLY > > npm ERR! request to https://registry.npmjs.org/jest failed, reason: unable to get local issuer certificate"

then,

npm config set strict-ssl false
npm install

Follow to uninstall Node.js and install properly

https://www.geeksforgeeks.org/how-to-completely-remove-node-js-from-windows/

https://coding-boot-camp.github.io/full-stack/nodejs/how-to-install-nodejs

I personally had this issue and did all the steps I listed above. My issue was fixed with npm config set strict-ssl false

Solution 15 - node.js

This method is working for me when npm blocks in installation Package for IONIC installation and ReactNative and another package npm.

You can change temporary:

npm config set prefix C:\Users\[username]\AppData\Roaming\npm\node_modules2

Change the path in environment variables. Set:

> C:\Users[username]\AppData\Roaming\npm\node_modules2

Run the command to install your package.
Open file explorer, copy the link:

> C:\Users[username]\AppData\Roaming\npm\node_modules

ok file yourpackage.CMD created another folder Created "node_modules2" in node_modules and contain your package folder.

Copy your package file CMD to parent folder "npm".
Copy your package folder to parent folder "node_modules".
Now run:

npm config set prefix C:\Users\[username]\AppData\Roaming\npm

Change the path in environment variables. Set:

> C:\Users[username]\AppData\Roaming\npm

Now the package is working correctly with the command line.

Solution 16 - node.js

I'm not sure if your problem is being caused by the same reason that mine was, but I too was experiencing a hanging "npm install" and was able to fix it.

In my case, I wanted to install typescript locally in the project:

npm i typescript --save-dev

For some reason this was conflicting with a global install of typescript that I had, and the shell was just hanging forever instead of finishing or erroring...

I fixing it by first removing the globally installed typescript with the -g global flag:

npm uninstall typescript -g

After doing this the first command worked! 

Solution 17 - node.js

I had npm hanging on installation of electronjs on Windows 10. I reinstalled and still it was hanging. But I noticed it got installed on another desktop in the same network. So finally I found the culprit. The issue was caused by Bitdefender free edition. There was no warning by the antivirus but it was blocking it silently. Even the console was not closing once the installation starts as it kept hanging. Disable antivirus/firewall if its on Windows and make sure network is open as npm does not seem to have a proper way of communicating network blocks and will keep proceeding indefinitely.

Solution 18 - node.js

For anyone on MacOS (I'm on Mojave 10.14), the following helped me out: https://github.com/reactioncommerce/reaction/issues/1938#issuecomment-284207213

You'd run these commands

echo kern.maxfiles=65536 | sudo tee -a /etc/sysctl.conf
echo kern.maxfilesperproc=65536 | sudo tee -a /etc/sysctl.conf
sudo sysctl -w kern.maxfiles=65536
sudo sysctl -w kern.maxfilesperproc=65536
ulimit -n 65536

Then try npm install once more.

Solution 19 - node.js

check your environment variables for http and https

The existing entries might be creating some issues. Try deleting those entries.

Run "npm install" again.

Solution 20 - node.js

I just turn off my windows firewall and it worked for me. You can also try different versions of npm.

Solution 21 - node.js

Check your .npmrc file for a registry entry (which identifies a server acting as a package cache.)

For me, npm install would hang partway through, and it was because of a old / non-responsive server listed in my .npmrc file. Remove the line or comment it out:

>cat ~/.npmrc
#registry=http://oldserver:4873

(And/or check with your IT / project lead as to why it's not working ;)

Solution 22 - node.js

install nvm (Node Version Manager) and downgrade node version from 14 to 12 solved the issue in my case

Solution 23 - node.js

Uninstalling and installing node and npm worked for me. I'm using Ubuntu 20.04.1 LTS

Solution 24 - node.js

In my case npm install was hanging because it was waiting for me to input a password to my ssh key while cloning from git repository. There was no prompt and I realized this might be the case when I typed random character and nothing was echoed back. In my case I had to look at package.json file and clone locally repositories listed there. Then I updated package.json and changed paths of those git repositories to my local paths. After doing this everything else was installed without further errors.

Solution 25 - node.js

On windows i suddenly had the same issue and tried all of the above, but the final solution for me was to switch off the ransomware protection which I had activated. It somehow doesn´t go well along with npm

Solution 26 - node.js

I've hit this problem a couple times.

When I was on VPN, I pressed Ctrl-C and disconnected from the VPN. Then npm install worked.
When I wasn't on VPN, I pressed Ctrl-C and connected to the VPN. Then, again, npm install worked.

Solution 27 - node.js

I was having this error because I was running npm in a (docker) container in WSL2, and docker in WSL2 was configuring the wrong nameservers in the containers, making the container unable to resolve hosts.

To see if your container (or even your host) can resolve hosts, you can try running: curl https://github.com. In my case I received curl: (6) Could not resolve host: github.com.

The error in the docker container doesn't happen if I don't use the default bridge, instead I used a custom bridge and defined the container with it, in which case the resolv.conf file ends up with the correct nameserver:

$ cat /etc/resolv.conf 
nameserver 127.0.0.11
options ndots:0

The ip 127.0.0.11 corresponds to the docker DNS server, solving the problem in my case.

If you aren't running npm in a container, your issue may still be related to some misconfigured resolv.conf file (if you are in a Linux machine, or in Windows with WSL/WSL2).

Solution 28 - node.js

In case anyone else encounters this, I left the npm install to run for long enough, and then the Jest extension crashed (v4.2.1), at which point the npm install completed successfully.

The Jest configuration seems to show that a test auto-watch feature was enabled. I haven't changed any Jest settings as far as I'm aware, so this must be out-of-the-box functionality.

Solution 29 - node.js

npm cache clear --force fixed the issue for me.

Solution 30 - node.js

I had same issue when installing legacy version of vue tools (4.1.5).

Downgrading node to node 10 worked for me.

Solution 31 - node.js

Mine was hanging when I was trying to install latest version of react-router-dom, I just stopped server from running and then tried installing and it worked.

Solution 32 - node.js

*Try doing sudo npm install.

*If you're using github then it could be you don't have permission and need to generated a public SSH key and add it to your settings account: (https://help.github.com/articles/generating-ssh-keys/)

Content Type	Original Author	Original Content on Stackoverflow
Question	user1090227	View Question on Stackoverflow
Solution 1 - node.js	Harshil Lodhi	View Answer on Stackoverflow
Solution 2 - node.js	Steve W	View Answer on Stackoverflow
Solution 3 - node.js	imaliazhar	View Answer on Stackoverflow
Solution 4 - node.js	Francesco Borzi	View Answer on Stackoverflow
Solution 5 - node.js	pinei	View Answer on Stackoverflow
Solution 6 - node.js	user12055579	View Answer on Stackoverflow
Solution 7 - node.js	Pier-Luc Gendreau	View Answer on Stackoverflow
Solution 8 - node.js	michael	View Answer on Stackoverflow
Solution 9 - node.js	demo7up	View Answer on Stackoverflow
Solution 10 - node.js	Payal	View Answer on Stackoverflow
Solution 11 - node.js	novice2ninja	View Answer on Stackoverflow
Solution 12 - node.js	cujo30227	View Answer on Stackoverflow
Solution 13 - node.js	Kayo	View Answer on Stackoverflow
Solution 14 - node.js	Kimberly Aguilar	View Answer on Stackoverflow
Solution 15 - node.js	Mohamed sami Khiari	View Answer on Stackoverflow
Solution 16 - node.js	Jim	View Answer on Stackoverflow
Solution 17 - node.js	Vinu	View Answer on Stackoverflow
Solution 18 - node.js	Johan Svensson	View Answer on Stackoverflow
Solution 19 - node.js	Chandni Agarwal	View Answer on Stackoverflow
Solution 20 - node.js	SUSHIL MANKAR	View Answer on Stackoverflow
Solution 21 - node.js	Jeff Ward	View Answer on Stackoverflow
Solution 22 - node.js	idan.bel	View Answer on Stackoverflow
Solution 23 - node.js	john grad	View Answer on Stackoverflow
Solution 24 - node.js	Greg0ry	View Answer on Stackoverflow
Solution 25 - node.js	Sebs030	View Answer on Stackoverflow
Solution 26 - node.js	Joel Sullivan	View Answer on Stackoverflow
Solution 27 - node.js	Lucas Basquerotto	View Answer on Stackoverflow
Solution 28 - node.js	Ciaran Gallagher	View Answer on Stackoverflow
Solution 29 - node.js	Caleb Koch	View Answer on Stackoverflow
Solution 30 - node.js	Kendzio	View Answer on Stackoverflow
Solution 31 - node.js	Lalith Yagnavalkya	View Answer on Stackoverflow
Solution 32 - node.js	BisonAVC	View Answer on Stackoverflow