[browser][CoreCLR] smoke test libraries on V8 and Firefox#124641
[browser][CoreCLR] smoke test libraries on V8 and Firefox#124641pavelsavara wants to merge 7 commits intodotnet:mainfrom
Conversation
pavelsavara
commented
Feb 20, 2026
- smoke test V8 + FF
- version check for shells
- version check for shell
|
Tagging subscribers to this area: @agocke, @dotnet/runtime-infrastructure |
There was a problem hiding this comment.
Pull request overview
This PR expands the WebAssembly/CoreCLR smoke-test matrix to run library tests on Firefox and a V8 shell, and adds runtime version gating in the JS loader to fail fast on unsupported Node.js / shell versions.
Changes:
- Add Node.js (>= 18) and V8 shell (>= 14) version checks to
validateWasmFeatures()in the JS loader bootstrap. - Update the runtime pipeline to run CoreCLR wasm smoke/library tests on Firefox and V8 in addition to Chrome.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
src/native/libs/Common/JavaScript/loader/bootstrap.ts |
Adds engine/runtime version checks during wasm feature validation. |
eng/pipelines/runtime.yml |
Enables additional wasm test scenarios (Firefox + V8) for CoreCLR library smoke tests. |
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
Co-authored-by: Copilot <175728472+Copilot@users.noreply.github.com>
|
|
Firefox went just fine: Log |
| export function verifyEnvironment () { | ||
| mono_assert(ENVIRONMENT_IS_SHELL || typeof globalThis.URL === "function", "This browser/engine doesn't support URL API. Please use a modern version. See also https://aka.ms/dotnet-wasm-features"); | ||
| mono_assert(typeof globalThis.BigInt64Array === "function", "This browser/engine doesn't support BigInt64Array API. Please use a modern version. See also https://aka.ms/dotnet-wasm-features"); | ||
| mono_assert(ENVIRONMENT_IS_SHELL || typeof globalThis.URL === "function", "This browser/engine doesn't support URL API. Please use a modern version. See also https://learn.microsoft.com/en-us/aspnet/core/blazor/supported-platforms"); |
There was a problem hiding this comment.
We typically omit en-us in the doc URLs so that the URL opens localized content based on user preferences.
| const message = ENVIRONMENT_IS_NODE | ||
| ? "Please install `node-fetch` and `node-abort-controller` npm packages to enable HTTP client support. See also https://aka.ms/dotnet-wasm-features" | ||
| : "This browser doesn't support fetch API. Please use a modern browser. See also https://aka.ms/dotnet-wasm-features"; | ||
| ? "Please install `node-fetch` and `node-abort-controller` npm packages to enable HTTP client support. See also https://learn.microsoft.com/en-us/aspnet/core/blazor/supported-platforms" |
There was a problem hiding this comment.
Do we have any official docs for node? I think the node links can point to internal runtime docs (maybe even have direct links without aka.ms indirection).