Phoebe: A small but meaningful subset of users (myself included) use Rust without rustup. Currently, this is painful, because the CLI unconditionally invokes rustup to ensure the wasm32-unknown-unknown target is installed. I ended up having to put a stub shell script into my path as rustup which does nothing and returns 0.
The CLI should verify that cargo has the wasm32-unknown-unknown target installed, and if it is present, not invoke rustup.
Bonus points if the CLI checks for rustup on the system when wasm32-unknown-unknown is not present, and if neither the target nor rustup are present, prints an error message telling the user to install the target.
Phoebe: A small but meaningful subset of users (myself included) use Rust without
rustup. Currently, this is painful, because the CLI unconditionally invokesrustupto ensure thewasm32-unknown-unknowntarget is installed. I ended up having to put a stub shell script into my path asrustupwhich does nothing and returns 0.The CLI should verify that
cargohas thewasm32-unknown-unknowntarget installed, and if it is present, not invokerustup.Bonus points if the CLI checks for
rustupon the system whenwasm32-unknown-unknownis not present, and if neither the target norrustupare present, prints an error message telling the user to install the target.