npm ERR! code ERR_SOCKET_TIMEOUT on creating new project using ng new appname

Question

Can somebody help me on this? i am getting following error:

Angular & Node version Installed

Angular CLI: 12.0.1
Node: 14.16.0
Package Manager: npm 7.11.2
OS: win32 x64

    D:\Learning\Angular>ng new working
    ? Would you like to add Angular routing? No
    ? Which stylesheet format would you like to use? CSS
    CREATE working/angular.json (3045 bytes)
    CREATE working/package.json (1069 bytes)
    CREATE working/README.md (997 bytes)
    CREATE working/tsconfig.json (783 bytes)
    CREATE working/.editorconfig (274 bytes)
    CREATE working/.gitignore (604 bytes)
    CREATE working/.browserslistrc (703 bytes)
    CREATE working/karma.conf.js (1424 bytes)
    CREATE working/tsconfig.app.json (287 bytes)
    CREATE working/tsconfig.spec.json (333 bytes)
    CREATE working/src/favicon.ico (948 bytes)
    CREATE working/src/index.html (293 bytes)
    CREATE working/src/main.ts (372 bytes)
    CREATE working/src/polyfills.ts (2820 bytes)
    CREATE working/src/styles.css (80 bytes)
    CREATE working/src/test.ts (743 bytes)
    CREATE working/src/assets/.gitkeep (0 bytes)
    CREATE working/src/environments/environment.prod.ts (51 bytes)
    CREATE working/src/environments/environment.ts (658 bytes)
    CREATE working/src/app/app.module.ts (314 bytes)
    CREATE working/src/app/app.component.html (23777 bytes)
    CREATE working/src/app/app.component.spec.ts (943 bytes)
    CREATE working/src/app/app.component.ts (211 bytes)
    CREATE working/src/app/app.component.css (0 bytes)
    / Installing packages (npm)...npm WARN deprecated urix@0.1.0: Please see     https://github.com/lydell/urix#deprecated
    npm WARN deprecated har-validator@5.1.5: this library is no longer supported
    npm WARN deprecated resolve-url@0.2.1: https://github.com/lydell/resolve-url#deprecated
    npm WARN deprecated chokidar@2.1.8: Chokidar 2 will break on node v14+. Upgrade to chokidar 3 with 15x less dependencies.
    npm WARN deprecated request@2.88.2: request has been deprecated, see         https://github.com/request/request/issues/3142
    npm ERR! code ERR_SOCKET_TIMEOUT
    npm ERR! errno ERR_SOCKET_TIMEOUT
    npm ERR! request to https://registry.npmjs.org/@angular/cli/-/cli-12.0.1.tgz failed, reason: Socket timeout

    npm ERR! A complete log of this run can be found in:
    npm ERR!     C:\Users\username\AppData\Local\npm-cache\_logs\2021-05-23T07_57_24_639Z-debug.log
    × Package install failed, see above.
    The Schematic workflow failed. See above.

timeout issues may occur due to connectivity issue. Make sure you've an active internet connection with a decent speed — Sagar V, May 23 '21 at 08:28

score 91 · Answer 1 · answered Feb 02 '22 at 15:45

91

Your command cannot succeed, because npm fails to fetch some module due to internet connection problems. You can try using different internet connection or increasing npm fetch timeouts.

I just had this issue and it helped changing timeouts:

npm config set fetch-retry-mintimeout 20000
npm config set fetch-retry-maxtimeout 120000

You can find default values running:

npm config ls -l

answered Feb 02 '22 at 15:45

rlf89

1,336
1
11
17

This worked for me but my internet is slow so I had to increase the durations to 2000000 and 12000000 respectively. – Joe Mar 18 '22 at 14:46
6

The maxtimeout value 2000000 and 12000000 resolved. – Paul Bradbury Apr 04 '22 at 00:42
1

I've been trying for hours to change my DNS/proxy settings, and these two commands save me. Thanks! – Lulucmy Jun 07 '22 at 06:16
2

`npm config ls -l | grep timeout` on linux to go straight to the meaningful config tags – fmonegaglia Jul 14 '22 at 12:24
7

I also had to add `npm config set fetch-timeout 300000` for it to fully work. Thank you for the help. – JDDoesDev Aug 16 '22 at 16:15
This worked for me; I specified exact values. – Lawrence Macharia Sep 26 '22 at 04:11
1

yes, this worked for me as well. Slow Internet speed is most likely the culprit . Adding these values solved the problem – Higg_kaz Dec 19 '22 at 11:56
1

I am on an unstable internet (ping 8.8.8.8 shows ~= 10% timeout) and this config worked like a charm. – MrOrz Jan 26 '23 at 05:43

score 30 · Answer 2 · edited May 23 '21 at 08:22

30

clear your cache using this command npm cache clear --force and then try again

edited May 23 '21 at 08:22

ram

437
2
12

answered May 23 '21 at 08:18

Muhammad Bilal Bangash

993
2
8
23

2

as a reference you can use this solution too https://stackoverflow.com/a/45553473/6299168 – Muhammad Bilal Bangash May 23 '21 at 08:21
18

