Comparing version 1.0.0-rc.12 to 1.0.0-rc.13
# CHANGELOG | ||
## 1.0.0-rc.13 | ||
* Show a message when Node can't be found in PATH | ||
## 1.0.0-rc.12 | ||
@@ -4,0 +8,0 @@ |
@@ -31,3 +31,3 @@ # Documentation | ||
If you have a multi-package repository, it's recommended to use tools like [lerna](https://github.com/lerna/lerna) and have `husky` installed ONLY in the root `package.json` to act as the source of truth. | ||
If you have a multi-package repository, it's __recommended__ to use tools like [lerna](https://github.com/lerna/lerna) and have `husky` installed ONLY in the root `package.json` to act as the source of truth. | ||
@@ -71,2 +71,2 @@ Generally speaking, you should AVOID defining `husky` in multiple `package.json`, as each package would overwrite previous `husky` installations. | ||
- if you're running `git` commands in the terminal, husky will use the version defined in your shell `PATH`. So if you're a `nvm` user, husky will use the version that you've set with `nvm`. | ||
- if you're using a GUI tools and `nvm`, GUI tools may have a different `PATH` and not load `nvm`, in this case husky will usually pick the highest `node` version installed by `nvm`. You can also check `~/.node_path` to see which version is used by GUIs. | ||
- if you're using a GUI client and `nvm`, it may have a different `PATH` and not load `nvm`, in this case the highest `node` version installed by `nvm` will usually be picked. You can also check `~/.node_path` to see which version is used by GUIs. |
@@ -17,7 +17,13 @@ "use strict"; | ||
gitParams="$*" | ||
${platform !== 'win32' | ||
? ` | ||
if ! command -v node >/dev/null 2>&1; then | ||
echo "Can't find node in PATH, trying to find a node binary on your system" | ||
fi | ||
` | ||
: ''} | ||
if [ -f $scriptPath ]; then | ||
${node} $scriptPath $hookName "$gitParams" | ||
else | ||
echo "Can't find husky, skipping $hookName hook" | ||
echo "Can't find Husky, skipping $hookName hook" | ||
echo "You can reinstall it using 'npm install husky --save-dev' or delete this hook" | ||
@@ -24,0 +30,0 @@ fi |
@@ -42,3 +42,3 @@ "use strict"; | ||
console.log(); | ||
console.log(`Warning: Setting ${hookName} script in package.json > scripts will be deprecated in v1.0`); | ||
console.log(`Warning: Setting ${hookName} script in package.json > scripts will be deprecated`); | ||
console.log(`Please move it to husky.hooks in package.json, a .huskyrc file, or a husky.config.js file`); | ||
@@ -45,0 +45,0 @@ console.log(`Or run ./node_modules/.bin/husky-upgrade for automatic update`); |
{ | ||
"name": "husky", | ||
"version": "1.0.0-rc.12", | ||
"version": "1.0.0-rc.13", | ||
"description": "Prevents bad commit or push (git hooks, pre-commit/precommit, pre-push/prepush, post-merge/postmerge and all that stuff...)", | ||
@@ -5,0 +5,0 @@ "bin": { |
@@ -84,3 +84,3 @@ # Important: looking for your feedback, [husky survey](https://goo.gl/forms/rvSbDFhR5jLcwDGn2) ❤️ | ||
* [Hotel](https://github.com/typicode/hotel) | ||
* ... and 21k+ [other awesome repos](https://libraries.io/npm/husky/dependent-repositories) :tada: | ||
* ... and 23k+ [other awesome repos](https://libraries.io/npm/husky/dependent-repositories) :tada: | ||
@@ -87,0 +87,0 @@ ## See also |
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
License Policy Violation
LicenseThis package is not allowed per your license policy. Review the package's license to ensure compliance.
Found 1 instance in 1 package
30443
442