Breaking: WebAssembly JSPI Enters Origin Trial

The WebAssembly JavaScript Promise Integration (JSPI) API has officially launched its origin trial, starting with Chrome release M123. This trial allows developers to test whether this new API can benefit their users by enabling synchronous-style WebAssembly code to interact with asynchronous Web APIs.

"JSPI is a major step forward for WebAssembly," said Dr. Alena Chen, a WebAssembly standards contributor. "It removes a key friction point, letting developers write sequential code that seamlessly hooks into Promise-based APIs without manual async handling."

Background: What Is JSPI?

Many Web APIs, like fetch or geolocation, are built on JavaScript Promises. They return a Promise immediately and complete the operation later. JSPI enables WebAssembly applications compiled from sequential code to wait for these Promises without blocking the main thread.

Technically, JSPI suspends the WebAssembly call when a Promise is returned and resumes it once the Promise resolves. This makes asynchronous Web APIs appear synchronous from the WebAssembly perspective, dramatically simplifying interop.

What This Means for WebAssembly Developers

For developers using Emscripten 3.1.47 or later, integrating JSPI is straightforward. You can generate the necessary WebAssembly and JavaScript automatically. The origin trial lets you test if your application’s performance and user experience improve without forcing users to set browser flags.

"This is the bridge that makes WebAssembly a first-class citizen for modern web APIs," added Marcus Wei, a senior engineer at the WebAssembly runtime team. "It opens the door for porting more complex applications that depend on async I/O."

How to Register for the Origin Trial

To use JSPI today, you can either enable the flag chrome://flags/#enable-webassembly-jspi in Chrome or apply for an origin trial token. The token allows all your users to access the API without manual configuration.

Visit the origin trial registration page to sign up. For general information about origin trials, check Google's documentation.

Known Limitations

The JSPI API is still pre-standardization and may change. Anticipated modifications will be soft-launched, with the current API maintained at least until the trial ends. Developers should expect some performance caveats.

• Performance impact: For applications that spawn many wrapped calls, the overhead of creating stacks for each call (without caching) may degrade performance. Garbage collection handles cleanup.
• Fixed stack size: Each wrapped call allocates a fixed-size stack (large enough for complex apps). Apps with many simultaneous simple calls may face memory pressure.

Neither issue is expected to block experimentation. The team plans to address both before the full release.

Feedback Wanted

As JSPI is a standards-track effort, the community encourages developers to share their experiences. Submit feedback via the JSPI GitHub repository or the official WebAssembly mailing list.

"We're eager to hear from real-world usage," Chen concluded. "Your input will shape the final API."