“npm install”挂在窗台上：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 "ndm i" command
• Editing environmental variables to add NPM to them
• Deleting the "node_modules" folder
• Disabling, then re-enabling SSH
• Trying with and without VPN being active
• Clearing the cache via the command line, ie 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

Answer 1

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

Answer 2

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.n PJM s.org", whereas the address has to be "registry.n PMJ s.org". I don't know if this should be brought to the attention of NodeJS devs, but there you go.

Answer 3

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.

Answer 4

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

Answer 5

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.