Asyncify is deprecated. Let's remove Asyncify builds once JSPI support is the baseline

[adamziel]

JSPI support landed in trunk and Asyncify is now officially deprecated in WordPress Playground 🎉 Let's monitor the runtime support and the remove Asyncify builds entirely once JSPI is widely supported.

Why? Because Asyncify builds often crash when asynchronous functions are used and every error report takes a few hours to address. Meanwhile, JSPI was designed specifically to not have that problem.

Runtime support as of Oct 10th, 2024

JSPI is supported on:

• ✅ Google Chrome with #enable-experimental-webassembly-jspi enabled at chrome://flags, or with sites where the JSPI origin trial is enabled.
• ✅ Node.js v23+ with --experimental-wasm-jspi --experimental-wasm-stack-switching feature flags.
• ✅ Deno, with --v8-flags=--experimental-wasm-jspi feature flag
• ✅ Firefox
• ? Chrome-based browsers like Edge
• ❌ Safari
• ❌ Non-Chrome, non-Firefox web browsers
• ❌ Node.js <= 21
• ❌ Non-v8 JS runtimes like Bun

Resources

• Original JSPI explorations
• Enable JSPI in Playground trunk