--verbose should print cargo command

[stepancheg]

wasm-pack build --target web --verbose

prints something like:

[INFO]: 🎯  Checking for the Wasm target...
[INFO]: 🌀  Compiling to Wasm...
       Fresh unicode-ident v1.0.12
       Fresh bumpalo v3.15.4
       Fresh log v0.4.21
       Fresh once_cell v1.19.0
       Fresh cfg-if v1.0.0
       Fresh proc-macro2 v1.0.79
       Fresh quote v1.0.35
       Fresh wasm-bindgen-shared v0.2.92 (/Users/nga/devel/left/wasm-bindgen/crates/shared)
       Fresh syn v2.0.52
       Fresh wasm-bindgen-backend v0.2.92 (/Users/nga/devel/left/wasm-bindgen/crates/backend)
       Fresh wasm-bindgen-macro-support v0.2.92 (/Users/nga/devel/left/wasm-bindgen/crates/macro-support)
       Fresh wasm-bindgen-macro v0.2.92 (/Users/nga/devel/left/wasm-bindgen/crates/macro)
       Fresh wasm-bindgen v0.2.92 (/Users/nga/devel/left/wasm-bindgen)
       Fresh js-sys v0.3.69 (/Users/nga/devel/left/wasm-bindgen/crates/js-sys)
       Fresh web-sys v0.3.69 (/Users/nga/devel/left/wasm-bindgen/crates/web-sys)
       Fresh without-a-bundler v0.1.0 (/Users/nga/devel/left/wasm-bindgen/examples/without-a-bundler)
    Finished release [optimized] target(s) in 0.22s
[INFO]: Optimizing wasm binaries with `wasm-opt`...
[INFO]: Optional fields missing from Cargo.toml: 'description', 'repository', and 'license'. These are not necessary, but recommended
[INFO]: ✨   Done in 0.53s
[INFO]: 📦   Your wasm pkg is ready to publish at /Users/nga/devel/left/wasm-bindgen/examples/without-a-bundler/pkg.

The important missing bit is there's no cargo command invocation flags. Which might be useful. In particular, I'd like to reverse-engineer what target was passed to cargo command, but it is not there.

wasm-pack 0.12.1