How to fix error 'not found husky-run' when committing new code?

Question

When committing on a project that uses Husky, I get an error that says not found husky-run

I checked the package.json and it has husky as a dependency, and I can see the pre-commit hook configuration for Husky in the package.json. So I don't know what to do to fix this. Additionally, other members on my team can commit and husky works for them.

I also tried rm -rf node_modules && npm install and then committing again, but still, I get the same error.

Anyone else have ideas on how to fix this?

I got this after running `yarn install` inside a unix-based Docker container and then committing on Windows. Windows was unable to run the file, even thought it existed. — Ninjakannon, Nov 30 '21 at 01:06

score 110 · Accepted Answer · edited Dec 22 '21 at 06:50

110

To fix this there are two methods, depending on which version of Husky you are already on.

If you're using Husky v4 or lower, do the following:

rm -rf .git/hooks
npm install

For Husky v7 or greater, do the following:

# For NPM
 npm install husky@7 --save-dev \
      && npx husky-init \
      && npm exec -- github:typicode/husky-4-to-7 --remove-v4-config

# For Yarn
 yarn add husky@7 --dev \
  && npx husky-init \
  && npm exec -- github:typicode/husky-4-to-7 --remove-v4-config
# or
 yarn add husky@7 --dev \
  && yarn dlx husky-init --yarn2 \
  && npm exec -- github:typicode/husky-4-to-7 --remove-v4-config

At this point you should be able to commit and have your hooks working again.

If anything goes wrong, please read the documentation for migration from 4 to 7.

edited Dec 22 '21 at 06:50

PURGEN

47
8

answered Feb 17 '21 at 17:00

frosty

21,036
7
52
74

1

Thanks, it worked for me, `npm install` step wasn't required. Using yarn here – Luiz Lelis May 14 '21 at 17:47
@dspacejs actually this solution worked for yarn too. Try to first delete your node_modules manually then reinstall. – Paul Razvan Berg May 17 '21 at 18:49
I'm always wary of solution with command line starting by `rm -rf`. Nuking a whole directory sound a bit much, especially when there is a migration script. – Édouard Lopez May 19 '21 at 12:59
this didn't work for me, git hooks directory was not recreated – Nathan Loyer Jun 23 '21 at 14:49
1

OK so this might have worked just fine for husky version 4 or older, but if you've upgraded to husky 6 then you need to follow the answer from Uladz Kha below. – Nathan Loyer Jun 23 '21 at 16:18
2

this did it for me – ied3vil Jun 24 '21 at 14:04
1

Thankyou - worked a treat - FYI use `rm -Recurse -Force .git/hooks` for Powershell – Preet Sangha Sep 29 '21 at 23:20

score 18 · Answer 2 · answered Apr 30 '21 at 12:12

18

To fix this in husky version 6 run:

yarn husky install

answered Apr 30 '21 at 12:12

Zeeshan Ali

254
2
7

score 10 · Answer 3 · edited Apr 25 '21 at 18:25

10

Do not delete .get/hooks hooks won't work. According migrating manual from 4 to 6 version :

For npm usage execute

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

For yarn usage:

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

and

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

If any errors while the process you can simply revert changes by executing:

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

Explanation what's going on:

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-6 creates hooks based on your husky v4 config. If --remove-v4-config is passed, previous config will be deleted (recommended).

edited Apr 25 '21 at 18:25

marc_s

732,580
175
1,330
1,459

answered Apr 21 '21 at 08:27

Uladz Kha

2,154
4
40
61

5

FYI People, you need **npm version 7** to run the last script in this thing. – Ashfaq nisar Jun 08 '21 at 19:27
1

I concur, needed npm version 7 to get this to work. After I ran the scripts, I reverted to npm 6 and nodejs 12 and things are still functioning correctly for me. Also this section of their help docs can help you update your scripts to work with husky@6: https://typicode.github.io/husky/#/?id=migrate-from-v4-to-v6 – Nathan Loyer Jun 23 '21 at 16:20
i have npm 6 and node 10 beause of project limitations. probably thats why it broke for me... – ied3vil Jun 24 '21 at 14:05
please try to `yarn husky install` for npm 6 – Uladz Kha Jun 24 '21 at 14:20
ALSO make sure you are on `git` version 2.9 or above ✅ (I was not and Husky 6 was not working after going through the migration cli steps). Found this little detail tucked in the fine print of the Husky migration docs and this resolved it. – Lauren Jun 24 '21 at 22:21

Kevin Goedecke · Answer 4 · 2022-03-08T23:36:27.427

7

I simply had to add a prepare script to my package.json:

"scripts": {
  ...
  "prepare": "husky install",
  ...
}

Then run yarn install or npm install and husky will be initialized. This will make sure people who check out your repo will also be able to run husky.

edited Mar 08 '22 at 23:36

answered Dec 11 '21 at 00:00

Kevin Goedecke

1,553
2
14
26

score 4 · Answer 5 · answered May 19 '21 at 11:56

4

just a "yarn install" solved this for me

answered May 19 '21 at 11:56

Ravi Kumar

61
4

score 4 · Answer 6 · answered May 08 '22 at 21:24

4

This worked for me:

add a file ~/.huskyrc if you don't have one already

touch ~/.huskyrc
open ~/.huskyrc
paste the following:

# ~/.huskyrc
# This loads nvm.sh and sets the correct PATH before running hook
export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

answered May 08 '22 at 21:24

Ayman Bakri

111
1
3

This one worked for me with `husky@4` Ty – user9869932 Apr 13 '23 at 22:22

score 2 · Answer 7 · answered Nov 03 '22 at 03:44

I occur this problem because the .git folder is at a different level from the package.json file, I resolved it by referencing this document:

https://typicode.github.io/husky/#/?id=custom-directory

Just like this:

// package.json
{
  "scripts": {
    "prepare": "cd .. && husky install front/.husky"
  }
}

score 0 · Answer 8 · answered Nov 23 '21 at 22:49

0

just this 'yarn add husky@6 --dev' inside your terminal

answered Nov 23 '21 at 22:49

Owamamwen

61
3

score 0 · Answer 9 · answered Jun 15 '22 at 15:55

If it may help anyone experiencing this issue and using yarn, uninstalling and reinstalling the husky package has fixed it in my case.

(Please check if you would need -W flag else remove it from the commands)

uninstall:

 yarn remove husky -W

install:

 yarn add husky@^4.2.5 -W //to install a specific version
 
 (or)
 
 yarn add husky -W //to install the latest version

score 0 · Answer 10 · answered Apr 12 '23 at 00:14

Adding to Ayman Bakri's answer, and based on this gist, if you are using a git frontend like Fork together with asdf and you are getting errors like npx: command not found, then you have to source asdf.sh in your ~/.huskyrc as follows:

source /usr/local/opt/asdf/libexec/asdf.sh

if you installed asdf via a package manager like homebrew, or:

source ~/.asdf/asdf.sh

if you installed asdf using the instructions. You must source the bash compatible script asdf.sh even if your default shell is Fish.

How to fix error 'not found husky-run' when committing new code?

10 Answers10

Linked