feat: improve NonZeroExitError message#151
Open
bluwy wants to merge 4 commits into
Open
Conversation
43081j
reviewed
Jun 26, 2026
43081j
reviewed
Jun 26, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
The default printed error message is a bit wordy and doesn't provide a lot of information. I fixed this by displaying the command that caused the error, and hide the
resultfrom the logs by making it non-enumerable.Ideally, we don't pass the entire process object willy nilly, but it could potentially break users who would access it even if untyped. I went with the least breaking approach for now but making it non-enumerable.
Also, I made
exitCodenon-nullable. Since it's calledNonZeroExitError, there's already an exit code.With:
Before:
After: