This repository has been archived by the owner on Apr 21, 2022. It is now read-only.
Throw error when top-level package.json is missing #87
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
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
This add an error case when loading the package manifest and the file doesn't exist. Now instead of failing on an undefined TypeError when
this.manifestis undefined or null later in the command, it fails with an uncaught error with a message of "No top-level package.json manifest found.".Right now this shows up as an uncaught error with a stacktrace and everything, but if it's better to print this with
console.errorand then end the process I can make those changes.Fixes #76