cargo-component
cargo-component copied to clipboard
bytecodealliance
A Cargo subcommand for creating WebAssembly components based on the component model proposal.
As a follow up to #11 we should consider caching the check for the `wasm32-unknown-unknown` target in case invoking `rustc --print sysroot` multiple times becomes undesirable. A good starting point...
Right now we create a `interface.wit` file to represent the _default_ interface of the component (i.e. what the component itself exports as functions rather than named instances). There's a really...
Upstream cargo has [upgraded](https://github.com/rust-lang/cargo/blob/master/Cargo.toml#L65) to clap v4. `takes_value` has been deprecated. `num_args` (the replacement for `takes_value`) will default `num_args` based on the `ArgAction` and doesn't need to be set for...
After setting "cargo-component" as the custom cargo command for rust-analyzer in VS Code, it begins to fail to parse Cargo.toml's for non-cargo component crates. ```bash "rust-analyzer.server.extraEnv": { "CARGO": "cargo-component" }...
Can't believe I hadn't seen this before! This + compose is awesome stuff! I currently have been embedding the wit in a custom section so that a binary can be...
When building the following code with `cargo component build --release` it builds successfully with the `wit-bindgen` generated code, but fails using the `cargo-component` `bindings` code with: ``` error: module requires...
It seems that composing a project with a structure like below has resolution issues that need a patch to the bindings generated to function: ```sh . ├── Cargo.toml...
This is a continuation of #75, which exposes the use case. Quoting @peterhuene here: For the feature request, I think it would be along the lines of: 1. Allow component...
Issue for bumping `wit-bindgen` to `0.22.x` Ideally after the patch is released to address https://github.com/bytecodealliance/wit-bindgen/pull/891 https://github.com/bytecodealliance/cargo-component/blob/658dc2ef060de5a7bd626d7f35fd786fb718c8fd/Cargo.toml#L105 (sorry for being high maintenance 🛠️, the deltas as messing up my builds)
Is it expected that the user need to add `wit` files of secondary dependencies into `Cargo.toml`? For example, in this modified tutorial example (https://github.com/minghuaw/wasm-component-tutorial), `package component:calculator` imports `component:add/add` and `component:sub/sub`,...
Metadata
Owner
Metadata
A Cargo subcommand for creating WebAssembly components based on the component model proposal.