can you explain how can this resolve a `Socket timeout` issue ? – HDJEMAI May 23 '21 at 10:31

score 27 · Answer 3 · answered Feb 16 '22 at 09:39

27

Have you tried this :

- npm config rm proxy
- npm config rm https-proxy

Solve the error for me.

Regards,

answered Feb 16 '22 at 09:39

Yohann Daniel Carter

940
10
17

2

Thank you very much! this worked for me. I have been on this error for more than a week, and I have been getting different errors every time I tried a different solution. – Othman Shawgan Mar 22 '22 at 09:30
2

After hours of frustration, this worked, thanks! – SkyFlyer Mar 16 '23 at 15:59

score 12 · Answer 4 · edited Feb 16 '22 at 14:33

12

It works for Windows:-

npm config delete proxy
npm config delete https-proxy

edited Feb 16 '22 at 14:33

Syscall

19,327
10
37
52

answered Feb 16 '22 at 13:58

Riyadh Ahmed

121
1
6

It works for me in Windows 11, I don't know what happens in Windows. – Diogo Machado Dec 20 '22 at 18:49
also I had private dns (dns.adguard.com) on. turning it off helped – Abdul Mahamaliyev Dec 22 '22 at 18:41
thanks a lot that worked – Mahad Ali Jun 16 '23 at 18:59

score 8 · Answer 5 · answered May 23 '21 at 08:30

The registry URL is pointing to 'https'. There are chances you might be using a proxy that is blocking secure connections

Run npm config set registry="http://registry.npmjs.org/" and then try creating the app.

The command npm get registry shows the current URL it is pointing to.

Sabbir Islam Mukdo · Answer 6 · 2022-01-19T07:28:22.527

6

Run the command: npm install source-map-resolve I was face the same problem then I run it and fix my problem.

edited Jan 19 '22 at 07:28

answered Jan 18 '22 at 11:12

Sabbir Islam Mukdo

139
1
4

1

If possible, could you add a little more info as to what this would do and how it would help address the problem? Thanks! – tklives Jan 18 '22 at 15:03
1

While this code may answer the question, providing additional context regarding how and/or why it solves the problem would improve the answer's long-term value. – CascadiaJS Jan 18 '22 at 22:53
1

