feat: create exit handler class #7442
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR refactors
exit-handler.jsto be a class so that it can more easily track its internal state. It uses this state to now fully distinguish between 3 states: npm never being set, npm not loaded, and exit handler never called. There are some new error messages shown via console.error if we know we are in an unexpected state.This also continues the refactoring started in #7415 to separate concerns between
npmandCLI. Identifying the error message and logging it have been move tonpmbut catching that error and setting theprocess.exitCodeare still handled inexit-handler.jsandcli/entry.js.It also moves
command.cmdExectonpmsince it never called from within anycommandinstance. This letsnpmonly ever callcommand.execorcommand.workspaceExecnow.