Skip to content

Track WASI Preview 3 draft implementation across async component-model foundations and 0.3.0 RC WASI packages #70

Description

@medz

Summary

Track draft WASI Preview 3 implementation in wasd using the same execution-ordered issue roadmap style as Preview1 and Preview2, but with async component-model foundations first and the current v0.3.0-rc-2025-09-16 WASI package set layered on top.

Current repo and spec state:

  • README.md still marks Preview 2 as not implemented, so Preview 3 capability is also not available today.
  • As of 2026-03-14, the official WebAssembly/WASI docs do not publish a Preview3.md or formal Preview 3 launch note.
  • The component-model README still describes Preview 3 as a subsequent milestone, and docs/Preview2.md still says "When Preview 3 is launched", so this tracker targets draft or RC sources rather than a released Preview 3 spec.
  • Preview 3 cannot reuse node:wasi; node support must be implemented through JS interop host adapters for each capability.
  • Preview 3 package work here intentionally targets the current official RC tag v0.3.0-rc-2025-09-16, and the async component-model references are pinned to commit 2e4800866d529aedc1b7730bc9452a4f85b97d8f.

Execution rules:

  • Each capability issue is expected to bring its own focused tests.
  • The checklist below is already sorted by dependency order; reading it top-to-bottom is the intended implementation path inside Preview 3.
  • The Blocked by notes explain why a later item is placed where it is; if you follow the checklist order, you should not need extra dependency triage.

References

Execution Order

Phase 1: Async Component Foundations

Phase 2: Preview 3 Draft Packages

Phase 3: Verification and Documentation

Exit Criteria

Close this tracker only when one of these is true:

  1. The async component foundations and the selected Preview 3 draft packages are implemented with tested behavior across the intended runtimes.
  2. Any remaining Preview 3 draft exclusions or RC-baseline caveats are explicitly documented, and package docs stop implying broader or more stable support than the runtime actually provides.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions