Skip to content

Enable the --js-wasm-jspi integration test - #4557

Closed
sideeffffect wants to merge 5 commits into
VirtusLab:mainfrom
sideeffffect:feat/js-wasm-jspi-unignore
Closed

sideeffffect wants to merge 5 commits into
VirtusLab:mainfrom
sideeffffect:feat/js-wasm-jspi-unignore

Conversation

@sideeffffect

Copy link
Copy Markdown
Contributor

No description provided.

sideeffffect and others added 5 commits October 13, 2026 21:43
Since Scala.js 1.22 the linker links js.async/js.await on WebAssembly
only when WasmFeatures.useJSPI is set; otherwise linking fails with
"Uses an async block without JSPI support in WebAssembly". The option
is passed to the Scala.js CLI as --useJSPI, which needs a Scala.js CLI
release containing VirtusLab/scala-js-cli#209.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
…s --useJSPI

The bundled scala-js-cli (1.22.0.1) rejects --useJSPI, so the end-to-end test
can only pass once VirtusLab/scala-js-cli#209 is released and scalaJsCli is
bumped. The option parsing and directive are covered by unit tests.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
1.22.0.3 is the first scala-js-cli version with --useJSPI
(VirtusLab/scala-js-cli#209).

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Skip it on Scala 3.3, whose compiler has no js.async/js.await support.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@sideeffffect

Copy link
Copy Markdown
Contributor Author

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant