Husky to simple-git-hooks migration in mrm #954
Merged
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
mrm
recently migrarted fromhusky
tosimple-git-hooks
. I updated the text according to these changes.This
mrm
migration brought these benefits to users:simple-git-hooks
has 0 dependencies and took 10 KB ofnode_modules
space compared to 1 MB of husky 4.simple-git-hooks
doesn’t read config on everypre-commit
hook call which increases the performance. It uses the husky 5 model when you need explicitly to call a script on config changes. But it is a good trade-off forlint-staged
case. It should give around a 0.5 second performance boost forpre-commit
.Comparison with husky 5:
simple-git-hooks
is smaller than husky 5.package.json
.pinst
dependency for Yarn 2.simple-git-hooks
has out-of-the box Yarn 2 support.I already tested
simple-git-hooks
on Autoprefixer, PostCSS, Browserslist, and my commercial projects (with a big team). Everything works great. Other people reported about successful migration too. @toplenborensimple-git-hooks
maintainer is always open for the changes and answers quickly.