Node.js 24 (LTS) drops MSVC on Windows — ClangCL now required to build Node and native modules

Key update

Node.js 24 entered LTS on October 28, 2025 and the Node.js project removed official MSVC support for building Node on Windows: the supported Windows toolchain for compiling Node and its native components is now ClangCL. This change is part of the Node 24 release and affects anyone who builds Node from source or compiles native addons on Windows.

Why it matters

This is a practical, non‑cosmetic change that can break or complicate real‑world developer workflows. Tooling and CI that relied on Visual Studio build tools (MSVC/MSBuild) to compile Node, node-gyp, or native npm modules must switch to a ClangCL‑based toolchain or use official prebuilt binaries. Expect to: update Windows CI images and runners to install Clang/ClangCL and matching Windows SDKs; rebuild and test all native addons (ABI/CRT differences can expose bugs or undefined behavior); verify build tooling like node-gyp, native build scripts, and prebuild pipelines work with ClangCL; and pin production Node binaries until native dependencies are validated in staging.

Actionable priorities for teams: first, do a smoke test of your production application and all native dependencies using the official Node 24 LTS binary; second, if you build Node or native modules in CI on Windows, replace MSVC images with ClangCL images and run a full native test matrix; third, if you distribute native binaries, add ClangCL build targets to prebuild pipelines and communicate new Windows compatibility requirements to downstream consumers. If switching the toolchain is not immediately feasible, continue using the Node binaries provided by the Node project (not building from source) while you validate and migrate.

Source

• Source