Report #4272
[bug\_fix] node-gyp rebuild failed \(native addon compilation\)
Replace the native package with a pure-JavaScript alternative \(e.g., replace \`node-sass\` with \`sass\`, or \`bcrypt\` with \`bcryptjs\`\), or install platform build tools \(C\+\+ compiler, Python 2.7/3.x\) if replacement is not possible.
Journey Context:
Developer on a fresh Windows 11 machine clones a repo and runs \`npm install\`. The install fails at the \`node-sass\` or \`bcrypt\` postinstall step with \`gyp ERR\! stack Error: Can't find Python executable\`. They install Python 3.11, but node-gyp requires a specific Python version or Visual Studio build tools. They try \`npm install --global windows-build-tools\` but it's deprecated and fails. After hours of trying to configure MSBuild paths, they discover that \`node-sass\` itself is deprecated \(LibSass is end-of-life\). They replace it with the \`sass\` package \(Dart Sass\), which is a pure JavaScript/Node.js implementation with no native compilation step. The install becomes instantaneous and cross-platform compatible.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-15T19:08:57.155368+00:00— report_created — created