doc: missing highest compatible Microsoft Visual Studio version #61449
Description
Refs: #60869
Situation
The Supported toolchains section of the BUILDING.md document for each active branch specifies only a minimum version of Microsoft Visual Studio using >= as follows. This implicitly includes the current latest version: Visual Studio 2026.
| Node.js branch | Windows Supported toolchain |
|---|---|
| v20.x | Visual Studio >= 2019 with the Windows 10 SDK on a 64-bit host |
| v22.x | Visual Studio >= 2022 with the Windows 10 SDK on a 64-bit host |
| v24.x | Visual Studio >= 2022 with the Windows 10 SDK on a 64-bit host |
| v25.x | Visual Studio >= 2022 with the Windows 10 SDK on a 64-bit host |
| main | Visual Studio >= 2022 with the Windows 10 SDK on a 64-bit host |
As originally described in issue #60869, Visual Studio 2026 does not work for branches v24.x and lower. Edit: V24.x is now compatible with Visual Studio 2026.
Specifying only a lower bound for the compatible version(s) of Visual Studio with >= notation makes the documentation also potentially inaccurate each time Microsoft releases a new version of Visual Studio. Version detection needs to be added specifically for each Visual Studio release - see for example #60727 for Visual Studio 2026.
According to Visual Studio Product Lifecycle and Servicing
Visual Studio starting with version 2026 follows the Microsoft Product Modern Lifecycle Policy and offers 2 years of support for each new major version. We plan to ship a new major version every year.
The previous cadence of Visual Studio 2019, 2022 and 2026 provided a gap of several years between major versions. When Microsoft releases Visual Studio 2027, 2028, and so on, the "Supported toolchains" documentation will automatically become inaccurate if it continues not to state an upper bound for the version.
Suggestion / Status
Change Supported toolchains to match actual support:
| Node.js branch | Windows Supported toolchain | Comment /Status |
|---|---|---|
| v20.x | Visual Studio 2019 or 2022 with the Windows 10 SDK on a 64-bit host | Fixed in v20.20.1 |
| v22.x | Visual Studio 2022 with the Windows 10 SDK on a 64-bit host | Fixed in v22.22.1 |
| v24.x | Visual Studio 2022 or 2026 with the Windows 10 or 11 SDK on a 64-bit host | Fixed in v24.15.0 |
| v25.x | Visual Studio 2022 or 2026 with the Windows 10 or 11 SDK on a 64-bit host | Fixed in v25.8.0 |
| main | Visual Studio 2022 or 2026 with the Windows 11 SDK on a 64-bit host | Fixed |
Activity
MikeMcC399 commentedon Jan 21, 2026
MikeMcC399 commentedon Jan 28, 2026
doc: Clarify supported Visual Studio versions for windows
MikeMcC399 commentedon Feb 15, 2026
MikeMcC399 commentedon Feb 15, 2026
doc: supported toolchain with Visual Studio 2022 only
doc: supported toolchain with Visual Studio 2022 only
doc: supported toolchain with Visual Studio 2022 only
doc: support toolchain Visual Studio 2022 & 2026 + Windows 11 SDK
doc: support toolchain Visual Studio 2022 & 2026 + Windows 11 SDK
doc: support toolchain with Visual Studio 2019 & 2022 only
doc: support toolchain with Visual Studio 2019 & 2022 only
oc: support toolchain Visual Studio 2022 & 2026 + Windows 11 SDK
oc: support toolchain Visual Studio 2022 & 2026 + Windows 11 SDK
oc: support toolchain Visual Studio 2022 & 2026 + Windows 11 SDK
oc: support toolchain Visual Studio 2022 & 2026 + Windows 11 SDK
doc: support toolchain Visual Studio 2022 & 2026 + Windows 11 SDK
MikeMcC399 commentedon Apr 17, 2026
With the release of Node.js 24.15.0 this issue is now resolved in each of the currently supported release lines.
xiyatu987 commentedon Apr 17, 2026