Skip to content

[WASI] Stop generation of Node.js execution script due to lack of preview2 support#122030

Closed
yamachu wants to merge 2 commits into
dotnet:mainfrom
yamachu:stop-generate-nodescripts
Closed

[WASI] Stop generation of Node.js execution script due to lack of preview2 support#122030
yamachu wants to merge 2 commits into
dotnet:mainfrom
yamachu:stop-generate-nodescripts

Conversation

@yamachu
Copy link
Copy Markdown
Contributor

@yamachu yamachu commented Nov 28, 2025

From .NET 9, wasip2 is now supported.
However, the currently available Node.js does not directly support preview2.

The generated execution script node.mjs currently specifies preview1, and as a result, it cannot be used as-is for execution.

To avoid user confusion, we are temporarily stopping the output of this file until proper support is available.

@yamachu yamachu requested a review from maraf as a code owner November 28, 2025 09:34
Copilot AI review requested due to automatic review settings November 28, 2025 09:34
@yamachu yamachu requested a review from akoeplinger as a code owner November 28, 2025 09:34
@dotnet-policy-service dotnet-policy-service Bot added the community-contribution Indicates that the PR has been added by a community member label Nov 28, 2025
@github-actions github-actions Bot added the needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners label Nov 28, 2025
Copy link
Copy Markdown
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

This PR temporarily disables the generation of Node.js execution scripts for WASI applications due to a compatibility mismatch. While .NET 9+ now supports WASI preview2, the Node.js script being generated hardcodes version: 'preview1', making it incompatible with the current runtime. The change prevents user confusion by not generating a script that cannot be used as-is.

Key Changes

  • Commented out the _WasmGenerateNodeScripts target invocation in the build dependency chain
  • Added an explanatory comment noting the temporary nature of this change pending Node.js preview2 support

@jkotas jkotas added os-wasi Related to WASI variant of arch-wasm area-Build-mono and removed needs-area-label An area label is needed to ensure this gets routed to the appropriate area owners labels Nov 28, 2025
@pavelsavara pavelsavara added the arch-wasm WebAssembly architecture label Apr 13, 2026
@dotnet-policy-service
Copy link
Copy Markdown
Contributor

Tagging subscribers to 'arch-wasm': @lewing, @pavelsavara
See info in area-owners.md if you want to be subscribed.

@pavelsavara
Copy link
Copy Markdown
Member

/azp run runtime-wasm

@azure-pipelines
Copy link
Copy Markdown

Azure Pipelines successfully started running 1 pipeline(s).

@pavelsavara
Copy link
Copy Markdown
Member

Closing in favor of #128997

@pavelsavara pavelsavara closed this Jun 4, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

arch-wasm WebAssembly architecture area-Build-mono community-contribution Indicates that the PR has been added by a community member os-wasi Related to WASI variant of arch-wasm

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants