`wasm-pack test` fails on wasm SIMD opcodes

[workingjubilee]

🐛 Bug description

wasm-pack test, apparently due to recent refinements in wasm SIMD opcodes, fails on new opcodes.
Issue propagating from rustwasm/wasm-bindgen#2522

An example from CI: https://travis-ci.com/github/rust-lang/stdsimd/jobs/497585556

Error: failed to deserialize wasm module

Caused by:
    0: failed to parse code section
    1: Unknown 0xfd opcode (at offset 568559)

This occurred after I added SIMD comparisons (simd_eq, etc) to tests, which looks like it's fixed in bytecodealliance/wasm-tools#222, so hopefully it's a matter of "just" updating dependencies.

🤔 Expected Behavior

The tests should have run and either passed, or failed for more interesting reasons than a toolchain failure.

👟 Steps to reproduce

On Windows:

> git clone https://github.com/rust-lang/stdsimd
> $Env:RUSTFLAGS="-Ctarget-feature=+simd128"
> wasm-pack test --release --firefox crates/core_simd

On Linux:

$ git clone https://github.com/rust-lang/stdsimd
$ RUSTFLAGS="-Ctarget-feature=+simd128" wasm-pack test --release --firefox crates/core_simd

🌍 Your environment

Include the relevant details of your environment.
wasm-pack version:

> wasm-pack --version --verbose
wasm-pack 0.9.1

rustc version:

> rustc --version --verbose
rustc 1.53.0-nightly (16bf626a3 2021-04-14)
binary: rustc
commit-hash: 16bf626a31cb5b121d0bca2baa969b4f67eb0dab
commit-date: 2021-04-14
host: x86_64-pc-windows-msvc
release: 1.53.0-nightly
LLVM version: 12.0.0

[workingjubilee]

Aha, I didn't fully understand how wasm-pack worked at the time I filed this ticket. After some experimentation I verified the problem was almost certainly a lockfile barring it from picking up the actual latest version. I don't remember what was going down that this remained the case even in CI, but I feel confident assigning the issue to somewhere between user error and hidden caching, at the moment.

For anyone else who has this issue, you will want to specify in your Cargo.toml a recent enough version to force the lockfile forward to at least wasm-bindgen 0.2.74, e.g.

wasm-bindgen = "0.2.76"
wasm-bindgen-test = "0.3.26"

Also you can cargo install wasm-bindgen-cli --force locally and pass --mode no-install if you want to control it at the user level, like how it was done in The Olden Days.