Skip to content

Track remaining WASI Preview1 support gaps on native and web backends #15

Description

@medz

Summary

The package currently exposes the wasi_snapshot_preview1 namespace across all runtimes, but the native/web backends still implement only a minimal command-style + virtual filesystem subset.

This issue is the execution-ordered tracker for closing the remaining Preview1 support gaps. Each checklist item below is backed by a child issue. Behavioral coverage belongs to each capability issue; the verification-phase items are complementary smoke, end-to-end, and documentation work.

Current state:

  • Official WASI Preview1 surface: 46 functions
  • Native/web backends: 19 implemented, 27 exported as explicit ENOSYS stubs
  • Node backend: delegates to node:wasi, so its surface is not the limiting factor for wasd itself

Official references:

Execution Order

Phase 1: Low-Complexity Wins

Phase 2: File Descriptor Model

Phase 3: Path and Directory Semantics

Phase 4: Events, Process, and Sockets

Phase 5: Verification and Documentation

Exit Criteria

We should close this issue only when one of these is true:

  1. Native and web backends support the full Preview1 surface with tested behavior.
  2. The remaining exclusions are explicitly documented, and the package/docs stop implying complete Preview1 support.

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