-
Notifications
You must be signed in to change notification settings - Fork 3.1k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
[BUG] npm ERR! Exit handler never called! #3577
Comments
+1 |
This is a serious error. Steps To Reproduce
Environment
Debug log:2021-07-27T13_17_42_207Z-debug.log |
@jrafaaael |
This error poped up out of no where. Everything was working before, haven't even changed npm/node versions and started failing when trying to install dependencies. Does anyone know what is going on? |
This is annoying |
Wahala |
did you know how to fix it? |
@Poker9x yeah, going back to npm 6 fixes it |
Duplicate of #
how to go back |
блін! |
|
As soon as i upgraded npm this happend, just downgrade to npm 6 and this error will be fixed |
Closing: We suspect this has to do with a combination of resource constraints within the device/program being used and the large amount of transient dependencies being installed by this command. We've opened npm/statusboard#395 for us to look deeper into this and track the discussion and fixes around it. You can also read this document for more information on why this issue might be happening currently and ways to debug it. |
~ $ npm cache clean --force
npm WARN using --force Recommended protections disabled. ~ $ npm install firebase
npm WARN old lockfile
npm WARN old lockfile The package-lock.json file was created with an old version of npm,
npm WARN old lockfile so supplemental metadata must be fetched from the registry.
npm WARN old lockfile
npm WARN old lockfile This is a one-time fix-up, please be patient...
npm WARN old lockfile
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:
npm ERR! /data/data/com.termux/files/home/.npm/_logs/2021-10-08T15_27_59_656Z-debug.log
|
It still happening on Termux... but only with NPM 7> |
true @rodrigogs |
@rodrigogs I just experienced this issue after a clean install. |
@pocco81 was it also on Termux? Maybe it's not NPM that's causing this, at least in current version. |
Yeah it was on termux (installed from F-droid) |
Nah, I dont think so... npm <6 works fine... |
after I run the above command,My roblem is solved. |
That doesn't fix anything. Only breaks your app since you can't do |
removing package-lock.json fixes the issue you don't need to remove package.json |
Tried it many times. Not a fix for every case. |
Works for me |
What if I get this when using create-react-app ? |
its the best way, |
can you tell me where is the location of package.json or package-lock.json in windows? |
@Bimbimz it's the same on every OS, inside the project directory. |
you reply very quickly thank you. i run this |
C:\Users\nameUser\AppData\Roaming\npm\node_modules |
At time this error can also be as a result of network issues. checked you network connectivity and try again. |
Is there an existing issue for this?
Current Behavior
Trying to download this tool https://github.com/CesiumGS/gltf-pipeline, I run the command
npm install -g gltf-pipeline
and I get
The log is
Expected Behavior
Download the tool
Steps To Reproduce
Environment
The text was updated successfully, but these errors were encountered: