husky
9.1.7 · 18 Nov 2024MIT49.9M / weekRepositoryHomepagenpmAtom feed
9.1.7 is the newest release of 9.x.
In short
1 removed1 new8 changed
- removed
Dropped support for Node 14 and 16.
Release note
Kicking off the year with an exciting update!
Note: install using husky@latest to get the bug fixes that were released after.
Introducing husky init
v8
npm pkg set scripts.prepare="husky install" npm run prepare npx husky add .husky/pre-commit "npm test"
v9
Adding husky to a project is now easier than ever. It's just a single line that does the same as above. No need to read the docs to get started anymore.
npx husky init
Adding a New Hook
v8
npx husky add .husky/pre-commit "npm test" git add --chmod=+x .husky/pre-commit # On Windows
v9
Adding a hook is as simple as creating a file. This can be accomplished using your favorite editor, a script or a basic echo command. For example, on Linux/macOS:
echo "npm test" > .husky/pre-commit
Further Size Reduction
v8 was already the most compact Git hooks manager at approximately 6kB.
v9 takes this a step further, reducing the size to just 3kB, likely making it the smallest devDependency in your toolkit.
To give you an idea of how small it is, the biggest file in the project is the MIT license 😄
More to Come
Additional features are in the pipeline for v9. Stay tuned :raised_hands:
Other Changes
Enhanced security with CI and npm
--provenancefor safer publishing.Added
$XDG_CONFIG_HOMEsupport. Move~/.huskyrcto~/.config/husky/init.shfor centralized configuration.Fixed permission issue for Windows-created hooks; they no longer need to be executable.
Removed
husky install. Usehuskyorhusky some/dirfor the same functionality (deprecation notice to be added).Modified behavior when
.gitis missing; it now triggers a warning instead of failure.Replaced
HUSKY_DEBUG=1withHUSKY=2for debugging.Updated the Husky API for module usage.
Transitioned to
ESMfor module usage.- removed
Dropped support for Node 14 and 16.
Revamped docs.
How to Migrate
v9 is backward compatible with v8, allowing you to freely upgrade and migrate your hooks later.
Here are the steps to migrate:
package.json
{
"scripts": {
- "prepare": "husky install"
+ "prepare": "husky"
}
}.husky/pre-commit
- #!/usr/bin/env sh - . "$(dirname -- "$0")/_/husky.sh" npm test
Note: sh will be used to run hooks, even if a shebang is set.
If you were using husky as a module:
- const husky = require('husky')
- // ...
+ import husky from 'husky'
+ console.log(husky())