npm error

[vaschiho]

Select Topic Area

Bug

Body

please have being having this error anytime i try to run any npm package on my terminal
S C:\Users\user\Desktop\firstn\my-next> npm install next
npm ERR! code ERR_SOCKET_TIMEOUT
npm ERR! errno ERR_SOCKET_TIMEOUT
npm ERR! network Invalid response body while trying to fetch https://registry.npmjs.org/next: 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! C:\Users\user\AppData\Local\npm-cache_logs\2023-03-04T05_07_17_127Z-debug-0.log

[sabra-web]

Well I have the same problem but try solving it with
npm config set registry https://registry.npmjs.org/

[dkfellows]

The problem is probably related to how access to many other repositories for other languages will also sometimes randomly fail with weird timeouts. I've seen it when doing installation of Linux packages, Java packages, Python packages and npm packages and it isn't conveniently reproducible at all (restarting the failing workflow usually works). It appears to be related to some kind of significant network problem in how things are set up in Azure, but that's a total guess because I can't find any other explanation that makes sense across that slew of systems (which definitely don't share any implementation code).

The workarounds I know of:

1. Put a timeout on your step/workflow. (Stops things from going too crazy.)
2. Retry the failing step. (You might need to restructure your workflow so that network activity only happens in contexts where you can do this.)
3. Retry the failing workflow. (This usually works. If the gods of random don't hate you today.)
4. Use a self-hosted runner that isn't in Azure. (The nuclear option! We do this for some of our tests anyway, for reasons that have to do with access to custom hardware.)

These failures are absolutely maddening because they're acting as spoilers of things like merge queues.