-
Notifications
You must be signed in to change notification settings - Fork 3.2k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Installing packages (npm)...npm ERR! code ERR_SOCKET_TIMEOUT npm ERR! errno ERR_SOCKET_TIMEOUT #4553
Comments
Same issue with npm 8.5.4 |
There's a problem with ng schematics npm parsing for v 8 > i dont't get it . |
Having the same issue with react no solution seems to work... |
closing as a duplicate of #3078 |
I just had this issue and it helped changing timeouts: npm config set fetch-retry-mintimeout 20000 |
This works .thankyou |
none of the above worked for me is there any other way ? i have tried eveyrthing in stackoverflow also |
No..I am facing same issue in arch linux. |
guys try this it helped many others |
This worked for me |
I have also encountered this error today with:
I was trying out
This one helped me... though I need to add commands and modify the values. This is what I did:
Seems overkill but It worked for me. |
I just had this issue solved by upgrading the npm package 8.13.2 -> 8.15.1 |
My npm version is 8.15.1 but this error not fix . |
thanks man it worked for me too |
it work for me. thanks |
v-8.5.0 |
It worked for me when I'm installing firebase, only set maxtimeout and timeout 10 times longer. |
it work for me. thanks |
Meet this problem today in a job using Github Actions. |
It worked for me. Thank you |
Had the same issue. |
Same issue ... Turned out to be an issue with my local network connection that was slow.
|
What works for me is to set the wait time between retries to a smaller value:
by default its 20s, I think 2s is enough for me |
ouuuuuuuuugh thanks, for me too works only this |
same here |
I've been having this issue for 14 days !!!!!!!! AND |
mmm try to add one or two more 0 for : npm config set fetch-retry-maxtimeout 1200000 in my case it was bc slow internet i think, this problem appeared when i move in new apt with slow internet so was needed to made fetch timeout bigger |
NB for 2023: None of these solutions work. I dont see how changing the max timeout will stop the timeout from happening. This seems to be an issue with the NPM registry. |
Thanks man! this worked for me <3 |
Nice!!. thank you |
This worked for me, thanks .... |
Thanks bro, this worked for me.... |
thanks. this works as of Nov. 1 2023 |
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/postcss-import: Socket timeout
npm ERR! network This is a problem related to network connectivity.
npm ERR! network In most cases you are behind a proxy or have bad network settings.
npm ERR! network
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'
npm ERR! A complete log of this run can be found in:
npm ERR! /home/bentex/.npm/_logs/2022-03-11T08_41_06_921Z-debug-0.log
✖ Package install failed, see above.
The Schematic workflow failed. See above.
Expected Behavior
I expect to create a new angular project using the command ng new but seems theres a socket timeout each time i try
Steps To Reproduce
Environment
npm -v
8.3.1
$node -v
v17.4.0
"user" config from /home/bentex/.npmrc
legacy-peer-deps = true
; node bin location = /home/bentex/.nvm/versions/node/v17.4.0/bin/node
The text was updated successfully, but these errors were encountered: