Note downstream you can use this without the dev-dep obviously, this is just needed to enforce wasm check in CI so that we are not breaking it in the future

LGTM, but would this check have actually caught the getrandom thing? My understanding is that if you compile without the js feature you'll get a runtime panic, so just running cargo check won't have noticed it.

Regardless, this CI job is an improvement over having nothing.

It seems it's a compile time check and without the getrandom thing the job would fail https://github.com/RCasatta/rust-elements/actions/runs/10578325188/job/29308193852?pr=2

Heads up that on my system I had to add another cargo update -p line for bumpalo after this. cargo does the right thing if you use 1.56.1 consistently but if you use a recent cargo and then downgrade to 1.56.1 it's a bit of work.

But I want to update the MSRV here to 1.63 and start committing lockfiles anyway so I won't worry about it for now.