Skip to content

typicode/husky-4-to-8

main
Switch branches/tags

Name already in use

A tag already exists with the provided branch name. Many Git commands accept both tag and branch names, so creating this branch may cause unexpected behavior. Are you sure you want to create this branch?
Code

Files

Permalink
Failed to load latest commit information.
Type
Name
Latest commit message
Commit time
March 21, 2021 21:33
lib
May 8, 2022 23:54
src
May 8, 2022 23:54
March 29, 2021 10:53
February 3, 2021 14:05
February 2, 2021 04:55
February 3, 2021 14:05

husky-4-to-8

Easily migrate your husky 4 config to husky 8

While it should cover most basic migrations, it's recommended to have a look at husky 8 documentation.

If your package.json is not at the same level as .git, please update manually.

Usage

npm

npm install husky@latest --save-dev \
  && npx husky-init \
  && npm exec -- github:typicode/husky-4-to-8 --remove-v4-config

yarn

Yarn 1

yarn add husky@latest --dev \
  && npx husky-init \
  && npm exec -- github:typicode/husky-4-to-8 --remove-v4-config

Yarn 2+

yarn add husky@latest --dev \
  && yarn dlx husky-init --yarn2 \
  && npm exec -- github:typicode/husky-4-to-8 --remove-v4-config

pnpm

pnpm install husky@8 --save-dev \
  && pnpx husky-init \
  && pnpx -- github:typicode/husky-4-to-8 --remove-v4-config

What each command does

husky init sets up Git hooks and updates your package.json scripts (you may want to commit your changes to package.json before running husky init).

husky-4-to-8 creates hooks based on your husky v4 config. If --remove-v4-config is passed, previous config will be deleted (recommended).

Revert

If there's an error during the process, you can clean things up by running:

rm -rf .husky && git config --unset core.hooksPath