$ npm install --global np
$ np --helpUsage$ np <version>Version can be:patch | minor | major | prepatch | preminor | premajor | prerelease | 1.2.3Options--any-branch Allow publishing from any branch--no-cleanup Skips cleanup of node_modules--yolo Skips cleanup and testing--no-publish Skips publishing--tag Publish under a given dist-tagExamples$ np$ np patch$ np 1.0.2$ np 1.0.2-beta.3 --tag=beta
np without arguments to launch the interactive UI that guides you through publishing a new version.
You can use any of the test/version/publish related npm lifecycle hooks in your package.json to add extra behavior.
For example, here we build the documentation before tagging the release:
sign-git-tag npm config to have the Git tag signed:
$ npm config set sign-git-tag true
You can use
np for packages that aren't publicly published to npm (perhaps installed from a private git repo).
"private": true in your
package.json and the publish step will be skipped. All other steps
including versioning and pushing tags will still be completed.
To publish scoped packages to the public registry, you need to set the access level to
public. You can do that by adding the following to your
registry option in package.json to the URL of your registry:
If you use a Continuous Integration server to publish your tagged commits, use the
--no-publish flag to skip the publishing step of
For new packages, start the
version field in package.json at
0.0.0 and let
np bump it to
0.1.0 when publishing.
MIT © Sindre Sorhus