sh: husky: command not found

[GaelFerrand]

Context

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?

Thank you!

[flo-sch]

Seems odd, is husky successfully being installed in the node_modules folder?

(Is there nothing in his environment preventing devDependencies to be installed?)

[GaelFerrand]

Husky is in the node_modules!

[DoctorDerek]

Is he running the command as simply prepare? It's a bit hard to tell from the code you shared.

When you do npm run prepare then it uses the local node_modules folder on the path, in the same that npx husky install would work.

[DoctorDerek]

I saw a similar error when I tried to commit a change without having run npm install in the current working directory, but it wasn't a husky issue -- it was husky itself flagging prettier as missing.

[rdmeal]

I had a very similar error message to this when running npm install inside a Docker container and it was down to the node environment being set to production - see #914 for more information and a possible solution.

[alexbu92]

Having this problem also, no solution found. husky is in node_modules.

[chandelieraxel]

For me, the problem was husky file not being executables by default. Husky was properly installed AFTER upgrading it to v 7.0.1 ( previous was the 5.2.0 as stated in the issue)

I'm on Mac (not sure if the same happen on other OS), and last git version helped me to identify the problem. (V 2.24.1 as time of writing this).

To give executable right on your file : chmod +x PATH_TO_HUSKY_FILE

You'll need to execute it for every hook you have

[vintprox]

Everything seems alright on local machine, but when I deploy on Heroku, I get this:

...
remote: -----> Installing dependencies
remote:        Installing node modules
remote:
remote:        > drcm-bot@0.1.0 prepare /tmp/build_b8e6fb4d
remote:        > husky install
remote:
remote:        sh: 1: husky: not found
remote:        npm ERR! code ELIFECYCLE
remote:        npm ERR! syscall spawn
remote:        npm ERR! file sh
remote:        npm ERR! errno ENOENT
remote:        npm ERR! drcm-bot@0.1.0 prepare: `husky install`
remote:        npm ERR! spawn ENOENT
...

The problem was that husky, being installed in devDependencies, gets stripped away if you set NPM_CONFIG_PRODUCTION=true.

[stale]

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

[ctsstc]

I'm noticing this same issue, it seems that having it as a devDependency doesn't work if you're only installing production only packages. This seems to have been working fine until I updated npm. Ideally you shouldn't need Husky for a production build though, but does prepare run always? I tried looking up more about it in the npm documentation and it says it runs "locally" but doesn't explain what changes if it's "local" or not.

https://docs.npmjs.com/cli/v8/using-npm/scripts#:~:text=Runs%20on%20local%20npm%20install%20without%20any%20arguments

I can replicate this locally by doing the following which is equivalent to a production build:

> npm install --omit=dev

>project@1.1.1 prepare
> husky install

sh: husky: command not found
npm ERR! code 127
npm ERR! path /Users/coder/projects/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/coder/.npm/_logs/2021-11-30T23_50_31_403Z-debug.log

Seems that moving it to a non-developer dependency may be the way to go for now, or look into some of these options proposed above about gating the execution.

[mindctrl]

I ran into this error. Turns out something on my laptop was setting NODE_ENV="production", and husky wasn't being installed because it's a dev dependency. Setting NODE_ENV to development fixed the problem.

[ctsstc]

I seem to have no problems on a new project on heroku with:

• node: v16.13.2
• npm: 8.1.2
• husky: 7.0.4

On the other project when I originally commented here I ended up doing:

"prepare": "if [[ $NODE_ENVIRONMENT != \"production\" ]]; then husky install; fi"

Note: It was running in a docker container up on AWS.

[raphaelsetin]

@ctsstc That didn't work for me.

The following worked (and is cross platform too):

"prepare": "node -e \"if (process.env.NODE_ENV !== 'production'){process.exit(1)} \" || husky install",