[v20.x] doc: support toolchain with Visual Studio 2019 & 2022 only - #61450
Closed
MikeMcC399 wants to merge 1 commit into
Closed
[v20.x] doc: support toolchain with Visual Studio 2019 & 2022 only#61450MikeMcC399 wants to merge 1 commit into
MikeMcC399 wants to merge 1 commit into
Conversation
Copy link
Copy Markdown
Contributor
Sorry, something went wrong.
Copy link
Copy Markdown
Collaborator
|
Review requested:
|
Sorry, something went wrong.
MikeMcC399
marked this pull request as ready for review
January 20, 2026 12:39
sxa
approved these changes
Jan 20, 2026
StefanStojanovic
approved these changes
Jan 20, 2026
Copy link
Copy Markdown
Contributor
Author
|
Thanks for your support and follow-up! I think commit-queue Add this label to land a pull request using GitHub Actions. only works for PRs targeting the main branch (see Commit Queue), so I would expect that this PR would need to be manually picked up by the Releasers / Backporters team. |
Sorry, something went wrong.
This comment was marked as outdated.
MikeMcC399
force-pushed
the
v20.x-visual-studio-2022
branch
from
0b906d4 to
4de61c7
Compare
February 25, 2026 10:52
Copy link
Copy Markdown
Contributor
Author
|
Modified commit message to use imperative verb and rebased |
Sorry, something went wrong.
aduh95
force-pushed
the
v20.x-staging
branch
from
dea3f59 to
d75ae77
Compare
February 28, 2026 11:18
MikeMcC399
force-pushed
the
v20.x-visual-studio-2022
branch
from
4de61c7 to
531ba50
Compare
February 28, 2026 15:10
marco-ippolito
approved these changes
Mar 2, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Reviewers
6 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Refs: #60869
Refs: #61449
Situation
The Supported toolchains section for v20.x lists Visual Studio >= 2019 with the Windows 10 SDK on a 64-bit host.
By implication, this includes also the latest release of Microsoft Visual Studio which is Visual Studio 2026.
.\vcbuild fails to run in the v20.x branch on Windows 11 25H2 in a PowerShell terminal with the Windows Prerequisites installed, and only using Visual Studio Build Tools 2026.
Support for Visual Studio Build Tools 2026 requires a minimum of gyp-next@0.21.0.
The Node.js v20.x branch includes gyp-next@0.16.2 in v20.x/tools/gyp and so lacks support for Visual Studio 2026.
Failure log
Change
In BUILDING.md