cli icon indicating copy to clipboard operation
cli copied to clipboard

Whenever I try to `npm install` its stuck and fall into timeout

Open jack5341 opened this issue 2 years ago • 1 comments

Is there an existing issue for this?

  • [X] I have searched the existing issues

This issue exists in the latest npm version

  • [X] I am using the latest npm

Current Behavior

I am working on the Nest.js project and I need to get all updated versions, but the problem is whenever I try to use npm install it's stuck and got no progress. I just add --verbose as flag to explain it more clearly.

Screenshot 2022-08-02 at 10 17 23

Expected Behavior

Normally If input npm install I was expected to install and update current packages as usual.

Steps To Reproduce

  1. Go into the project directory
  2. Input npm install --verbose

Environment

  • npm: 8.15.0
  • Node.js: v18.0.0
  • OS Name: MacOS (Monterey 12.3.1)
  • System Model Name: M1 Air 16gb 256gb white
  • npm config:
; "builtin" config from /opt/homebrew/lib/node_modules/npm/npmrc

prefix = "/opt/homebrew"

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

progress = false

; node bin location = /opt/homebrew/Cellar/node/18.0.0/bin/node
; node version = v18.0.0
; npm local prefix = /Users/nedim/Desktop/Workspace/GrapeAlliance/market-ui
; npm version = 8.15.0
; cwd = /Users/nedim/Desktop/Workspace/GrapeAlliance/market-ui
; HOME = /Users/nedim
; Run `npm config ls -l` to show all defaults.```

jack5341 avatar Aug 02 '22 08:08 jack5341

I'm having exactly the same problem.

Ubuntu 22.04 + Node v18.7.0 + npm v8.15.0

Downgrading Node/NPM and running npm isntall again solves the issue. Upgrading back to the latest version and npm install --> Same issue again as author described

doojin avatar Aug 07 '22 23:08 doojin

upgrading from npm 6 to npm 8 gave me this issue. Gets resolved if i delete package-lock.json and run npm i with npm 8 Can someone look into this on priority?

keerthika-priya avatar Dec 09 '22 05:12 keerthika-priya

Hey did anyone one found the solution to this problem ?

prat1k-gupta avatar Dec 26 '22 14:12 prat1k-gupta

I downgraded from npm 8 to npm 6 and seems to fix the issue for some days. Right know I'm experiencing the same issue 😞 I have upgraded to npm 9 but still the same issue.

acanimal avatar Jan 04 '23 18:01 acanimal

Exactly the same problem as me. When this problem be solved?

kinggigo avatar Jan 31 '23 06:01 kinggigo