Upgrade wasm-bindgen

[evilpie]

Connections

Description

It seems like just upgrading wasm-bindgen/js-sys/web-sys breaks the WGPU examples:

Uncaught (in promise) RuntimeError: unreachable executed
__wbg_finalize_init http://127.0.0.1:8000/webgl2.js:2039
__wbg_init http://127.0.0.1:8000/webgl2.js:2121
webgl2_bg.wasm:12106005:1

The question is if that is a problem with wasm-bindgen and should be reported upstream, or caused by the vendoring of WebGPU.

Testing

Squash or Rebase?

Checklist

• Run cargo fmt.
• Run taplo format.
• Run cargo clippy --tests. If applicable, add:
  • --target wasm32-unknown-unknown
• Run cargo xtask test to run tests.
• If this contains user-facing changes, add a CHANGELOG.md entry.

[evilpie]

The issue on the wasm-bindgen side was fixed.

[cwfitzgerald]

Nice, thanks!

[cwfitzgerald]

Actually wait, is there any reason to bump these? cargo.lock bumps should update them, as we don't have = dependencies

Question

[evilpie]

True, in fact Cargo.lock already has 0.2.144.