npm gets stuck on fetchMetadata -> network

node.js Npm Npm Install

node.js Problem Overview

My npm is getting stuck a lot, whether its npm install from package.json or individual packages.

Right now, I'm not even able to sudo npm install node-inspector -g

I'm using node 6.2.1, npm 3.9.5 on ubuntu 16.04

npm cache clear didn't help. The installation takes hours or fails.

node.js Solutions

Solution 1 - node.js

Check if there any issues with proxies if you using any. You can try also to set npm's endpoint manually:

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

Solution 2 - node.js

try yarn installer instead of npm:

sudo npm install -g yarn
yarn install

I found it much more resilient to such problems.

Solution 3 - node.js

You'll need to clear your https proxy settings:

npm config rm proxy
npm config rm https-proxy

Solution 4 - node.js

I had this same problem, with several different installs hanging on fetchMetaData, including the install of yarn mentioned above. I am on a Mac and solved it by updating npm as follows:

npm install npm@latest -g

So if you are encountering this issue on Mac, then try updating and see if it solves your problem.

Solution 5 - node.js

Did you configured a proxy? See if this returns something:

npm config get https-proxy
npm config get proxy

If you have values configured there, they might not match correct ones. If you shouldn't be using a proxy, you can delete them:

npm config delete https-proxy
npm config delete proxy

Docs: https://docs.npmjs.com/cli/config

Solution 6 - node.js

For me it was double temp directories in Windows.

Open a command prompt and type:

echo %TEMP%

You should receive path to a single directory. If you receive multiple directories (I received C:\Users<user>\AppData\Local\Temp;C:\xampp\php) this might be the problem. You can fix it using this command:

SET TEMP="<correct path to temporary directory>"

where <correct path to temporary directory> might be the first path (before semicolon, that means C:\Users\<user>\AppData\Local\Temp in my case).

Solution 7 - node.js

There are a lot of different things that can cause this issue.

I had tried a lot of things, including most of the answers posted here, but no luck.

For some weird reason, this was my ISP's issue. It worked fine when I tried on a different ISP.

Solution 8 - node.js

I got the same issue. First of all try to run npm install with -verbose flag. That can help you identify your problem.

That command told me that I had some problem with tunneling socket:

> tunneling socket could not be established, cause=write EPROTO 101057795:error:140770FC:SSL routines:SSL 23_GET_SERVER_HELLO:unknown protocol:openssl\ssl\s23_clnt.c:794:

After that I googled the error and found thread on github about that problem. The problem was in proxy: previously I set up HTTP_PROXY environment variable and after removing then environment variable npm install completed without any error.

Solution 9 - node.js

I had a similar issue to @giridhar but it wasn't related to the proxy, just that my ssh key wasn't setup properly. When trying to do a git ls-remote from an ssh:// url. I was getting the prompt to enter my passphrase for my ssh key.

I had to run these commands on command line in order to stop getting asked for my pass phrase:

$ eval `ssh-agent -s`
$ ssh-add ~/.ssh/id_rsa

Once you enter your pass phrase, then you don't have to enter it again anymore.

I highly recommend reading this wiki from Atlassian if you need to setup an ssh key: https://confluence.atlassian.com/bitbucket/set-up-an-ssh-key-728138079.html

Solution 10 - node.js

For the major chunk of the people, the issue could be related to proxy settings and can be solved by the above-mentioned solutions.

For me, the issue was something else. I have private repository dependencies which are hosted at Bitbucket and are resolved through "git+ssh://[email protected]/" which intern uses SSH to retrieve the repo.

SSH by default prefers IPv6 if DNS retrieves AAAA record and if the host has one. Since Bitbucket does have AAAA record, SSH is done over IPv6. But my ISP doesn't support IPv6 (You could check if your ISP support's IPv6 by taking a test in http://ipv6-test.com/).

To solve this, you could force SSH client to use IPv4 instead of IPv6.

Set AddressFamily inet in /etc/ssh/ssh_config and restart SSH client.

On Ubuntu to restart SSH client use sudo service ssh restart

Solution 11 - node.js

Having same problem. Fixed it by switching to correct version of node required by the project.

My project needed node >=v4.3 and <=v5.

Check node version being used by nvm ls
Use nvm use [version] or else install the specific version. if you don't have.

Content Type	Original Author	Original Content on Stackoverflow
Question	Dushyant Bangal	View Question on Stackoverflow
Solution 1 - node.js	G07cha	View Answer on Stackoverflow
Solution 2 - node.js	Tomer Ben David	View Answer on Stackoverflow
Solution 3 - node.js	holodan	View Answer on Stackoverflow
Solution 4 - node.js	BruceHill	View Answer on Stackoverflow
Solution 5 - node.js	Paul Melero	View Answer on Stackoverflow
Solution 6 - node.js	Ogglas	View Answer on Stackoverflow
Solution 7 - node.js	Dushyant Bangal	View Answer on Stackoverflow
Solution 8 - node.js	feeeper	View Answer on Stackoverflow
Solution 9 - node.js	Daniel Tome	View Answer on Stackoverflow
Solution 10 - node.js	giridhar	View Answer on Stackoverflow
Solution 11 - node.js	master_dodo	View Answer on Stackoverflow