error: `env: node: No such file or directory`

[BeLi4L]

When I try to commit some changes, I have the following error: env: node: No such file or directoryas you see on this screenshot:

I guess it's due to a pre-commit in my repo that uses yarn/node. Usually node is on my PATH, because I run nvm setup scripts in both .bashrc and .zshrc.

Any idea of why Sourcegit can't find node? Does it use a special shell or path? 🤔

[love-linger]

it's because your sourcegit process is not started via bash or zsh. Are you using Sourcegit on macOS?

[BeLi4L]

Yes I'm on macOS

[love-linger]

The simplest way to solve this problem is changing the hook script's interpreter to /bin/zsh. For example:

#!/bin/zsh

node xxxxxx

[aikawayataro]

.*rc files are only sourced when the shell is called interactively so to make it work with zsh, you should do PATH magic at .zshenv. There is no direct equivalent to bash though.

edit:
You can also make bash interactive and it will source .bashrc with this shebang: #!/bin/bash -i

[BeLi4L]

Thanks for your quick answers! ❤️

My hook scripts actually use #!/bin/sh so I just added [ -s "/opt/homebrew/opt/nvm/nvm.sh" ] && \. "/opt/homebrew/opt/nvm/nvm.sh" to every git hook script, and it works 🥳

[BeLi4L]

I noticed that VS Code doesn't have this issue (whereas sourcegit & some other git GUIs have it) @love-linger

Any idea why? Are they doing anything differently? 🤔

I'm asking because to fix this in my company, I'd have to update every git hook in every repo, which is a huge pain, and may cause issues on some people's environments 😅

[love-linger]

You can make a link to the nvm.sh

ln -s /opt/homebrew/bin/nvm /opt/homebrew/opt/nvm/nvm.sh

After that you can use nvm in your hook files

[gadfly3173]

I noticed that VS Code doesn't have this issue (whereas sourcegit & some other git GUIs have it) @love-linger

Any idea why? Are they doing anything differently? 🤔

I guess it's because vscode reads various shell configuration files by itself.

https://github.com/microsoft/vscode/blob/3ae1a2259222266236891f983a0a9229b491998d/src/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh

[BeLi4L]

Not sure I understand 🤔

Doing that would only allow me to access the nvm command, which isn't what I want, since the nvm.sh script is only a config script, which defines a nvm command, and adds the correct node/npm versions to PATH, which is what I want.

In a perfect world, I'd like to have the git GUIs I use do this kind of thing, because I don't want to update EVERY git hook and tell EVERY developer in the company to add a symbolic link somewhere, whereas it's not necessary in VS code 😅

[BeLi4L]

I guess it's because vscode reads various shell configuration files by itself.

https://github.com/microsoft/vscode/blob/3ae1a2259222266236891f983a0a9229b491998d/src/vs/workbench/contrib/terminal/common/scripts/shellIntegration-bash.sh

Oh right I see thanks! ;)

[love-linger]

If you are using the latest build from Github Action, you can start SourceGit from commandline open -a SourceGit. It will introduce the PATH environment variable to SourceGit and its subprocess