Conversation
Ethan-Arrowood
approved these changes
Jan 20, 2026
| }); | ||
| if (out.stderr) { | ||
| log.error(out.stderr); | ||
| log.warning(out.stderr); |
There was a problem hiding this comment.
Why this change? I assume stderr should go be error normally.
Member
Author
There was a problem hiding this comment.
Yeah, that was my initial reason for doing it like this, but in reality it turns out that output is largely unnecessary unless npm exits non-zero, most of what it outputs there is warning text. This will still be output to stderr IIRC, but it will be hidden by default unless you pass --verbose.
Not strongly opinionated on this, but in the place we are using this the output feels out of place.
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
2 participants
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.
Just a few small log cleanup bits.