Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Ignore exit codes from "npm list --json" as they can be misleading #56

Merged
merged 1 commit into from Nov 20, 2013

Conversation

domcleal
Copy link
Contributor

@domcleal domcleal commented Nov 7, 2013

Instead just try and parse the JSON on stdout. If the command doesn't
produce JSON fail, then the error handler still exists. Bugs in npm or
packaging like https://bugzilla.redhat.com/show_bug.cgi?id=986422 can
cause package lists to come back empty even if the error's harmless.

Instead just try and parse the JSON on stdout.  If the command doesn't
produce JSON fail, then the error handler still exists.  Bugs in npm or
packaging like https://bugzilla.redhat.com/show_bug.cgi?id=986422 can
cause package lists to come back empty even if the error's harmless.
apenney pushed a commit that referenced this pull request Nov 20, 2013
Ignore exit codes from "npm list --json" as they can be misleading
@apenney apenney merged commit 5f63895 into voxpupuli:master Nov 20, 2013
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants