hook fails as it assumes yarn will be available in $PATH #666

detj · 2020-02-06T06:21:04Z

husky misjudges package manager & tried to find yarn while it was upgraded using npx yarn upgrade husky --latest. I don't keep a global yarn & use npx yarn ... for all my yarn needs.

Possible to let the user choose package manager?

.git/hooks/husky.sh

# Run husky-run with the package manager used to install Husky
case $packageManager in
  "npm") run_command npx --no-install;;
  "pnpm") run_command pnpx --no-install;;
  "yarn") run_command yarn run --silent;;
  "*") echo "Unknown package manager: $packageManager"; exit 0;;
esac

Instead of husky inferring which package manager it should use, would it be possible to let the user configure it for husky?

Workaround

npm install -g yarn fixes the error.

$ HUSKY_DEBUG=1 git commit # ...

husky:debug husky v4.2.1 - pre-commit
husky:debug Current working directory is /Users/detj/src/my-project
Can't find yarn in PATH: /Applications/Xcode.app/Contents/Developer/usr/libexec/git-core:...
Skipping pre-commit hook
On branch master
Your branch is ahead of 'origin/master' by 1 commit.
  (use "git push" to publish your local commits)

nothing to commit, working tree clean

OS: macOS 10.15.3

The text was updated successfully, but these errors were encountered:

detj · 2020-03-18T18:31:01Z

would you consider this an issue? or it is pretty much expected to have yarn available in $PATH.

barakyosi · 2020-03-25T10:02:42Z

There's a similar issue when using "husky" with SourceTree.
Getting an error:

Can't find yarn in PATH: /Library/Developer/CommandLineTools/usr/libexec/git-core:/Applications/SourceTree.app/Contents/Resources/bin:/usr/bin:/Applications/SourceTree.app/Contents/Resources/git_local/gitflow:/Applications/SourceTree.app/Contents/Resources/git_local/git-lfs:/usr/bin:/bin:/usr/sbin:/sbin
Skipping pre-commit hook

This error can't be fixed by installing yarn globally. Any idea how to fix it?

BTW - it works with earlier versions of Husky.

axelfriberg · 2020-04-02T14:53:56Z

Getting the same error on husky 4.2.3

Can't find yarn in PATH

Also tried Tower which is another GUI git client and same issue there. So seems like a regression since it worked out of the box with GUI git clients in previous versions.

lewislbr · 2020-04-05T08:49:13Z

Does Husky really need to have locally installed Node and npm/Yarn? It makes it impossible to use with Docker, where I don't have anything in my local machine.

hcharley · 2020-04-08T18:30:49Z

Hmm, I just started running into this on VSCode.

xarvh · 2020-05-17T08:05:03Z

Having the same problem.
In Ubuntu, yarn is available as a package that provides a yarnpkg binary, that I alias as yarn.
Therefore, there is no yarn binary available strictly speaking.

(Why does husky need to know where the binaries are anyway? o_O)

bobrosoft · 2020-06-30T09:55:14Z

Killed 2 hours on trying to figure out what's wrong with Husky pre-commit hook and that Can't find yarn in PATH error.
Switched to husky@3.1.0, all is working there.

armspkt · 2020-06-30T16:55:13Z

sudo launchctl config user path `echo $PATH`

I use this command and everything works fine again.

https://community.atlassian.com/t5/Bitbucket-questions/SourceTree-Hook-failing-because-paths-don-t-seem-to-be-set/qaq-p/274792

j3ko · 2020-08-22T05:16:21Z

Killed 2 hours on trying to figure out what's wrong with Husky pre-commit hook and that Can't find yarn in PATH error.
Switched to husky@3.1.0, all is working there.

I don't think downgrading solves the underlying issue. I downgraded to 3.1.0 and it also skips the hook with this message instead (I am using nvm, not sure if that matters):

Info: can't find node in PATH, trying to find a node binary on your system
husky > pre-commit (node v10.15.1)
ℹ No staged files match any configured task.
Info: can't find node in PATH, trying to find a node binary on your system
Info: can't find node in PATH, trying to find a node binary on your system
Info: can't find node in PATH, trying to find a node binary on your system

both versions work fine on windows.

elalemanyo · 2020-10-16T19:24:21Z

@armspkt I try your command and nothing change... still work for you? What is your OSX version? I am using 10.15.7

tcastelly · 2020-10-20T08:40:55Z

I had the same problem. I'm not sure it's a nice fix, but it works for me.
Yarn is installed for alternative os

First $PATH has to be updated:

export PATH="$HOME/.yarn/bin:$PATH"

Next I add a symbol link like this:

ln -s ~/.yarn/bin/yarn.js ~/.yarn/bin/yarn

I hope it can help

spasquali-ww · 2020-12-14T10:32:51Z

Just for clarity, must yarn exist in $PATH for husky to function?

typicode · 2021-01-28T11:24:51Z

Running yarn via npx is not supported in v4.

To answer the other question, husky 4 expects that the package manager used to install is in PATH environment variable.

There's a section about setting up PATH for yarn 1
https://classic.yarnpkg.com/en/docs/install

As to why, it's because of this:
https://yarnpkg.com/getting-started/migration#call-binaries-using-yarn-run-rather-than-node_modulesbin

As recommended, husky uses yarn run to execute husky-run binary (which runs hooks) and so it needs it to be available.

Hope it makes things a little clearer :)

Husky 5 is a little more flexible in this regard but npm or yarn will probably still need to be in PATH. If you're using a GUI Git client and tools like nvm or brew, there's a special section in the docs about setting PATH with .huskyrc.

jasonworden · 2021-10-15T22:20:09Z

I was receiving Can't find yarn in PATH errors when Husky commit hooks run in Sourcetree on Mac. I was able to fix this with the following steps.

Go to my terminal and run which yarn. This outputs something like /Users/my-user/.nvm/versions/node/v12.x.x/bin/yarn. Grab yarn's parent directory, in this case /Users/my-user/.nvm/versions/node/v12.x.x/bin/.
Edit your ~/.huskyrc file (create one if you don't have one already). Add the following to this file:

# Add yarn to path
export PATH=/Users/my-user/.nvm/versions/node/v12.x.x/bin:$PATH

luisbello30 · 2022-02-06T20:51:39Z

I was receiving Can't find yarn in PATH errors when Husky commit hooks run in Sourcetree on Mac. I was able to fix this with the following steps.

Go to my terminal and run which yarn. This outputs something like /Users/my-user/.nvm/versions/node/v12.x.x/bin/yarn. Grab yarn's parent directory, in this case /Users/my-user/.nvm/versions/node/v12.x.x/bin/.

Edit your ~/.huskyrc file (create one if you don't have one already). Add the following to this file:
# Add yarn to path
export PATH=/Users/my-user/.nvm/versions/node/v12.x.x/bin:$PATH

I had the same problem and with this configuration it was solved

There is a section on how to set PATH if you are using a version management script like nvm

https://typicode.github.io/husky/#/?id=command-not-found

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

OS: macOS 10.15.7
Git Client: Fork
nvm: v0.39.1
node: v16.13.2
husky: v4.3.0

DisasterMan78 · 2022-04-26T15:46:49Z

Getting the same error on husky 4.2.3
Can't find yarn in PATH
Also tried Tower which is another GUI git client and same issue there. So seems like a regression since it worked out of the box with GUI git clients in previous versions.

Worth noting Tower has additional issues with hooks on OSX:

https://www.git-tower.com/help/guides/integration/environment/mac

Not their fault, but it is a PITA. I'm working on a client machine with reduced admin access because SECURITY and it's quite a drag having to rebase on the command line.

joeyfigaro · 2022-10-05T16:11:34Z

Getting the same error on husky 4.2.3
Can't find yarn in PATH
Also tried Tower which is another GUI git client and same issue there. So seems like a regression since it worked out of the box with GUI git clients in previous versions.
Worth noting Tower has additional issues with hooks on OSX:

https://www.git-tower.com/help/guides/integration/environment/mac

Not their fault, but it is a PITA. I'm working on a client machine with reduced admin access because SECURITY and it's quite a drag having to rebase on the command line.

This issue also affects the Github desktop client, FWIW.

SercanSercan · 2023-01-11T14:33:07Z

If you are also desperately trying to fix ".husky/pre-commit: line 4: lint-staged: command not found", add "npx lint-staged" to your pre-commit file. Read more about the solution here: https://storksnestblog.wordpress.com/2023/01/11/fixing-husky-lint-staged-command-not-found-error/

arthur-esterox · 2023-03-01T08:15:01Z

I was receiving Can't find yarn in PATH errors when Husky commit hooks run in Sourcetree on Mac. I was able to fix this with the following steps.

Go to my terminal and run which yarn. This outputs something like /Users/my-user/.nvm/versions/node/v12.x.x/bin/yarn. Grab yarn's parent directory, in this case /Users/my-user/.nvm/versions/node/v12.x.x/bin/.

Edit your ~/.huskyrc file (create one if you don't have one already). Add the following to this file:
# Add yarn to path
export PATH=/Users/my-user/.nvm/versions/node/v12.x.x/bin:$PATH

Wonderful, thanks a lot, you saved my time.

j3ko mentioned this issue Aug 22, 2020

Hook should fail if command is not found #715

Closed

telamonian mentioned this issue Sep 30, 2020

followup #9100: made sdm switch pretty, accessible jupyterlab/jupyterlab#9104

Merged

typicode closed this as completed Jan 28, 2021

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

hook fails as it assumes yarn will be available in $PATH #666

hook fails as it assumes yarn will be available in $PATH #666

detj commented Feb 6, 2020

detj commented Mar 18, 2020

barakyosi commented Mar 25, 2020

axelfriberg commented Apr 2, 2020 •

edited

Loading

lewislbr commented Apr 5, 2020

hcharley commented Apr 8, 2020

xarvh commented May 17, 2020 •

edited

Loading

bobrosoft commented Jun 30, 2020

armspkt commented Jun 30, 2020 •

edited

Loading

j3ko commented Aug 22, 2020

elalemanyo commented Oct 16, 2020

tcastelly commented Oct 20, 2020

spasquali-ww commented Dec 14, 2020

typicode commented Jan 28, 2021

jasonworden commented Oct 15, 2021 •

edited

Loading

luisbello30 commented Feb 6, 2022

DisasterMan78 commented Apr 26, 2022

joeyfigaro commented Oct 5, 2022

SercanSercan commented Jan 11, 2023

arthur-esterox commented Mar 1, 2023

hook fails as it assumes yarn will be available in $PATH #666

hook fails as it assumes yarn will be available in $PATH #666

Comments

detj commented Feb 6, 2020

Possible to let the user choose package manager?

Workaround

detj commented Mar 18, 2020

barakyosi commented Mar 25, 2020

axelfriberg commented Apr 2, 2020 • edited Loading

lewislbr commented Apr 5, 2020

hcharley commented Apr 8, 2020

xarvh commented May 17, 2020 • edited Loading

bobrosoft commented Jun 30, 2020

armspkt commented Jun 30, 2020 • edited Loading

j3ko commented Aug 22, 2020

elalemanyo commented Oct 16, 2020

tcastelly commented Oct 20, 2020

spasquali-ww commented Dec 14, 2020

typicode commented Jan 28, 2021

jasonworden commented Oct 15, 2021 • edited Loading

luisbello30 commented Feb 6, 2022

DisasterMan78 commented Apr 26, 2022

joeyfigaro commented Oct 5, 2022

SercanSercan commented Jan 11, 2023

arthur-esterox commented Mar 1, 2023

axelfriberg commented Apr 2, 2020 •

edited

Loading

xarvh commented May 17, 2020 •

edited

Loading

armspkt commented Jun 30, 2020 •

edited

Loading

jasonworden commented Oct 15, 2021 •

edited

Loading