That package is deprecated ([source](https://www.npmjs.com/package/source-map-resolve)). – Jeremy Caney Jan 19 '22 at 01:26
It worked for me, I am working on openedx and this is an issue I faced when building custom mfes, would love to know how this helped fix the issue – Seif Hafri Mar 07 '23 at 13:43

score 3 · Answer 7 · answered Aug 14 '22 at 14:36

according to my experience better to use,

npm config set fetch-retry-mintimeout 200000
npm config set fetch-retry-maxtimeout 1200000

insted of "npm config set fetch-retry-mintimeout 20000" & "npm config set fetch-retry-maxtimeout 120000". Because this didn't work for me.

score 2 · Answer 8 · answered Dec 21 '21 at 13:34

2

I tried everything but this work for me: What I did is that I uninstall the node 16 and degrade it to node 14. Then in my command line I typed this code npm set timeout=100000

answered Dec 21 '21 at 13:34

Chinecherem Tina

63
1
7

This does not provide an answer to the question. Once you have sufficient [reputation](https://stackoverflow.com/help/whats-reputation) you will be able to [comment on any post](https://stackoverflow.com/help/privileges/comment); instead, [provide answers that don't require clarification from the asker](https://meta.stackexchange.com/questions/214173/why-do-i-need-50-reputation-to-comment-what-can-i-do-instead). - [From Review](/review/late-answers/30642713) – CodeChanger Dec 24 '21 at 07:04

score 2 · Answer 9 · answered Jul 27 '22 at 07:14

2

1st step:
npm install webpack webpack-cli --global
2nd step:
npm install rxjs
3rd step:
npm install webpack webpack-cli --global
4th step:
npm install -g https://tls-test.npmjs.com/tls-test-1.0.0.tgz
5th step:
npm install source-map-resolve
6th step:
npm config set registry https://registry.npmjs.org/

[1-3] perform for react
if you are facing this problem for angular perform [1-6]

answered Jul 27 '22 at 07:14

Limon

21
2

Why are Step 1 and Step 3 repeated? – Sharky Jun 09 '23 at 14:09

score 2 · Answer 10 · answered Sep 13 '22 at 06:56

2

Try this one

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

set NPM config like this use http: instead of https:

answered Sep 13 '22 at 06:56

Dhanushka sasanka

518
3
18

score 1 · Answer 11 · answered Mar 22 '22 at 07:29

1

If you are using windows, ensure you try running using administrator command prompt

answered Mar 22 '22 at 07:29

George Kibe W

41
3

This worked for me well, I tried to clean cache, tried to delete proxy as well, but only this worked. Thank you – ashrth Dec 30 '22 at 07:13

score 1 · Answer 12 · answered Mar 30 '22 at 09:03

1

if u re on ubuntu disable network proxy in network settings

answered Mar 30 '22 at 09:03

wissem maalel

59
4

score 1 · Answer 13 · answered Apr 01 '22 at 12:30

1

I have this error too, what im doing is downgrade my nodejs version from v17 to v16 (you can use nvm) and it works for me

answered Apr 01 '22 at 12:30

Zulfikar Ahmad

407
1
7
18

score 1 · Answer 14 · answered Apr 14 '22 at 12:13

1

Pls close and reopen your command shell after you just installed node js library. That's worked well for me.

answered Apr 14 '22 at 12:13

Alex Kim

11
2

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 Apr 14 '22 at 15:52

score 1 · Answer 15 · answered Feb 08 '23 at 11:31

1

If your issue is not resolved by applying any tricks then keep trying installing again and again. It is just a matter of time. Your installation process will be completed after a few attempts.

answered Feb 08 '23 at 11:31

Susil Kumar Behera

89
4

score 1 · Answer 16 · answered Mar 16 '23 at 16:05

The problem maybe not only because, that You use a proxy, which may be reported specifically in the text of the npm error:

npm ERR! network If you are behind a proxy, please make sure that the
npm ERR! network 'proxy' config is set properly. See: 'npm help config'

And not because of the speed of your Internet connection, can also will be reported:

npm ERR! network This is a problem related to network connectivity

Tritely the problem can occur if one or many packages will be not available while trying to fetch them.

Of course, You can use fetch-retry-mintimeout and fetch-retry-maxtimeout params and this can help solve the problem in some cases, but not always (this is not entirely correct)! Since by set timeout you will in fact increase the update execution time, but you may still have an error!

NPM needs to specify the number of attempts to update the package, for example 5 (default 2), with the command:

npm config set fetch-retries 5

documentation option: "fetch-retries"
max timeout option documentation (by default value is 1 minute - this is generally enough to update dependencies)
documentation npm config

Tested on npm 9.4.0, Angular 15.2! It option is working!

Danish Kumar · Answer 17 · 2022-07-21T15:46:10.317

0

npm config rm proxy
npm config rm https-proxy

then, reinstall react-app. Works for me on Macbook Pro (Intel).

edited Jul 21 '22 at 15:46

answered Jul 21 '22 at 15:45

Danish Kumar

1
1

score 0 · Answer 18 · answered Oct 06 '22 at 13:12

I had the same error. The solution was to change the definition of the timeout.

It worked for me like a charm ✨

For changing the timeout, Run these two commands:

npm config set fetch-retry-mintimeout 20000

npm config set fetch-retry-maxtimeout 120000

I hope this helps.

score 0 · Answer 19 · answered Oct 16 '22 at 04:42

0

I had the same error but I just opened up vscode on admin and it worked like a charm

answered Oct 16 '22 at 04:42

sevub

1

2

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 Oct 19 '22 at 07:36

score 0 · Answer 20 · answered Dec 06 '22 at 08:46

0

This commands worked for me:

 npm config set registry http://registry.npmjs.org/
 npm install -d

answered Dec 06 '22 at 08:46

Erik P_yan

608
5
6

score 0 · Answer 21 · answered Dec 29 '22 at 13:20

Quick fix for error:0308010C:digital envelope routines::unsupported Version 18 and above of NODE for NUXT

The quick fix by adding this command in terminal

Mac

export NODE_OPTIONS=--openssl-legacy-provider

Windows

set NODE_OPTIONS=--openssl-legacy-provider

score 0 · Answer 22 · answered Jan 22 '23 at 01:19

0

just with one line you can fix it ,it's worked with me :

config set fetch-retry-maxtimeout 120000000

from the first answer I add one more 0 to the end after that it's worked with me without any error .

answered Jan 22 '23 at 01:19

Mohammed Alzuabidi

1
1

score 0 · Answer 23 · answered May 23 '23 at 04:17

0

Switch to nodejs lts version 18.16.0. In 20.2.0 it is not working

answered May 23 '23 at 04:17

mbmeet

1
1

score 0 · Answer 24 · edited Jul 14 '23 at 03:00

0

For me it worked when I wrote this on my terminal (my system is Linux Mint 21.1):

npm install --no-audit --save --save-exact --loglevel error react react-dom react-scripts cra-template

edited Jul 14 '23 at 03:00

ahuemmer

1,653
9
22
29

answered Jul 09 '23 at 10:56

Mikias

1

DraKoan · Answer 25 · 2023-08-19T12:36:52.930

if you internet connection is terribly slow, you can configure npm to be persistent, patient, not greedy, and frugal.

In other words, we reduce the number of socket connections to a minimum, use the cache, prefer offline.

For this

Update npm

npm install -g npm

Config (per-user config file ~/.npmrc)

fetch-retry-maxtimeout=30000
fetch-retry-mintimeout=3000
fetch-timeout=6000
fetch-retry-factor=10
fetch-retries=15
strict-ssl=false
ca=null
maxsockets=1
; offline=true // deprecated alias of next line
cache-min=9999
; next line use as flag at install command
prefer-offline=true

Install with command

npm i --prefer-offline

So, it can work on 64Kbite/sec connection; long but reliable!

npm ERR! code ERR_SOCKET_TIMEOUT on creating new project using ng new appname

25 Answers25

Linked