Show the output of Cargo's build

[alexcrichton]

💡 Feature description

Compiling a crate can often take quite a long time and it's nice to know about the progress within the build when checking up on it. Would it be possible to avoid suppressing the output of cargo build and have it stream to the console?

[ashleygwilliams]

i have also wanted this! i think it's possible, and i'd want it to be default, i think, though i do think we might want to give a flag option to turn it off. any one else have thoughts?

[alexcrichton]

One other possibly related feature request is doing this for all possibly-long-running commands as well, for example rustup target add wasm32-unknown-unknown has its own progress bar but it doesn't show up. That runs a risk of taking a long time (megabytes over the network) and having a progress bar would be nice!

I think having an option to supress the output seems fine as well, Cargo for example supports -q which shuts up most of the default output

[fitzgen]

Personally, I'd prefer always displaying all output by default, but having a -q flag to wasm-pack which makes it not display subprocess's outputs.

It would be neat if we prefixed the output with the command that was run, eg:

cargo build (stderr): a warning message or something...
cargo build (stderr): some more warnings or whatever...
cargo build (stdout): something from stdout
[4/8] Compiling to wasm...