-
-
Notifications
You must be signed in to change notification settings - Fork 32.7k
Closed
Labels
help wantedIssues that need assistance from volunteers or PRs that need help to proceed.Issues that need assistance from volunteers or PRs that need help to proceed.v18.xIssues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.
Description
See #42115 (comment). I'm opening a new issue for visibility.
Staring with V8 version 9.9 (and still with the latest canary, V8 fails to compile on Windows with MSVC (2019 and 2022).
@bnoordhuis tried to help finding a workaround, but it didn't work.
I opened an issue on V8's tracker (v8:12661). It was assigned a low priority which makes sense from their point of view because MSVC is not officially supported by V8.
@gengjiawen requested access to a Windows VM in nodejs/build#2891 but it's not clear if someone is going to give them this access.
I think this is becoming critical for us. V8 updates are blocked because of this issue and we are coming close to the release of v18.0.0.
@nodejs/tsc @nodejs/platform-windows @nodejs/v8-update @nodejs/v8
adarshmadrecha, dnalborczyk and lin72h
Metadata
Metadata
Assignees
Labels
help wantedIssues that need assistance from volunteers or PRs that need help to proceed.Issues that need assistance from volunteers or PRs that need help to proceed.v18.xIssues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.Issues that can be reproduced on v18.x or PRs targeting the v18.x-staging branch.v8 engineIssues and PRs related to the V8 dependency.Issues and PRs related to the V8 dependency.windowsIssues and PRs related to the Windows platform.Issues and PRs related to the Windows platform.