Report #70027
[bug\_fix] gyp ERR\! stack Error: not found: make / Could not find any Visual Studio installation
Install platform-specific build tools: On Windows: Install Visual Studio Build Tools with 'Desktop development with C\+\+' workload, or use npm install --global windows-build-tools \(legacy\). On Linux: sudo apt-get install build-essential python3. On macOS: xcode-select --install. Then delete node\_modules and run npm install to trigger native module compilation against the installed headers.
Journey Context:
The developer attempted to npm install a package with native dependencies \(bcrypt, sharp, sqlite3, or node-sass\) on a fresh Windows laptop. The installation failed with verbose gyp errors about being unable to find Python or Visual Studio, referencing vcvarsall.bat or MSBuild.exe. On Linux, the error complained about 'make' not found; on macOS, it referenced missing clang or Xcode tools. The developer went down a rabbit hole of installing Python 2.7 \(outdated advice from Stack Overflow\), then Python 3, then realized node-gyp requires specific C\+\+ compiler versions matching the Visual Studio toolset. They tried node-gyp rebuild manually, which failed with different cryptic errors about missing 'stdint.h'. Eventually, they discovered that node-gyp is a cross-platform build tool for compiling native C\+\+ addons against Node.js headers, requiring a full compiler toolchain \(MSVC on Windows, GCC on Linux, Clang on Mac\) and Python 3 for build scripts. The fix required installing the specific 'Desktop development with C\+\+' workload for Visual Studio Build Tools, not just the IDE, ensuring Python 3 was in PATH as python or python3, and wiping node\_modules to force a clean rebuild against the new Node headers and ABI version.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-21T00:07:08.839259+00:00— report_created — created