sh: husky: command not found

Question

I've setup a node project with husky but when my collegue tries to run npm install on his Mac he gets the following error :

noa-be@1.0.0 prepare
husky install

sh: husky: command not found
npm ERR! code 127
npm ERR! path /Users/X/Desktop/Workspace/project
npm ERR! command failed
npm ERR! command sh -c husky install

npm ERR! A complete log of this run can be found in:
npm ERR!     /Users/X/.npm/_logs/2021-04-12T13_07_25_842Z-debug.log

These are the relevant package.json parts:

{
    "scripts": {
        "prepare": "husky install"
    },
    "devDependencies": {
        "husky": "^5.2.0",
    }
}

I thought this would be enough for husky to be installed when running npm install, but it's not. What am I missing?

score 155 · Answer 1 · answered May 17 '22 at 18:47

155

If you are using nvm, you might want to create a file called .huskyrc in your home directory and add the following lines of code to it:

~/.huskyrc

export NVM_DIR="$HOME/.nvm"
[ -s "$NVM_DIR/nvm.sh" ] && \. "$NVM_DIR/nvm.sh"

answered May 17 '22 at 18:47

Hossein Mousavi

3,118
3
16
35

12

You are legendary, sir. – TetraDev Jul 28 '22 at 17:13
2

looking all over the internet and found this awesome solution. thanks! – Fahmi Jabbar Aug 10 '22 at 12:19
1

Also, don't forget to install husky on the devDependencies. – Shamim Hossain Oct 17 '22 at 20:04
4

LEGENDARY, I HAVE BEEN LOOKING FOR THIS SOLUTION FOR ALMOST 6 MONTHS. THANKS – ImBIOS Dec 19 '22 at 03:08
1

I would also like to thank you very much so...you absolute LEGEND!!! – Shane O'Moore Jan 31 '23 at 08:54
Does this apply to Windows? If so, where is this `home` file exactly? – JP Strydom Feb 07 '23 at 13:33
1

I go the following error message when trying to commit from IntelliJ (worked fine directly from terminal): `.husky/pre-commit: 4: npm: not found`. Your suggestion fixed my issue. Thanks! – Lyannic Mar 11 '23 at 13:13
1

you deserve an oscar – Leonardo Cavalcante Apr 02 '23 at 18:16
1

worked. you sir beats chatgpt – STEEL Aug 23 '23 at 09:33
1

Commits were working fine for me using CLI, but Tower.app was complaining with an error. After I added this Tower was able to commit. – Brian Litzinger Aug 24 '23 at 13:48

score 23 · Answer 2 · answered Oct 20 '21 at 19:02

23

I was struggling with the same exact problem for hours. Finally, I could install dependencies and start working on my project by doing this:

Temporarily remove the "prepare": "husky install" script from the package.json file.
Run npm i (npm install). Dependencies installed successfuly.
Add again the "prepare" script that you removed in step 1.
Run again npm i to install the husky git hooks, so husky can do its job from now on.

answered Oct 20 '21 at 19:02

David Ferreira

1,233
17
24

Thank you so much. Any idea the reasoning behind why we have to remove prepare and why husky isn't built in a way to avoid this? – Evan Erickson May 30 '23 at 14:58

score 16 · Answer 3 · answered Feb 23 '22 at 18:36

16

This error is also thrown by npm ci if the NODE_ENV is set to "production" pre-install

answered Feb 23 '22 at 18:36

lukejkw

1,054
13
19

2

Good point. I'd like to see this as a comment near the question as it's not a real answer to the issue – dance2die May 28 '22 at 14:47

score 14 · Answer 4 · answered Jul 25 '22 at 15:14

14

Faced this issue in Github Desktop.

solved it by quit Github Desktop and re-open it.

answered Jul 25 '22 at 15:14

Itay Tur

683
1
15
40

2

Thanks. :D Took me too long to figure this out. – Mika Aug 09 '22 at 12:33
2

That's the right answer lol. Thanks! – thodwris Apr 10 '23 at 19:10
2

your answer is gold I ran into this today :D – Abigail Nguyen Apr 21 '23 at 01:39

score 11 · Accepted Answer · answered Jul 19 '21 at 20:05

I've been able to solve the problem by upgrading to latest Husky version (7.0.1, from 5.2.0).

Git was also helpful, and told me that the files weren't executables. (Git V 2.24.1)

So I give them executable rights :

chmod +x PATH_TO_HUSKY_FILE

You'll need to execute this command for every hooks

score 9 · Answer 6 · answered Jun 14 '22 at 13:00

9

It worked in my terminal but not in VSCode version control. So had to force quite the vscode app and restarting it worked.

answered Jun 14 '22 at 13:00

Norfeldt

8,272
23
96
152

Yep, this fixed it in vscode. Why...like most broken things, it doesn't pay to figure it out. – James May 29 '23 at 16:30
It fixed in my case, MacOS Ventura M2, zsh (oh-my-zsh) with fnm and starship. – ImBIOS Jun 25 '23 at 14:47

score 8 · Answer 7 · answered May 05 '21 at 19:36

I believe it could be version specific issue. Install version 6, npm i husky@6.0.0 --save-dev, and it should work as the husky doc says.

Apparently, when I did npm i husky --save-dev, it was installing "husky": "^0.8.1" for me for some strange reason, giving me the exact same error: sh: husky: command not found.

Method 1:

Update manually, in your package.json:

{
    "scripts": {
        "prepare": "husky install",
        "create-hook": "husky add .husky/pre-commit \"npm test\"",
    }
}

Then, run npm run prepare && npm run create-hook.

It should create .husky directory with .pre-commit file in it.

Method 2:

npx husky install

npm set-script prepare "husky install"

npx husky add .husky/pre-commit "npm test"

score 2 · Answer 8 · answered Aug 29 '22 at 05:24

2

I was able to fix this by providing an explicit location for husky

  "scripts": {
    "prepare": "node_modules/.bin/husky-run install"
  },

answered Aug 29 '22 at 05:24

dtruong0

41
5

score 0 · Answer 9 · answered Nov 29 '22 at 23:51

Using Lerna

When I upgraded husky from version 4 to 8 there was information todo first pre commit manually. For this purpose pre-commit bash script was generated in .husky directory.

What I had todo was simply run the command included in this file:

lerna run precommit --concurrency 2 --stream

score 0 · Answer 10 · answered Apr 25 '23 at 16:09

What .huskyrc needs to do is:

Check if there is a .nvmrc file in the working directory
Run the nvm.sh script
Run nvm use, so all node related executables (eg: yarn) will be ready to use

Thus, here is a version of .huskyrc that fulfil those requisites:

export NVM_DIR="$HOME/.nvm"

if [ -f .nvmrc ] && [ -s "$NVM_DIR/nvm.sh" ];
then
  . "$NVM_DIR/nvm.sh"
  nvm use
fi;

score 0 · Answer 11 · answered May 05 '23 at 11:42

0

In case you're facing this issue while installing the production dependencies you can use this solution

npm set-script prepare '' && npm install --omit=dev

answered May 05 '23 at 11:42

Abdelrahman Ismail

106
6

score 0 · Answer 12 · answered Aug 18 '23 at 15:29

0

For peoples in Windows using WebStorm, Gitkraken etc... if you encounter this error, try to setup C:\Program Files\Git\bin for Path in Environment Variables System. It may help you. Do not forget to restart IDE/terminal after it.

answered Aug 18 '23 at 15:29

Alexander Gvozd

121
1
6

sh: husky: command not found

12 Answers12

Using Lerna

Linked

Related