Skip to content

Self-contained WIT artifacts as directories #875

Closed

Description

@alexcrichton

One thing I think would be nice to have as part of the WASI release process would be an artifact that's just a wit directory with all of the WIT files contained within. This would enable using WITs without also requiring a dependency on wkg which I feel can be useful from a "lean tooling" perspective and also helps transition to a world where WITs are fully managed by a tool eventually. In the long run though I think there'll always be use cases for taking the WITs from here as-is in a simple-ish fashion (e.g. wkg-less) and integrating them into a project.

Activity

  1. ricochet commented on Jan 29, 2026

    @ricochet
    Contributor

    Are you thinking a tar.gz of each proposal, e.g. wasi-http-0.2.9.tar.gz, or would it be more preferable to have them all like wit.tar.gz? Just a heads up, the release train has us releasing next Tuesday.

  2. alexcrichton commented on Jan 29, 2026

    @alexcrichton
    ContributorAuthor

    I was thinking ideally a single wit.tar.gz or something like that which is suitable to pass to wasm-tools component wit or similar. Effectively a canonical thing (ish) to curl-and-unpack and ready to go after things are aligned. No rush on this though, if it takes a moment to set up I think that's reasonable.

  3. added a commit that references this issue on Feb 2, 2026
    e800de2
  4. ricochet commented on Feb 3, 2026

    @ricochet
    Contributor
  5. added a commit that references this issue on Feb 4, 2026
    2f05d66
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions