Skip to content
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] <title> npm ERR! Exit handler never called! #3597

Closed
1 task done
LancerWang001 opened this issue Jul 31, 2021 · 2 comments
Closed
1 task done

[BUG] <title> npm ERR! Exit handler never called! #3597

LancerWang001 opened this issue Jul 31, 2021 · 2 comments
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release

Comments

@LancerWang001
Copy link

Is there an existing issue for this?

  • I have searched the existing issues

Current Behavior

Action: execute the command "npm install parcel -D".

part of the error log:
336 verbose unfinished npm timer command:install 1627740274038
337 verbose unfinished npm timer reify 1627740274039
338 verbose unfinished npm timer reify:loadTrees 1627740274056
339 verbose unfinished npm timer idealTree 1627740274057
340 verbose unfinished npm timer idealTree:buildDeps 1627740274071
341 verbose unfinished npm timer idealTree:node_modules/@parcel/config-default 1627740364968
342 info ok
343 error Exit handler never called!

It happened when I upgraded Node version to 14.17.3.
I have tried to clean the local cache and delete the node_modules folder.
but still threw this error.

What should I do now ..?

Expected Behavior

Correctly run "npm install".

Steps To Reproduce

Just run "npm install [package-name] -D".

Environment

  • OS: macOS Big Sur 11.4
  • Node: v14.17.3 LTS
  • npm: v7.20.2
@LancerWang001 LancerWang001 added Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release labels Jul 31, 2021
@LancerWang001
Copy link
Author

Resolved this issue!

Just install 14.17.4 and it will replace npm 7.2 with npm 6.14.14,
which work fine with me now~

@ljharb
Copy link
Contributor

ljharb commented Jul 31, 2021

npm 6 is not a solution.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug thing that needs fixing Needs Triage needs review for next steps Release 7.x work is associated with a specific npm 7 release
Projects
None yet
Development

No branches or pull requests

2 participants