Git Hooks and Node Environment Issues

Git Hooks and Node Environment Issues

🧠Cause

I previously resolved the issue described in Git Hooks and Multi-JDK Environment Issues. However, today I encountered another problem where the local Node environment 🪝 hooks were not being recognized. It really has been a series of setbacks.

npx: command not found

The error message is as follows:

# 下面这一行是 sdkmanrc 的配置环境
-e Using java version 8.0.452-amzn in this shell.
# 这里开始是我的 node 环境问题
.husky/pre-commit: line 16: npx: command not found
husky - pre-commit script failed (code 127)
husky - command not found in PATH=node_modules/.bin:/opt/homebrew/opt/git/libexec/git-core:/usr/bin:/bin:/usr/sbin:/sbin

Judging from the shell log above, Git hooks can no longer detect my Node environment. Additionally, the node_modules folder installed via npm install in the project does not contain the npx executable.

❌ Problem

My development computer is a MacBook Pro with an M1 Pro chip. For developers new to the Mac system, when setting up their own shell environment on a new computer, I imagine some of you will use Homebrew, just like I did. I have to admit that installing packages this way is indeed convenient—all it takes is brew install xxx. However, this can also lead to environment mismatch issues.

Before writing this document, my shell environment consisted entirely of packages installed via Homebrew. Specifically, the files installed via brew install are placed in the /opt/homebrew/bin/ directory, which differs from where the native environment actually reads them. Most Linux and Unix developers use directories like /usr/bin and /usr/sbin to access the executables they need, and this differs significantly from actual production environments.

🔧 Solution

> Now that we know where the problem lies, let’s get to work on fixing it! > My issue is that brew install node prevents git hook from being accessible. > The rest of this document explains how to resolve this issue.

1. Completed: 卸载 Node

   使用 brew uninstall node 卸载当前环境

2. Completed: 安装 NVM

   安装 Node Version Manager 进行版本管理

3. 03

   Current: 安装 Node

   使用 NVM 安装指定版本的 Node.js

Uninstall Node

brew uninstall node

npm uninstall npm -g

node -v\nnpm -v

This completes the uninstallation of the Node environment installed via Homebrew. Next, we’ll install nvm

Install nvm

> Please Google “What is nvm” yourself

We’ll use the instructions provided by the nvm author on GitHub. GitHub: https://github.com/nvm-sh/nvm

curl -o- https://raw.githubusercontent.com/nvm-sh/nvm/v0.40.3/install.sh | bash

nvm -v

nvm ls-remote

nvm install v22.16.0

All set. If you’ve made it this far, you’ve successfully completed the process. You can now use it as usual.

📝 Summary

Through resolving this issue, I’ve summarized some important lessons regarding development environment management:

🔄 Choosing an Environment Management Tool

1. Avoid using Homebrew to install development language environments: Although Homebrew is convenient, it can cause path inconsistencies that interfere with the proper functioning of Git hooks
2. Use version management tools:
   • Java environment: Manage using SDKMAN
   • Node.js environment: Manage using NVM
   • Python environment: Manage using pyenv

🔗 Related Articles

• Git Hooks and Multi-JDK Environment Issues - Resolving Java environment issues
• SDKMAN Installation and Configuration Guide - Detailed installation tutorial for SDKMAN

💡 Best Practices

1. Unified Environment Management: Use the same environment management tool consistently across the team
2. Project Configuration: Add the appropriate configuration files to the project (e.g., .sdkmanrc , .nvmrc )
3. Documentation: Document the environment setup steps in the project documentation so team members can quickly set up their environments

This way, whether the issue involves a Java or Node.js environment, it can be properly resolved, ensuring that Git hooks function correctly.