PR #173 introduced husky to automatically run the pre-commit hook specified in the package.json.
However, that slows down git "drastically" because it needs to run an npm command for every action. (husky registers itself for each possible commit hook).
We should maybe go to a .githooks folder and simply run git config hooks.Path .githooks as part of pre-test or some other command that you are likely to execute locally.
This will ensure the git hooks get installed locally automatically which is the sole reason we would went for husky in the first place.
PR #173 introduced
huskyto automatically run the pre-commit hook specified in thepackage.json.However, that slows down
git"drastically" because it needs to run an npm command for every action. (husky registers itself for each possible commit hook).We should maybe go to a
.githooksfolder and simply rungit config hooks.Path .githooksas part ofpre-testor some other command that you are likely to execute locally.This will ensure the git hooks get installed locally automatically which is the sole reason we would went for
huskyin the first place.