Skip to content

docs(wasm): record issue #203 stage 3 status (JSPI still flagged) #425

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
gg582 merged 1 commit into from
Oct 20, 2026
Merged

docs(wasm): record issue #203 stage 3 status (JSPI still flagged) #425

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions docs/api/wasm-component.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -145,6 +145,16 @@ overhead is what crosses the default limit.
shipping unflagged in node and browsers, and port the SSE examples
off the EM_JS callback. Only then does the Emscripten build leave CI.

Status checked 2026-10-20:
- JSPI is still flagged in node. With Node v24.16.0 (`node --version`),
`WebAssembly.promising` and `WebAssembly.Suspending` are undefined
without `--experimental-wasm-jspi` and defined with it. The 0.3
smoke targets still pass that flag. Browser JSPI was not checked.
- No example under `example/` calls the EM_JS chunk callback or
`cwist_app_dispatch_stream()`. The callback is defined in
`include/cwist/wasm/wasm_entry.h`, so there is no example port to
do yet. Stage 3 stays open until the flag condition changes.

## Browser runtime gate (WASI 0.2)

`make component-browser-smoke` remains a packaging-only check.
Expand Down
Loading