Command "husky-run" not found.

[budarin]

Just have upgraded from v4.3.8 to v5.0.9 and got the error

have tried to uninstall/install husky, remove npde_modules - nothing helped

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
error Command "husky-run" not found.

[Milo123459]

Can confirm. This is so ridiculously annoying. Here is my solution

[typicode]

Hi @budarin,

Could you provide steps to reproduce the issue? Also are you using Git 2.9+?

[budarin]

git version 2.30.0 (2.30.0.windows.2)

steps to reproduce - upgrade husky to the latest ver.
on both platforms: Windows and MacOS

[Milo123459]

Git version: 2.30.0.windows.2, if this is required for git 2.9+ then there needs to be support for older versions

[typicode]

Hmm, can't try right now on Windows. But here are the steps I've done and it seems to work. Let me know if I'm missing something.

/tmp/foo main
❯ git init
Initialized empty Git repository in /tmp/foo/.git/

/tmp/foo main*
❯ npm init -y
Wrote to /tmp/foo/package.json:

{
  "name": "foo",
  "version": "1.0.0",
  "main": "index.js",
  "scripts": {
    "test": "echo \"Error: no test specified\" && exit 1"
  },
  "keywords": [],
  "author": "",
  "license": "ISC",
  "devDependencies": {
    "husky": "^4.3.8"
  },
  "dependencies": {},
  "description": ""
}



/tmp/foo main*
❯ npm install husky@4 -D

> husky@4.3.8 preuninstall /tmp/foo/node_modules/husky
> node husky uninstall

husky > Uninstalling git hooks
husky > Done

> husky@4.3.8 install /tmp/foo/node_modules/husky
> node husky install

husky > Setting up git hooks
husky > Done

> husky@4.3.8 postinstall /tmp/foo/node_modules/husky
> opencollective-postinstall || exit 0

Thank you for using husky!
If you rely on this package, please consider supporting our open collective:
> https://opencollective.com/husky/donate

npm WARN foo@1.0.0 No description
npm WARN foo@1.0.0 No repository field.

+ husky@4.3.8
updated 1 package and audited 47 packages in 1.883s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities


/tmp/foo main*
❯ npm install husky@5 -D

> husky@4.3.8 preuninstall /tmp/foo/node_modules/husky
> node husky uninstall

husky > Uninstalling git hooks
husky > Done
npm WARN foo@1.0.0 No description
npm WARN foo@1.0.0 No repository field.

+ husky@5.0.9
removed 46 packages, updated 1 package and audited 1 package in 0.67s

1 package is looking for funding
  run `npm fund` for details

found 0 vulnerabilities


/tmp/foo main*
❯ npx husky install
husky - Git hooks installed

/tmp/foo main*
❯ npx husky add .husky/pre-commit "echo hello && exit 1"
created .husky/pre-commit

/tmp/foo main*
❯ git add package.json

/tmp/foo main*
❯ git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
hello
husky - pre-commit hook exited with code 1 (error)

[Milo123459]

^ After downgrading and building again, it just, doesn't work. I've got an idea but a faint one.

[Milo123459]

Alright, figured out how to fix it.

Firstly, we need to remove .git/hooks.

For me, I ran typicodes husky-4-to-5, which worked like a charm.

Then, run yarn / npx husky install.

Viola, should work. You can check out my repo to check out how I did it.

Some additional resources:
From my testing, you can not add a .sh or any file extension to the end of a hook file.
Add a hook using yarn husky add '.husky/hook-name' 'optional content here' (or npx)
How you can run commitlint:

#!/bin/sh
. "$(dirname "$0")/_/husky.sh"

echo '$ commit-msg' 
echo '$ yarn commitlint -e $1'
yarn commitlint -e $1

Have a great day. 👋

Leave me a comment if this helped you out!

[mo-sharif]

Thanks, @Milo123459 your suggestion works like a charm 🙌

[Milo123459]

Glad it does 😉

[budarin]

Alright, figured out how to fix it.

Firstly, we need to remove .git/hooks.

For me, I ran typicodes husky-4-to-5, which worked like a charm.

Then, run yarn / npx husky install.

Viola, should work. You can check out my repo to check out how I did it.

Have a great day. 👋

Leave me a comment if this helped you out!

it did not help me :(
after reinstalling husky - it does not create /hooks folder in .git

[Milo123459]

What's happened meaning it didn't work?
Can you send me if it errors?

[budarin]

What's happened meaning it didn't work?
Can you send me if it errors?

there were no errors - hooks folder had not been created with husky

[Milo123459]

Try, npx husky install.

[budarin]

Try, npx husky install.

You could see that husky does not recreate hooks folder during installation

[Milo123459]

Try yarn husky install

[budarin]

but my previous hooks are lost!!! :(
my commitizen hooks are out of husky flow

[Milo123459]

Firstly, don't close this issue, it'll be helpful for other users.
Secondly, they should still be in your package.json

[Milo123459]

Did you run husky 4 to 5?

[budarin]

Firstly, don't close this issue, it'll be helpful for other users.
Secondly, they should still be in your package.json

they are in package.json but not used with husky in commit process

[Milo123459]

yarn husky add .husky/hook-name "script to run"

[budarin]

Did you run husky 4 to 5?

23 verbose stack Error: could not determine executable to run
23 verbose stack     at getBinFromManifest (C:\Program Files\nodejs\node_modules\npm\lib\exec.js:264:23)
23 verbose stack     at exec (C:\Program Files\nodejs\node_modules\npm\lib\exec.js:178:15)
24 verbose cwd C:\Users\Мастер\AppData\Local\npm-cache\_cacache\tmp\git-clone-bc12e66d

[budarin]

yarn husky add .husky/hook-name "script to run"

I used to use huskyrc.js - now it's useless?

[Milo123459]

Yes.

[Milo123459]

Did you run husky 4 to 5?

23 verbose stack Error: could not determine executable to run

23 verbose stack     at getBinFromManifest (C:\Program Files\nodejs\node_modules\npm\lib\exec.js:264:23)

23 verbose stack     at exec (C:\Program Files\nodejs\node_modules\npm\lib\exec.js:178:15)

24 verbose cwd C:\Users\Мастер\AppData\Local\npm-cache\_cacache\tmp\git-clone-bc12e66d

I node version?

[budarin]

Did you run husky 4 to 5?

23 verbose stack Error: could not determine executable to run

23 verbose stack     at getBinFromManifest (C:\Program Files\nodejs\node_modules\npm\lib\exec.js:264:23)

23 verbose stack     at exec (C:\Program Files\nodejs\node_modules\npm\lib\exec.js:178:15)

24 verbose cwd C:\Users\Мастер\AppData\Local\npm-cache\_cacache\tmp\git-clone-bc12e66d

I node version?

v15.8.0

[Milo123459]

Never mind on that, just convert everything to .husky/hook

[budarin]

do
yarn husky add .husky/pre-commit "lint-staged"

then try to commit - got the error:

> git -c user.useConfigOnly=true commit --quiet --allow-empty-message --file -
.husky/pre-commit: line 4: lint-staged: command not found
husky - pre-commit hook exited with code 127 (error)

[Milo123459]

Replace lint-staged with yarn lint-staged

[inhaq]

@PaulMEdwards yup, using yarn but you can use npx as well mentioned above by @Milo123459

[Milo123459]

There probably is a way to isolate the sh files like package.json scripts, but it'll have to work for pnpm and yarn v2 which is a pain.

[shellscape]

Can confirm that the latest version of 5.x is broken again with pnpm. Looking at issues between pnpm and husky repos, this seems to pop up as an issue at least once a year. Can't help but wonder if something can be done to prevent these regressions. Also confirming that v4.3.8 does still work with pnpm.

[Milo123459]

pnpx. Use pnpx.

[shellscape]

@Milo123459 that's a workaround, not a solution. I'd expect husky to behave the same on install between 4.x and 5.x. As it is, it's broken.

[Milo123459]

It's not pnpms fault. It's husky's. The script just has to be isolated like the npm scripts are. I'm sure there is a way to do that.

Also, at least it works, better then nothing! 😅

[shellscape]

We're on the same page there, saying the same thing in different ways 👍

[SalahAdDin]

Initially, followed @Milo123459 and deleted .git/hooks and then was getting an error in following the next steps and git was committing code without hooks. Then tried yarn husky install and yarn husky add .husky/pre-commit "lint-staged" it worked. btw node is v15.8.0

Well, this does not work for me, hooks are not working now.

@Milo123459 that's a workaround, not a solution. I'd expect husky to behave the same on install between 4.x and 5.x. As it is, it's broken.

Indeed it is.

[Milo123459]

@SalahAdDin try yarn lint-staged as seen in my example.

[SalahAdDin]

I solved it by the GitKraken related issue.

[kevinschaffter]

@SalahAdDin Can you post that issue here and your fix?

[typicode]

To fix husky-run not found, install husky 5 and run husky init script:

With yarn:

yarn add husky -D && yarn husky init

With pnpm:

pnpm add husky -D && pnpx husky install

It will set up hooks and create a pre-commit hook that you can edit in .husky/pre-commit. If you want to add another hook, it's highly recommended to use husky add ... command.

Optionally, you can delete .git/hooks to remove artifacts from husky 4 (it's automatically done if you upgrade with npm).

There's also section for migrating from husky 4 to 5 in the docs:
https://typicode.github.io/husky/#/

Hope this helps :)

[SalahAdDin]

@SalahAdDin Can you post that issue here and your fix?

Issue and fix: #875

[shellscape]

@typicode running yarn husky init results in the following:

Usage
  husky install [dir] (default: .husky)
  husky uninstall
  husky set|add <file> [cmd]

You closed this issue with bad info.

[Milo123459]

That looks like husky6, this issue covered husky 5..

[SalahAdDin]

That looks like husky6, this issue covered husky 5..

No way, Husky 6?

[guaizi149]

package.json
add "prepare": "npx husky install",

[sourceful-julian]

I found this very helpful for mac osX - https://dev.to/studiospindle/using-husky-s-pre-commit-hook-with-a-gui-21ch
Creating a huskyrc in the home directory and adding the path to your local/user npm files (PATH="/usr/local/bin:/Users/julian/.npm/bin:$PATH") fixed the problems I had with husky not being able to find yarn despite having the npm/bin path in my global PATH

[asvetlenko]

I have the same issue: