Add publish script to package.json #1
Conversation
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
Might just be me but I found myself running npm publish without ./package and messing up my package a few times. This PR adds a publish script that publishes the ./package directory. And npm run publish is 6 characters shorter than npm publish ./package so that's a plus point too. Of course, it assumes that the user hasn't replaced npm completely with another package manager, but if they have then they could very easily change it when they visit package.json to change the package name.
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.
Might just be me but I found myself running
npm publishwithout./packageand messing up my package a few times. This PR adds a publish script that publishes the ./package directory. Andnpm run publishis 28.5% shorter thannpm publish ./packageso that's a plus point too.Of course, it assumes that the user hasn't replaced npm completely with another package manager, but if they have then they could very easily change it when they visit package.json to change the package name.