view: Better errors when package.json is not JSON#2051
Closed
view: Better errors when package.json is not JSON#2051
Conversation
We show a list of bundled dependencies, there's no need to ALSO show the individual files in each one.
Previously, `npm view <noargs>` was just saying "Invalid package.json" if the package.json file was not JSON, or if it was missing. This errors out with the appropriate error in these cases. Also, no need to read the big clunky 'read-package-json' for this, we're literally just checking for a single field. We can be a bit more efficient here.
darcyclarke
added
release: next
2 tasks
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.
Based on #2050, land that first.
Previously,
npm view <noargs>was just saying "Invalid package.json"if the package.json file was not JSON, or if it was missing.
This errors out with the appropriate error in these cases.
Also, no need to read the big clunky 'read-package-json' for this, we're
literally just checking for a single field. We can be a bit more
efficient here.