husky-4-to-8
husky-4-to-8 copied to clipboard
typicode
Quickly migrate your hooks from husky v4 to husky@latest
Hi there, Trying to upgrade Husky from 4 to 8 in a project, running into a 404 Not Found when running `npm exec -- github:typicode/husky-4-to-8 --remove-v4-config`. Node version: 16.13.2 npm...
Is it normal this error? ```shell git:(dev) ✗ yarn add husky@latest --dev \ > && yarn dlx husky-init --yarn2 \ cmdand> && npm exec -- github:typicode/husky-4-to-7 --remove-v4-config yarn add v1.22.5...
https://github.com/typicode/husky-4-to-6/blob/c9bbca76eeaec8a91a5dfd1095a9907114623e47/README.md#L16 ^ that requires `npm@7` which does not ship with any current LTS release of Node.js.
`npm exec` is only in npm 7. Added snippet uses npx for older version users :)
The update command turfed the commit msg command into `commitlint -E HUSKY_GIT_PARAMS` which yielded > Error: Received 'HUSKY_GIT_PARAMS' as value for -E | --env, but environment variable 'HUSKY_GIT_PARAMS' is not...
`npm exec` doesn't seem to work with `npm 6`. `npx`, OTOH, does the job just fine.
Hey, I just wanted to leave a note that the README assumes someone's on a *nix system, so the multi-line instructions should probably be written as three separate lines. After...
`npm exec` is new with NPM 7, so it errors with NPM 6. `npx` will work with npm 6 and 7.
yarn instructions: yarn add husky@6 --dev \ && npx husky-init \ && npm exec -- github:typicode/husky-4-to-6 --remove-v4-config the npm exec just shows help screen when it gets to it npx:...
