WASI 0.3 preview: native async added to the WebAssembly Component Model

WebAssemblyWASIDevOps

Key update

The WASI roadmap now targets an August 2025 preview for WASI 0.3 and signals that the release will add native async to the WebAssembly Component Model and refactor existing 0.2 interfaces to take advantage of native async. This means component-level functions can be implemented and called asynchronously with asynchrony expressed in the Canonical ABI, rather than relying on runtime-specific adapters or workarounds. (wasi.dev)

Why it matters

Native async in the Component Model is a practical inflection point: it lets multi-language WebAssembly components expose true asynchronous APIs (awaitable calls, async I/O, timers, sockets) across language and runtime boundaries without bespoke glue. For developers that build composed Wasm apps, edge functions, or language-agnostic libraries, this reduces fragile adapter layers, improves performance predictability for async workloads, and simplifies design patterns for streaming and long-running operations. Runtimes and toolchains (Wasmtime, Wasmer, language toolchains producing components, and OCI-based component registries) will need to adopt the new ABI semantics; the roadmap estimates preview availability in August 2025 with completion around November 2025, so teams should plan to test previews, update CI and runtime targets, and avoid shipping hard dependencies on unstable preview-to-preview behavior until implementations stabilize. (wasi.dev)

Source

Read Next