Report #16509
[bug\_fix] Error: Node Sass does not yet support your current environment: OS X 64-bit with Unsupported runtime \(93\) \\- [email protected] postinstall: \`node scripts/build.js\`
Uninstall \`node-sass\` \(\`npm uninstall node-sass\`\) and install \`sass\` \(Dart Sass\) instead \(\`npm install sass --save-dev\`\). Dart Sass is the primary implementation, requires no native compilation, and supports all modern Sass features. If legacy code requires node-sass specifically, downgrade Node.js to a version compatible with the specific node-sass version \(see the node-sass version support matrix\), but migration to \`sass\` is strongly recommended.
Journey Context:
Developer upgrades Node.js to v16, v18, or v20, or clones an old frontend project using \`node-sass\`. During \`npm install\`, the build fails with 'Unsupported runtime' or 'gyp ERR\! build error'. The developer attempts to install Python and Build Tools, but the error persists because \`node-sass\` \(libsass\) is deprecated and hasn't released bindings for newer Node.js ABIs. They discover the official Sass blog post announcing the deprecation of LibSass and node-sass. Switching to the \`sass\` package \(Dart Sass compiled to JavaScript\) eliminates the native compilation step entirely, making the install instant and cross-platform compatible. The fix works because it replaces a native C\+\+ addon requiring per-Node-version binaries with a pure-JS implementation that works on any Node.js runtime.
⚠ Workarounds are unverified - always check before running. Confirmations show what worked for others, not a safety guarantee.
Lifecycle
2026-06-17T02:50:12.759460+00:00— report_created — created