I've created a very simple pre-commit script:-
#!/usr/bin/env sh
# Run tests
npm test
if [ $? -ne 0 ]; then
echo "Tests failed. Aborting.."
exit 1
fi
exit 0
When I run git commit
at the command line (with failing tests), I get the expected exit 1 with the message Tests failed. Aborting..
.
However, If I use GitHub for Mac however I get:
.git/hooks/pre-commit: line 5: npm: command not found
Tests failed. Aborting..
(256)
I'm guessing its down to npm
not being available to the execution environment that GitHub for Mac is using, but I've been tearing my hair out trying to work out how to fix this.
The $PATH variable that is available in GUI environments like Github Desktop and Sourcetree is different than the one available in the terminal. By default the $PATH available in the GUI environments can't find your node modules. As was stated in the previous answer, you can ensure that /usr/local/bin is in the path by adding
In my case this did not work because I am using Node Version Manager, which stores different versions of Node and makes it easy to upgrade and switch Node versions. It stores your node_modules for each version of Node in a separate file. Here is the code I used to get around this problem:
This checks for NVM, and if it exists, loads it and uses it to find the path to the node modules for the currently used version of Node. If you are only trying to access node modules and don't need to get at anything special you can skip adding the sbin folder, e.g.
/usr/local/sbin
Resolved. As globally installed node modules end up under
/usr/local/bin
I simply needed to add the following at the beginning of my pre-commit:i.e. appending both
/usr/local/bin
and/usr/local/sbin
toPATH
at the point of execution.