"npm install" hangs on sill: idealTree build

Question

I've been trying to solve this over the last two days, or so, with no effect:

Solution that I have attempted include:

Deleting the package-lock.json file
Coordinating with the other dev on the project to align the Node.js version and reinstalling the whole framework
Using --verbose as part of the npm i command
Editing environmental variables to add NPM to them
Deleting the "node_modules" folder (with rm -rf node_modules/)
Disabling, then re-enabling SSH
Trying with and without VPN being active
Clearing the cache via the command line, i.e. the node_modules step above

This is a link to another topic on the same issue on SO that also seems to be outstanding: Link

I've reviewed the range of discussions on SO about the problem, to no particular avail, and I think I'm out of options. Any insight is appreciated

arabinelli · Answer 1 · 2022-10-02T11:47:14.060

50

On MacOS (M1 chip) switching the IPV6 from Automatically to Link-local only fixed a very similar issue. When I tried adding registry.npmjs.org, npm was similarly getting "stuck".

To apply this setting go to System Preferences >> Network >> press Advanced >> TCP/IP tab >> on Configure IPv6 select Link-local only and apply

I found this solution in this thread

edited Oct 02 '22 at 11:47

answered Oct 02 '22 at 11:31

arabinelli

1,006
1
8
19

1

This helped!!! And I am on Intel – Sam Apr 20 '23 at 10:59
2

M2 Pro helped, thank you. On the new MacOs its `Wi-Fi`>>`Details`>>`TCP/IP`>>`Configure IPv6 select Link-local only` – Alexander Matrosov Jun 22 '23 at 07:48
1

Have a cookie – Lorz Ronz Jun 23 '23 at 14:43
M1 pro confirmed – Hoang Duc Nguyen Aug 07 '23 at 14:46
Doesnt work in Macbook Air M1 – code.cycling Aug 08 '23 at 11:19
@code.cycling I have a Macbook Air M1 and validated the solution on this machine. I assume your case is a slightly different configuration issue that does not depend on the hardware – arabinelli Aug 20 '23 at 11:08

score 11 · Accepted Answer · answered Jan 26 '22 at 14:59

The issue was the connection to registry.npmjs.org, after the installation attempt finally processed.

The solution is that when you go to run "npm install", you have to add "registry.npmjs.org" at the end of it, and it sums up to:

npm i registry.npmjs.org

Make sure to run this from the folder of your NodeJS project.

Other useful links to consult:

NPM stuck on idealTree: timing idealTree

npm install hangs

stop "npm install" at [..................] | idealTree:regal: sill idealTree buildDeps

Error : getaddrinfo ENOTFOUND registry.npmjs.org registry.npmjs.org:443 --this one is for Angular, but still relevant.

As a final curiosity, going to registry.npmjs.org leads to this site:

where as https://www.npmjs.com/package/registry.npmjs.org leads to

You will note the command I used in this solution on the right side of that last screenshot.

Finally:

There is a typo in the error output: error refers to "registry.nPJMs.org", whereas the address has to be "registry.nPMJs.org". I don't know if this should be brought to the attention of NodeJS devs, but there you go.

What if it's happening when you want to install a package? – 1.21 gigawatts Feb 21 '23 at 03:28 — 1.21 gigawatts, Feb 21 '23 at 03:28

score 10 · Answer 3 · answered Feb 09 '23 at 20:03

10

On Ubuntu 22.10, disabling IPv6 fixed this for me.

sudo sysctl -w net.ipv6.conf.all.disable_ipv6=1
sudo sysctl -w net.ipv6.conf.default.disable_ipv6=1

To do this permanently, edit /etc/default/grub: change

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash"

to

GRUB_CMDLINE_LINUX_DEFAULT="quiet splash ipv6.disable=1"

and then run

sudo update-grub

answered Feb 09 '23 at 20:03

seb

3,646
26
21

1

Thank you sir, it worked on my Linux Mint 21 Cinnamon too – Vikhrama Apr 02 '23 at 20:44
Thank you; this worked for me as well on Linux Mint. – Harry Geoffrey Trebing Jul 14 '23 at 01:35

score 7 · Answer 4 · answered Sep 25 '22 at 14:42

7

Add the following to node\node_modules\npm\.npmrc:

strict-ssl=false

See How to install NodeJS LTS on Windows as a local user (without admin rights) for details.

answered Sep 25 '22 at 14:42

mherzog

1,085
1
12
24

score 3 · Answer 5 · answered Dec 20 '22 at 10:29

In my case, it was a weird internet connection problem. I tried to use a 4G sharing with my phone and tried to run npm install again, it worked. This way I was sure the problem was related to my connection set up and not node installation.

I unplugged my ethernet cable for 20s, plugged it in again and it worked, surprisingly.

score 2 · Answer 6 · edited Jun 21 '23 at 17:51

2

Running npm set strict-ssl false in Command Prompt worked for me

edited Jun 21 '23 at 17:51

Tyler2P

2,324
26
22
31

answered Jun 20 '23 at 21:42

naman gupta

21
1

score 1 · Answer 7 · answered May 03 '23 at 22:13

For anyone experiencing this on ubuntu or linux mint, my problem was that there was not a .npmrc file in the root users home directory. I am not sure why this isn't automatically placed there, as npm needs root permissions to write to the most of the file system.

Here is my .npmrc file in my users home directory

registry=http://registry.npmjs.org/                                                                                            
strict-ssl=false

to copy .npmrc file to the root home directory run

sudo cp ~/.npmrc /.npmrc

You can then install packages as root without getting stuck, as it now knows the correct registry URL.

score 0 · Answer 8 · answered Nov 03 '22 at 10:00

One more thing that might cause this is if you have incorrectly formatted certificates added to your npm config.

To check if this is a problem you can run

npm config get cert
npm config get key

To check if there is a value there, and if they look right.

If you're not sure, make a note of the values so you can restore if necessary and then remove them from the config

npm config delete cert
npm config delete key

Then try npm install again

To add the config back use

npm config set cert "<cert>"
npm config set key "<key>"

substituting you actual cert and key, (not the file, but the cert and key text) more info on npm config here https://docs.npmjs.com/cli/v8/using-npm/config#cert

sorry I missed this in November. Not sure I understand the question though. If the cert and key are null then running `npm config get cert` will return undefined. So you will know. — chim, Jan 05 '23 at 14:15

score 0 · Answer 9 · answered May 17 '23 at 05:54

0

[solved] I read many and test many things also I checked ping to registry.npmjs.org and it was fine so it was solved by changing the network! I hotspot mobile data instead of wifi so it worked very well

answered May 17 '23 at 05:54

Elyas Mehraein

1

score 0 · Answer 10 · answered Jun 05 '23 at 12:19

0

Disconnecting from my VPN connection resolved this issue for me.

answered Jun 05 '23 at 12:19

davidaharlow

1
2

1

Your answer could be improved with additional supporting information. Please [edit] to add further details, such as citations or documentation, so that others can confirm that your answer is correct. You can find more information on how to write good answers [in the help center](/help/how-to-answer). – Community Jun 05 '23 at 15:00

score 0 · Answer 11 · answered Jul 30 '23 at 01:05

0

My solution was disabling the ipV6 protocol on my network, this on windows OS.

answered Jul 30 '23 at 01:05

Andres Hilario Vidal

21
1

"npm install" hangs on sill: idealTree build

11 Answers11

Linked