cargo-component
cargo-component copied to clipboard
A Cargo subcommand for creating WebAssembly components based on the component model proposal.
The [Documentation ](https://component-model.bytecodealliance.org/language-support/rust.html#importing-an-interface) mentions that > By default, cargo-component imports any required [WASI interfaces](https://wasi.dev/interfaces) for us without needing to explicitly declare them. Is there any documentation when this exactly happens?...
## Impact It seems this error means that anyone running Apple silicon (M1+ laptops) is currently unable to build/transpile a wasm component and run it in the browser. ## Brief...
I have a component that adds two numbers. It uses the adder world defined in `ghcr.io/bytecodealliance/docs/adder:0.1.0`. In my Cargo.toml, I get an error if I specify the world within the...
Hi! thanks for making `cargo-component` :) I've noticed the last two releases don't have precompiled binaries. They're useful to have, to speed up CI contexts, where we can `wget` them...
Originally, the entire point of `parse_arg` was to provide the traits that types can implement to provide a canonical argument parsing (mainly dealing with `OsString`). The additional functions were scope...
wit-bindgen has a feature to disable certain variants and records from being included for the additional_derives: https://github.com/bytecodealliance/wit-bindgen/pull/1199 Looks like this is just empty currently: https://github.com/bytecodealliance/cargo-component/blob/40a41559a1cd938900823f727e7a9ab4f4ada910/src/bindings.rs#L112 I would like to be...
Currently, to the best of my knowledge, `cargo component` generates a `src/bindings.rs` file using a version of `wit-bindgen` baked directly into the executable `cargo-component` itself. Running `cargo component new` generates...
## Description I build my repository in CI/CD by checking out the repository, and then mounting it into a docker container in which I execute the build using CMake/Make. The...
Now that `cargo-component` uses `wasm-pkg-tools` it can inherit the `wkg.lock` and stop using `Cargo-component.lock` Depends on https://github.com/bytecodealliance/wasm-pkg-tools/pull/124 being merged first.
I use `.cargo/config.toml` to control the compilation of workspace. ```toml # .cargo/config.toml [build] target = "wasm32-wasip2" ``` But `cargo component build` still generates `wasm32-wasip1` ```yaml cargo-component-component 0.19.0 ```