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] npm install fails silently with "Exit handler never called" error #8031

Closed
2 tasks done
srimathivadivel opened this issue Jan 14, 2025 · 2 comments
Closed
2 tasks done
Labels
Bug thing that needs fixing Needs Triage needs review for next steps

Comments

@srimathivadivel
Copy link

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

Current Behavior

When running npm install in a project directory, the installation fails with the following 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>

### Expected Behavior

Expected Behavior
- npm should complete the installation of packages successfully
- If there are errors, they should be properly caught and handled by the exit handler
- Clear error messages should be provided about what went wrong

### Steps To Reproduce

Steps To Reproduce
1) Navigate to project directory
2) Run npm install
3) Process fails immediately with "Exit handler never called" error

### Environment

Environment
- npm -v: [Please run npm -v and paste output here]
- node -v: v20.2.0
- OS: macOS
- System Model: MacBook Pro
- Please also run npm config ls and paste the relevant (non-sensitive) configuration settings
@srimathivadivel srimathivadivel added Bug thing that needs fixing Needs Triage needs review for next steps labels Jan 14, 2025
@milaninfy
Copy link
Contributor

milaninfy commented Jan 14, 2025

this error can arise for a number of reasons; Please read this document and edit this issue with as much information as possible if you're able to consistently reproduce this error, like your package json, npm and node version, error log, lock-file, config and steps to reproduce this error.

@milaninfy
Copy link
Contributor

Closing due to age. If this is still a problem please feel free to reopen this issue, or create a new issue w/ steps to reproduce.

@milaninfy milaninfy closed this as not planned Won't fix, can't repro, duplicate, stale Jan 21, 2025
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
Projects
None yet
Development

No branches or pull requests

2 participants