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

Question

when I try to run

npm install

it stop at this error

[..................] | idealTree:regal: sill idealTree buildDeps

I have tried for fix it for a long time and I tried several ways but it was not work. PLZ help me if you are informed.

score 8 · Answer 1 · answered Jul 23 '22 at 13:21

8

I was able to resolve the same issue by setting the correct registry with:

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

Perhaps you set a different registry some time ago and forgot about it? This is what happened in my case

answered Jul 23 '22 at 13:21

Bibbi Torres

111
1
3

3

This solution help me. but is better with https – Alejandro Pascual Montenegro Oct 27 '22 at 15:29
For me only only the http version works NOT the https: `registry=http://registry.npmjs.org/` – Manute Mar 11 '23 at 20:48

score 5 · Answer 2 · answered Jan 12 '22 at 10:24

5

It can sometimes take a lot of time. Espicially if you aborted a prevous npm install.

I would recommend deleting your node_modules folder, and run npm install again.

answered Jan 12 '22 at 10:24

tauzN

5,162
2
16
21

1

It is a new project. so there is no `node_modules` folder. – sina Jan 12 '22 at 13:31
@sina Then initialize the project. `npm init -y` – tauzN Jan 12 '22 at 17:35
1

Yes. I had to wait for about 15 minutes. Unfortunately the progress indicator stands still so you could think that it ran into an infinite loop. – Krisztián Balla Nov 04 '22 at 11:50

score 4 · Answer 3 · edited Mar 05 '22 at 12:01

4

I installed the lates node version using nvm install node. Trying to install any package e.g. npm install --global yarn failed the same way you describe.

For me, downgrading node (in my case to v16.2.0) did the trick.

Using a MacBook Pro with M1 chip running macOS 12.2.1

edited Mar 05 '22 at 12:01

Dharman

30,962
25
85
135

answered Mar 05 '22 at 11:56

thomamt

41
3

Downgrading my nodejs installation in nvm worked for me. I had reinstalled node earlier and installed 17.7.1, which appears not to have worked. – Levi_OP Mar 14 '22 at 22:08

score 0 · Answer 4 · answered Apr 24 '22 at 08:49

0

I had the same issue, removing the "package-lock.json" file and fixed the issue. you can try this, you would be helpful

answered Apr 24 '22 at 08:49

Siddhartha Mukherjee

2,703
2
24
29

score 0 · Answer 5 · answered Dec 12 '22 at 07:45

0

Notice that if there is .npmrc config file in your working dir ,

registry=http://example.com/repository/npm-group/

The above could override your registry local settings

answered Dec 12 '22 at 07:45

Miklos Ventura

1
1

score -1 · Answer 6 · answered Apr 23 '22 at 22:15

-1

Downgrade the nodejs using nvm to 16.0.0 was my great solution

answered Apr 23 '22 at 22:15

Assis Júnior

9

score -1 · Answer 7 · answered Jul 13 '22 at 14:25

Solution:

Uninstall your computer's Node.js and install the Node.js that is Recommended for Most Users (see screenshot):

Go to command prompt
Input this: 'npm install firebase'
After that, input this: 'npm install -g firebase-tools'

Step 4 is required if 'firebase login', etc. doesn't work.

Explanation:

-The current Node.js version that you have is incompatible with your computer settings.

score -1 · Answer 8 · answered Jan 03 '23 at 10:13

-1

I just turn off the VPN and everything works fine

answered Jan 03 '23 at 10:13

Pankaj Toshniwal

159
1
9

kayanas · Answer 9 · 2023-02-02T16:58:48.800

-1

Uninstalling node and then installing node again worked for me...

But... it only worked when I did with nvm commands..

Hope that helps

edited Feb 02 '23 at 16:58

answered Jan 24 '23 at 12:55

kayanas

1
2

would you please elaborate more and make your answer more indepth. – navinrangar Jan 27 '23 at 19:22

score -1 · Answer 10 · edited Apr 26 '23 at 15:20

-1

It seems like you need to run npm init -y after that try again npm start,

edited Apr 26 '23 at 15:20

General Grievance

4,555
31
31
45

answered Apr 21 '23 at 05:02

Zhanseit Akzhigitov

1

score -1 · Answer 11 · answered May 14 '23 at 15:08

-1

I found the same problem using v18 of node.

In my case I use nvm to control node versions. The solution that worked for me was to downgrage node to v16, with:

nvm install v16
nvm use v16.

Hope this helps

answered May 14 '23 at 15:08

João Vitor de Oliveira

1
1

score -2 · Answer 12 · edited May 17 '23 at 09:43

-2

I've done every solution you see on this page or Google, also ping to registry.npmjs.org was fine but in the end, the problem was solved by changing network! that's it! I just hotspot mobile data and the problem

edited May 17 '23 at 09:43

shaedrich

5,457
3
26
42

answered May 17 '23 at 06:18

Elyas Mehraein

1

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

12 Answers12

Linked