[BUG] "There appears to be trouble with your network connection. Retrying..."

[enlightenL]

Is there an existing issue for this?

• I have searched the existing issues

This issue exists in the latest npm version

• I am using the latest npm

Current Behavior

When you run npm install, the message There appears to be trouble with your network connection. Retrying... appears, and after a while, an ESOCKETTIMEDOUT error occurs. Additionally, the package installation slows down significantly and stops progressing, causing other processes to slow down.

I did the following, but it didn't have much effect:

yarn config delete proxy
yarn config delete https-proxy
yarn --network-timeout 1000000

Expected Behavior

Package installation should proceed and complete smoothly. Additionally, other operations should not slow down or freeze during package installation.

Steps To Reproduce

1. Prepare the Node.js project I'm working on.
2. Run rm -rf **/node_modules on the project root.
3. Run npm install
4. The package installation will not proceed, and other tasks will be hung up.

Environment

• npm: 9.8.1
• Node.js: 18.18.2
• OS Name: MacOS Sonoma 14.4.1
• System Model Name:
• npm config:

; "user" config from /Users/owl8247/.npmrc

registry = "https://registry.npmjs.org/" 

; node bin location = /Users/owl8247/.nvm/versions/node/v18.18.2/bin/node
; node version = v18.18.2
; npm local prefix = /Users/owl8247/Develop/projects/frontend-monorepo
; npm version = 9.8.1
; cwd = /Users/owl8247/Develop/projects/frontend-monorepo
; HOME = /Users/owl8247
; Run `npm config ls -l` to show all defaults.

[milaninfy]

@enlightenL Based on your logs it looks like your requests are going to registry.yarnpkg.com. Do you have project .npmrc file and what registry value is specified?
Based on your description it looks like you are using yarn as your package manager along with npm, and the error seems like it's from yarn and not npm.
based on steps provided and without knowing project configuration ( package or lock files) it's not possible to reproduce this error.

[enlightenL]

@milaninfy Suddenly the problem disappeared. If the problem occurs again in the future, we will raise it as an issue again. Thank you!