can-npm-publish - npm Package Compare versions

Comparing version 1.3.2 to 1.3.3

bin/cmd.js

@@ -8,3 +8,3 @@ #!/usr/bin/env node
     Usage
-      $ can-npm-publish [directory|pacakge.json path]
+      $ can-npm-publish [directory|package.json path]
 
@@ -11,0 +11,0 @@ Options

lib/can-npm-publish.js

@@ -90,6 +90,6 @@ // MIT © 2018 azu
         if (name === undefined) {
-            return Promise.reject(new Error("This package has not `name`."));
+            return Promise.reject(new Error("This package has no `name`."));
         }
         if (version === undefined) {
-            return Promise.reject(new Error("This package has not `version`."));
+            return Promise.reject(new Error("This package has no `version`."));
         }
@@ -96,0 +96,0 @@ return viewPackage(name, registry).then(versions => {

package.json

 {
   "name": "can-npm-publish",
-  "version": "1.3.2",
+  "version": "1.3.3",
   "description": "A command line tool that check to see if `npm publish` is possible.",
@@ -5,0 +5,0 @@ "keywords": [

README.md

@@ -23,3 +23,3 @@ # can-npm-publish [![Build Status](https://travis-ci.org/azu/can-npm-publish.svg?branch=master)](https://travis-ci.org/azu/can-npm-publish)
     Usage
-      $ can-npm-publish [directory|pacakge.json path]
+      $ can-npm-publish [directory|package.json path]
 
@@ -26,0 +26,0 @@ Options

No alert changes

Worsened metrics

Total package byte prevSize

9552

decreased by-0.02%

No dependency changes