cargo-component

cargo-component copied to clipboard

Currently target dependencies are specified through a map where the key is the `package:name` package id. However, multiple dependencies can have the same id if they are of different versions....

rylev

`cargo component` passes through certain commands like `build` to be run by `cargo`. The blurb at the bottom of `--help` explains this. ``` Unrecognized subcommands will be passed to cargo...

calebschoepp

Right now if a command component is created and a world is included via: ```wit package example:demo world demo { include wasi:cli/command } ``` then the output component will expect...

alexcrichton

Add `test` command to support running tests

5

Currently there is no `test` command in `cargo-component`. The standard `cargo test` doesn't work because the standard tooling has no visibility to `bindings`, `exports` or any generated structs and enums....

ithinkicancode

`CARGO_BUILD_TARGET` environment variables should be supported, just like `cargo` https://doc.rust-lang.org/cargo/reference/config.html#buildtarget

rvolosatovs

Building with `--release` fails to generate one component type section

3

I've got [this small repro](https://github.com/bnjbvr/repro-cargo-component-release-failure), in which if I compile with `cargo-component build`, the component is created and can be loaded in wasmtime; but if I do `cargo-component build --release`,...

bnjbvr

Compile error when installing cargo component

6

Recently, I got an error when I was installing `cargo component` in GitHub actions. The error is: ``` error[E0061]: this method takes 1 argument but 0 arguments were supplied -->...

kajacx

Some wasi imports added per default into wit

2

If I create a new component, it contains some imports which are not used. How can these be disabled? I searched all code and documentation and could not find any...

elwerene

Resource Static Methods Cause Build Failure When Imported

5

Hey all, I ran into an issue where I couldn't import static resource functions which were defined in another wasm component. I have a minimal example attached as a zip...

toadslop

Currently, when publishing a wit package, the string used at the top of the package declaration in the wit file does not need to correspond to the name or version...

macovedj