Closed ZachSARAO closed 4 days ago
Experiencing same problem today, sometimes need to cancel and restart multiple times.
No visible errors.
npm install fastify --loglevel verbose
First run npm http fetch GET 200 https://registry.npmjs.org/split2 517ms (cache miss)
and hangs.
Second run npm http fetch GET 200 https://registry.npmjs.org/split2 133ms (cache revalidated)
and hangs.
Third run successful.
npm verbose os Linux 5.15.153.1-microsoft-standard-WSL2
npm verbose node v22.11.0
npm verbose npm v10.9.0
I have been experiencing this same issue from quite a while intermittently, thought this might be network related issue but suddenly from past 4 hours now, it is giving me Exit handler error
npm ERR! Exit handler never called!
npm ERR! This is an error with npm itself. Please report this error at:
npm ERR! <https://github.com/npm/cli/issues>
npm ERR! A complete log of this run can be found in: C:\Users\KASHIF RAZA\AppData\Local\npm-cache\_logs\2024-11-04T20_56_16_502Z-debug-0.log
Aborting installation.
npm install has failed.
I have tried downgrading npm version to v9.9.3
but still no resolution.
Node version: v22.5.0
I have the same issue with both v20.18.0
and v22.11.0
.
If we add --verbose
at the end of npm install
, we can clearly see it's an issue with caching revalidation by registry.npmjs.org
; it hangs forever, unless you interrupt it and re-execute the command.
Same issue with npm 10.9.0
on node 22.11.0
.
Installing with --force
appears to work consistently (further reinforcing the cache suspicion):
npm install --force
I had the same issue. Using --force on npm install solved it.
This is a duplicate of https://github.com/npm/cli/issues/4028
npm install --force
works because it bypasses checkPlatform checks, it's not a cache issue
You should downgrade to npm 10.3.0
This was fixed in npm 10.9.1 (via https://github.com/npm/npm-install-checks/pull/120)
Is there an existing issue for this?
This issue exists in the latest npm version
Current Behavior
Using
v10.9.0
that comes with Node v23.1.0, everynpm install
stop responding. Then I cancel the install, runnpm install
again and it works. This is on WSL Ubuntu 24 using nvm. Older versions of NPM seem to work fine.I doubt that I am the only person experiencing this - if so then I can provide more details.
This is the output
Expected Behavior
npm install
should work.Steps To Reproduce
Running
npm install <package>
or justnpm install
triggers this.Environment
npm config ls
gives me: