> Since no alternative has presented itself, every time I revisit wasm-pack I’m pained by new potholes that have risen due to neglect I've had open PRs for a y

> Since no alternative has presented itself, every time I revisit wasm-pack I’m pained by new potholes that have risen due to neglect I've had open PRs for a year now: https://github.com/rustwasm/wasm-pack/pull/937 https://github.com/rustwasm/wasm-pack/pull/937 https://github.com/rustwasm/wasm-pack/pull/1089 https://github.com/rustwasm/wasm-pack/pull/1089 Very straight forward changes. Emailed Ashley about helping with wasm-pack, no response (in response to https://github.com/rustwasm/wasm-pack/issues/928 https://github.com/rustwasm/wasm-pack/issues/928) Updates to wasm-bindgen shouldn't require a change to wasm-pack. It should expose ways to pass arbitrary flags down While having a webpack plugin is nice, I since gave up on wasm-pack & added a build-wasm to my package.json's scripts: https://github.com/serprex/openEtG/commit/9997fb098d168920bb4726857173f45e93b1594a#diff-7ae45ad102eab3b6d7e7896acd08c427a9b25b346470d7bc6507b6481575d519 https://github.com/serprex/openEtG/commit/9997fb098d168920bb... This way if someone wants to contribute to openetg they don't need to install my wasm-pack fork. Ideally wasm-pack-plugin would skip wasm-pack & use wasm-bindgen directly I do hope wasm-bindgen is able to be adequately resourced. It's a pleasure to program wasm modules in Rust