`cargo web start` in a workspace can't automatically find my frontend crate.
cedric-h opened this issue · comments
When I run cargo web start in my project's Cargo workspace, I get:
error: no default package; you can specify a crate to use with the -p argument
cargo web start -p front does work, where front is my frontend stdweb crate.
However, it seems like cargo web start should be smart enough to find the crate with the Web.toml; if it can't find any crate with a Web.toml or multiple crates with Web.tomls, then I should get the message above.
It seems like #17 is pretty similar. I'll see if I can find the commit that resolved that issue and see if I can use the content there to write a PR to make this enhancement.