{{ message }}
fix: Proper way of finding npm pack filename output.#3460
Open
ovcharenko wants to merge 1 commit into
Open
Conversation
Member
|
the other branch which tried to solve this is here and my recommendation: #3259 (comment) |
Sorry, something went wrong.
Author
That doesn't help much IMHO, because the JSON is part of other noisy output. So instead of one-line fix you will have to find JSON object and handle all error parsing. |
Sorry, something went wrong.
Member
|
pretty sure in json mode it does a better job of obscuring the nonsense |
Sorry, something went wrong.
Author
19d0b42 should do this, right? |
Sorry, something went wrong.
asottile
reviewed
May 23, 2025
bbabec2 to
928edc0
Compare
September 26, 2025 15:51
asottile
reviewed
Oct 2, 2025
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
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.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.
That will fix pollution of installation path with TypeScript output: