Ryan Levick
Ryan Levick
#### Feature Several times I've simply wanted the linker to stub out all implementations for a component that it has not yet seen. Essentially I've wanted to do roughly the...
Instead of requiring `componentize-js` to be used as a library, it would be nice if there was also a CLI experience. To begin with the CLI could take two mandatory...
As noted in https://github.com/bytecodealliance/ComponentizeJS/issues/88, it is not obvious how imports work. While I understand the hesitation to document this extensively as things are likely to change in the future, it...
The `witPath` option to the `componentize` function can either be a path to a single wit file or to a directory. If the path is a wit file then the...
**tl;dr** `wac plug` differs in semantics from `wasm-tools compose -d` for simplicity sake. While a majority of users are likely to only need the simplified semantics of `wac plug`, there...
It would be nice to have some sort of convenience for declaring a `wac_types::Package` from wit files. Essentially replacing this code: ```rust let mut resolve = wit_parser::Resolve::new(); let pkg =...
With a wac file that contains a reference to a dependency named `foo:bar-baz`, wac will look in the `deps` folder under a `foo` directory for a `bar-baz.wasm` file. However, if...
The wac language is a powerful tool that enables essentially any composition scenario. However, there are some common composition scenarios for which we could provide short hand commands to accomplish...
The phrasing "encoding a composition" makes a ton of sense once you've got a solid understanding of what wac is doing under the hood, but arguably does not capture the...
From [this discussion on the v0.3 draft PR](https://github.com/WebAssembly/wasi-http/pull/101#issuecomment-1971968430) @lukewagner said: > https://github.com/WebAssembly/wasi-http/pull/103 is proposes adding a take-headers for extracting headers that become mutable (once they are disconnected from the request/response)....