馃悰 Fix #600: Unexpected end of json input #645
Merged
Conversation
This file contains 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
NPM is mixing json with human readable error messages (npm/cli#2740) and refuse to fix it because they want more time to plan (npm/cli#3437). This provides a temporary fix by simply filtering out every line that starts with `npm ERR!` so we have a clean JSON input. As a side effect, this will be broken when attaching a debugger to the process, but that would have been broken without this fix.
|
CI is failing |
|
That should fix it |
|
I'm getting this error too, there 馃槄: https://gitlab.com/201flaviosilva/utilsjs |
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.
NPM is mixing json with human readable error messages (npm/cli#2740)
and refuse to fix it because they want more time to plan (npm/cli#3437).
This provides a temporary fix by simply filtering out every line that starts
with
npm ERR!so we have a clean JSON input.As a side effect, this will be broken when attaching a debugger to the
process, but that would have been broken without this fix.
Note: I have not added a test, but I can try if you find that they are necessary.
Fixes #600