commitplease - npm Package Compare versions

Comparing version 3.1.0 to 3.2.0

index.js

@@ -33,2 +33,5 @@ var fs = require('fs')
 function getProjectPath () {
+  // Rely on npm to inject some path into PATH; However, the injected
+  // path can both be relative or absolute, so add extra path.resolve()
+
   // During npm install, npm will inject a path that ends with
@@ -41,3 +44,3 @@ // commitplease/node_modules/.bin into process.env.PATH
   if (p !== undefined) {
-    return p
+    return path.resolve(p)
   }
@@ -50,3 +53,3 @@
   if (p !== undefined) {
-    return p
+    return path.resolve(p)
   }
@@ -58,3 +61,3 @@
   // https://git-scm.com/docs/githooks/2.9.0
-  return process.cwd()
+  return path.resolve(process.cwd())
 }
@@ -61,0 +64,0 @@

package.json

 {
   "name": "commitplease",
-  "version": "3.1.0",
+  "version": "3.2.0",
   "description": "Validates strings as commit messages",
@@ -5,0 +5,0 @@ "main": "index.js",

README.md

@@ -159,3 +159,3 @@ # Commitplease
   "scripts": {
-    "commitmsg": "commitplease"
+    "commitmsg": "commitplease .git/COMMIT_EDITMSG"
   },
@@ -168,3 +168,3 @@ "commitplease": {
 
-However, since husky does not use npm in silent mode (and there is [no easy way](https://github.com/typicode/husky/pull/47) to make it [do so](https://github.com/npm/npm/issues/5452)), there will be a lot of additional output when a message fails validation. Therefore, using commitplease alone is recommended.
+However, since husky does not use npm in silent mode (and there is [no easy way](https://github.com/typicode/husky/pull/47) to make it [do so](https://github.com/npm/npm/issues/5452)), there will be a lot of additional output when a message fails validation. Moreover, husky will run your `scripts` entry and nothing more, so you have to [specify everything yourself](https://github.com/jzaefferer/commitplease/issues/100) (e.g. the path to the commit message file). Therefore, using commitplease alone is recommended.
 
@@ -171,0 +171,0 @@ ## API

New alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Fixed alerts

License Policy Violation

License

This package is not allowed per your license policy. Review the package's license to ensure compliance.

Found 1 instance in 1 package

Improved metrics

Lines of code

1393

increased by0.14%

Worsened metrics

Total package byte prevSize

52988

decreased by-70.92%

Number of package files

19

decreased by-13.64%

No dependency changes