.bashrc: Change npm test logic
The whole `if command ...` logic doesn't make sense to me, because the command exits with 0 if it is successful, which means false! This is just more readable anyways. Signed-off-by: Alan Orth <alan.orth@gmail.com>
This commit is contained in:
parent
049c3600ef
commit
c42a4edfd4
5
.bashrc
5
.bashrc
@ -37,8 +37,9 @@ export ANSIBLE_HOSTS=hosts
|
|||||||
# if we have npm, we probably want to use npm binaries
|
# if we have npm, we probably want to use npm binaries
|
||||||
# I don't like installing globally (npm -g), so add local
|
# I don't like installing globally (npm -g), so add local
|
||||||
# node modules' bin to PATH
|
# node modules' bin to PATH
|
||||||
if test $(which npm >/dev/null 2>&1); then
|
command -v npm >/dev/null 2>&1
|
||||||
PATH=$PATH:node_modules/.bin
|
if [[ $? -eq 0 ]]; then
|
||||||
|
export PATH=$PATH:node_modules/.bin
|
||||||
fi
|
fi
|
||||||
|
|
||||||
# Enable pyenv
|
# Enable pyenv
|
||||||
|
Loading…
Reference in New Issue
Block a user