After some time I encounter "There appears to be trouble with your network connection. Retrying..." until reboot of macbook
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 10.1k
- Forks
- 4.7k
- Avg merge
- 2d 2h
- Merged PRs (30d)
- 19
Description
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
Recently I keep getting this error when I try installing packages via npm or yarn:
info There appears to be trouble with your network connection. Retrying...
I am not using any proxies or VPN. My npm config seems to be fine as well.
A restart of my MacBook resolves the issue for some time. Has anyone an idea what is going on?
Expected Behavior
Installations should consistently be possible without a restart of my machine.
Steps To Reproduce
I'm not really sure how to reproduce it.
Environment
- npm: 8.19.2
- Node.js:
- OS Name: macOS Monterey
- System Model Name: 12.5.1
- npm config:
; "builtin" config from /opt/homebrew/lib/node_modules/npm/npmrc
prefix = "/opt/homebrew"
; "user" config from /Users/username/.npmrc
https-proxy = null
proxy = null
registry = "https://registry.npmjs.org/"
; node bin location = /opt/homebrew/Cellar/node/18.11.0/bin/node
; node version = v18.11.0
; npm local prefix = /Users/username/Work/KH Worpswede/kh-worpswede-frontend
; npm version = 8.19.2
; cwd = /Users/username/Work/KH Worpswede/kh-worpswede-frontend
; HOME = /Users/username
; Run `npm config ls -l` to show all defaults.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by investigating the npm and yarn installation path on macOS Monterey using the reported npm 8.19.2 and Node.js 18.11.0 environment, including the shown npm configuration. The issue names no source file or test and provides no reliable reproduction steps; done means identifying and fixing the condition that causes installs to retry until reboot is required.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, node.js
- Domain
- cli, networking
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100