np - npm Package Compare versions

Comparing version 2.7.0 to 2.8.0

index.js

		@@ -115,3 +115,4 @@ 'use strict';
		title: 'Bumping version',
		task: () => exec('npm', ['version', input])
		// Specify --force flag to proceed even if the working directory is dirty as np already does a dirty check anyway
		task: () => exec('npm', ['version', input, '--force'])
		},
		@@ -118,0 +119,0 @@ {

package.json

		{
		"name": "np",
		"version": "2.7.0",
		"version": "2.8.0",
		"description": "A better `npm publish`",
		@@ -5,0 +5,0 @@ "license": "MIT",

readme.md

		@@ -84,5 +84,19 @@ # np [![Build Status](https://travis-ci.org/sindresorhus/np.svg?branch=master)](https://travis-ci.org/sindresorhus/np)

		### Public scoped packages

		To publish [scoped packages](https://docs.npmjs.com/misc/scope#publishing-public-scoped-packages-to-the-public-npm-registry) to the public registry, you need to set the access level to `public`. You can do that by adding the following to your `package.json`:

		```json
		"publishConfig": {
		"access": "public"
		}
		```

		### Initial version

		For new packages, start the `version` field in package.json at `0.0.0` and let `np` bump it to `1.0.0` or `0.1.0` when publishing.


		## License

		MIT © [Sindre Sorhus](https://sindresorhus.com)

Improved metrics