error on windows.

[LollipopFt]

hi, i received this error, not sure what it means. the .wasm file was able to generate properly.

C:\Users\lollipopft\rust\projects\roguelike>cargo run --release --target=wasm32-unknown-unknown
    Finished release [optimized] target(s) in 0.86s
     Running `wasm-server-runner target\wasm32-unknown-unknown\release\roguelike.wasm`
thread 'main' panicked at 'index out of bounds: the len is 0 but the index is 0', C:\Users\lollipopft\rust\.cargo\registry\src\github.com-1ecc6299db9ec823\wasm-bindgen-cli-support-0.2.79\src\descriptor.rs:208:15
stack backtrace:
   0:     0x7ff722d26d3f - <unknown>
   1:     0x7ff722d417ca - <unknown>
   2:     0x7ff722d20a08 - <unknown>
   3:     0x7ff722d2989b - <unknown>
   4:     0x7ff722d29394 - <unknown>
   5:     0x7ff722d29d9c - <unknown>
   6:     0x7ff722d29c5b - <unknown>
   7:     0x7ff722d27687 - <unknown>
   8:     0x7ff722d29959 - <unknown>
   9:     0x7ff722d6f910 - <unknown>
  10:     0x7ff722d6f8d7 - <unknown>
  11:     0x7ff722aa2410 - <unknown>
  12:     0x7ff722aa2813 - <unknown>
  13:     0x7ff722aa1fca - <unknown>
  14:     0x7ff722aa8fa7 - <unknown>
  15:     0x7ff722a7eaac - <unknown>
  16:     0x7ff722a743a8 - <unknown>
  17:     0x7ff722a6d01c - <unknown>
  18:     0x7ff722a17d16 - <unknown>
  19:     0x7ff722a2c86a - <unknown>
  20:     0x7ff722d2659f - <unknown>
  21:     0x7ff722a716f7 - <unknown>
  22:     0x7ff722d4810c - <unknown>
  23:     0x7ff9d1977034 - BaseThreadInitThunk
  24:     0x7ff9d2c82651 - RtlUserThreadStart
error: process didn't exit successfully: `wasm-server-runner target\wasm32-unknown-unknown\release\roguelike.wasm` (exit code: 101)

[jakobhellermann]

I've seen an error message like that once when the version of wasm-bindgen in the wasm file didn't match the version in wasm-server-runner. Can you run the command cargo tree -p wasm-bindgen --target wasm32-unknown-unknown --depth 0 and send the output?

[LollipopFt]

wasm-bindgen v0.2.75

[jakobhellermann]

Right, wasm-server-runner uses the latest version which is v0.2.79. Does a simple cargo update or cargo update -p wasm-bindgen --precise 0.2.79 fix the issue?

[LollipopFt]

yes, thank you!

[LollipopFt]

yes, thank you!