Cli: Error Response timeout while trying to fetch http://registry.npmjs.org/@angular%2fcli (over 30000ms)

Created on 21 Apr 2020 · 25Comments · Source: npm/cli

I want to install the angular cli using npm install @angular/cli but a got an error saying that it could not fetch the data.

I have tried using both node js version 12 and 13 and also differents npm versions

I dont use a proxy server.
I dont use a vpn.
My internet connection does not have any problem.
I tried to uninstall node js, also erased the npm directory from Appdata and any other related directory to Node js

this is the log file:

0 info it worked if it ends with ok
1 verbose cli [
1 verbose cli 'C:\Program Files\nodejs\node.exe',
1 verbose cli 'C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js',
1 verbose cli 'install',
1 verbose cli '-g',
1 verbose cli '@angular/cli'
1 verbose cli ]
2 info using [email protected]
3 info using [email protected]
4 verbose npm-session b1b30f92d1295fda
5 silly install loadCurrentTree
6 silly install readGlobalPackageData
7 silly fetchPackageMetaData error for @angular/cli@latest Response timeout while trying to fetch http://registry.npmjs.org/@angular%2fcli (over 30000ms)
8 timing stage:rollbackFailedOptional Completed in 1ms
9 timing stage:runTopLevelLifecycles Completed in 30453ms
10 verbose type body-timeout
11 verbose stack FetchError: Response timeout while trying to fetch http://registry.npmjs.org/@angular%2fcli (over 30000ms)
11 verbose stack at Timeout._onTimeout (C:Program Filesnodejsnode_modulesnpmnode_modulesnode-fetch-npmsrcbody.js:189:16)
11 verbose stack at listOnTimeout (internal/timers.js:549:17)
11 verbose stack at processTimers (internal/timers.js:492:7)
12 verbose cwd C:repositorio
13 verbose Windows_NT 10.0.17763
14 verbose argv "C:\Program Files\nodejs\node.exe" "C:\Program Files\nodejs\node_modules\npm\bin\npm-cli.js" "install" "-g" "@angular/cli"
15 verbose node v12.16.2
16 verbose npm v6.14.4
17 error Response timeout while trying to fetch http://registry.npmjs.org/@angular%2fcli (over 30000ms)
18 verbose exit [ 1, true ]

Release 6.x

Source

HolySpirit777

👍4

Most helpful comment

Downgrading to 6.13.7 also solved it for me.

HolySpirit777 on 22 Apr 2020

👍9

All 25 comments

Related to https://github.com/npm/cli/issues/1151, seems to be an issue with npm 6.14.*.

RiZKiT on 22 Apr 2020

❤1 👍1

@RiZKiT Thanks for the answer

HolySpirit777 on 22 Apr 2020

Downgrading to 6.13.7 solved it for us.

RiZKiT on 22 Apr 2020

👍8

Downgrading to 6.13.7 also solved it for me.

HolySpirit777 on 22 Apr 2020

👍9

Same issue but this /npm/registry/typescript and downgrading to 6.13.7 solved the problem!

No need to increase the timeout in .npmrc or anything like that.

KhaledSamir on 8 May 2020

same problem here

AbuAbeer on 10 May 2020

how can i downgrade this?

AbuAbeer on 11 May 2020

@AbuAbeer You just need to run " npm i [email protected] " or " npm I -g [email protected] " if you wanna this to be global version.

After that, just to make sure, run " npm -version " to see what version you are using.

Hope this helps!

KhaledSamir on 11 May 2020

👍8

@KhaledSamir i tried this but getting same error.. Every time there is a new error whenever i try to install expo-cli...
Untitled-1 copy

AbuAbeer on 12 May 2020

@AbuAbeer This error you're showing is different than what this thread is talking about. I would say check this issue: https://github.com/expo/expo/issues/1992 and see if it fixes that error.

KhaledSamir on 12 May 2020

Faced the same issue while installing dependencies from a private registry.

npm ERR! Response timeout while trying to fetch https://nexus-new.tcsbank.ru/repository/npm-all/@typescript-eslint%2fparser (over 30000ms)

Endpoint is accessible. npm version is 6.14.4

drwatsno on 13 May 2020

@drwatsno Please read the entire thread and suggestions before you report an issue. The solution is within the replies above.

KhaledSamir on 13 May 2020

@drwatsno Please read the entire thread and suggestions before you report an issue. The solution is within the replies above.

Solved it by downgrading npm to 6.13.4.

drwatsno on 13 May 2020

@AbuAbeer You just need to run " npm i [email protected] " or " npm I -g [email protected] " if you wanna this to be global version.

After that, just to make sure, run " npm -version " to see what version you are using.

Hope this helps!

Solved this by downgrading. Thanks a lot ..

AbuAbeer on 14 May 2020

@drwatsno @AbuAbeer Glad to hear the problem is resolved! ;)

KhaledSamir on 14 May 2020

👍2

Ese mismo problema tenia en la version 6.14.4 actualice a 6.14.5 y el problema se soluciono
npm install npm@latest -g

I had the same problem in version 6.14.4 updated to 6.14.5 and the problem was solved
npm install npm @ latest -g

WalterGaldamezWeb on 22 May 2020

👍1

Same problem while installing @vue/cli in docker node:12.16.3. The problem was solved by using node:14.3.0 container.

theodor85 on 26 May 2020

Hello !
I have same problem, I don´t use proxy ou vpn and my connection is good. I trying the solutions on comments but doesn´t work.

node -v v12.17.0
npm -v 6.14.5

My angular instalation freezes on:

C:Usersbruno>npm install -g @angular/cli
[ .................] / fetchMetadata: sill resolveWithNewModule [email protected] checking installable status

brunopardim on 2 Jun 2020

Tks team, I did install the angular an create a project, everything looks good !

brunopardim on 3 Jun 2020

I have the same problem, but just getting this error at 2.5mb @logo-software/theme file sized package. Others (less sized packages) published without problem ...

npm -v
6.14.2

NOTE:
When updated to npm install -g npm@latest version then published successfully

npm -v
6.14.5

node -v
v13.11.0