bytecodealliance / bytecodealliance/wasm-tools
Package `wasm-tools` as WASM Components
- Dominant language
- Rust
- Stars
- 1.8k
- Forks
- 351
- Avg merge
- 16h 57m
- Merged PRs (30d)
- 38
Description
`jco` currently maintains [custom wrappers](https://github.com/bytecodealliance/jco/blob/main/crates/wasm-tools-component/wit/wasm-tools.wit) around various `wasm-tools` tools. This is used to expose the functionality provided by `wasm-tools` from JavaScript.
It would be nice if those bindings could be provided by `wasm-tools` directly, rather than being wrapped by `jco`. Presumably other language-specific toolchains may want to also package `wasm-tools`, and being able to share the same package definitions would be great.
I'm intentionally not requesting this be made a priority. But I did want to flag it, since it seems like something this would be good to do _eventually_. Ideally around the time using [warg](https://warg.io) as a distribution mechanism for Components becomes viable [^viability].
Thank you!
[^viability]: I haven't kept up with the state of `warg`, so I don't know how far along it is. My understanding was that it's still pretty early, and it'll be a little while longer before we can use it to manage and distribute Components?
Contributor guide
Assessment
This issue has not been assessed yet.