Ari

> The flag has to be added in wasm-bindgen-test-runner, which is the application called when running cargo test (or wasm-pack test for that matter (I assume)). So it would work...

> The wasm-bindgen-test-runner has to also parse arguments passed to it from cargo test. Which you can see handled here: The line is commented with https://github.com/rustwasm/wasm-bindgen/blob/adcf7786d14943244cbe418a2a17d00430008e2e/crates/test/src/rt/mod.rs#L293-L294 and is followed by...

So there are three things the user has to get right: - `RUSTFLAGS` need to be set correctly when building in order to generate profiling information (profiling) - `WASM_BINDGEN_TEST_COVERAGE` environment...

@egasimus PR is open at https://github.com/rustwasm/wasm-bindgen/pull/3782

Try this: ```toml [dev-dependencies] wasm-bindgen-test = { version = "0.3", features = ["coverage"] } [patch.crates-io] wasm-bindgen-test = { git = "https://github.com/aDogCalledSpot/wasm-bindgen", branch = "coverage" } wasm-bindgen = { git =...

@vaxerski could you give a high-level overview of what would need to be done to support this, so that someone could maybe look into it a bit?

Are there possible first steps that could be done in order to slowly move towards this? I dont expect this to be solved with a single PR.