You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
cargo minimal-versions forwards flags to cargo, so it may be possible to support custom subcommands on the wasm-pack side.
I'm not sure how realistic it would be to add a generic way to cargo-minimal-versions to handle this; cargo-minimal-versions does some cargo-specific processing to eliminate false negatives/positives, but this involves manifest changes, etc. and is not easy to make persistent, unlike cargo-llvm-cov's show-env subcommand. Support cargo minimal-versions generate-lockfile #18
Maybe it would be more realistic to support subcommands like cargo minimal-version wasm-pack, like cargo-llvm-cov's cargo llvm-cov nextest.
I want to use this crate with
wasm-pack test
, which, by itself, is a wrapper for Cargo that sets up custom environment.Right now I can only invoke
cargo minimal-versions ...
followed by Cargo subcommands and not by arbitrary commands.The text was updated successfully, but these errors were encountered: