Prompt if publishing scoped package fails with private error. #16
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
Publishing a scoped package defaults to `--access private` on the NPM registry for new packages (unless the package has setup a `publishConfig` property to indicate public access). This commit detects that specific failure and prompts the user to see if they really meant to publish it as a public package. There is no default value for the confirmation prompt (meaning you **must** answer either "Yes" or "No") in order to avoid an accidental private information leak.
This was referenced Mar 30, 2020
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.
Publishing a scoped package defaults to
--access privateon the NPM registry for new packages (unless the package has setup apublishConfigproperty to indicate public access).This commit detects that specific failure and prompts the user to see if they really meant to publish it as a public package. There is no default value for the confirmation prompt (meaning you must answer either "Yes" or "No") in order to avoid an accidental private information leak.