wasm-pack Crash Report

[liamcurry]

🐛 Bug description

wasm-pack crashes in Windows 10 when trying to build anything.

Here is the output when trying to build the "hello_world" example from the wasm-bindgen repo.

sagan@DESKTOP-A5G4IFN MINGW64 ~/Documents/sagan-software/wasm-bindgen (master)
$ wasm-pack build examples/hello_world/

  [1/10] Checking `rustc` version...
  [2/10] Checking crate configuration...
  [3/10] Adding WASM target...
  info: component 'rust-std' for target 'wasm32-unknown-unknown' is up to date
  [4/10] Compiling to WASM...
     Compiling proc-macro2 v0.4.25
     Compiling unicode-xid v0.1.0
     Compiling wasm-bindgen-shared v0.2.32 (C:\Users\sagan\Documents\sagan-soft
     Compiling cfg-if v0.1.6
     Compiling lazy_static v1.2.0
     Compiling wasm-bindgen v0.2.32 (C:\Users\sagan\Documents\sagan-software\wa
     Compiling log v0.4.6
     Compiling quote v0.6.10
     Compiling syn v0.15.26
     Compiling wasm-bindgen-backend v0.2.32 (C:\Users\sagan\Documents\sagan-sof
     Compiling wasm-bindgen-macro-support v0.2.32 (C:\Users\sagan\Documents\sag
     Compiling wasm-bindgen-macro v0.2.32 (C:\Users\sagan\Documents\sagan-softw
     Compiling hello_world v0.1.0 (C:\Users\sagan\Documents\sagan-software\wasm
      Finished release [optimized] target(s) in 38.09s
  [5/10] Creating a pkg directory...
  [6/10] Writing a package.json...
   [INFO]: Optional fields missing from Cargo.toml: 'description', 'repository', and 'license'. These are not necessary, but recommended
  [7/10] Copying over your README...
  [8/10] No LICENSE found in Cargo.toml, skipping...
  wasm-bindgen 0.2.31
  [9/10] Installing wasm-bindgen...
| [10/10] Running WASM-bindgen...
Well, this is embarrassing.

wasm-pack had a problem and crashed. To help us diagnose the problem you can send us a crash report.

We have generated a report file at "C:\Users\sagan\AppData\Local\Temp\report-bdf0ec94-6888-4e78-8f8d-de9b9f0043bb.toml". Submit an issue or email with the subject of "wasm-pack Crash Report" and include the report as an attachment.

- Authors: Ashley Williams <ashley666ashley@gmail.com>

We take privacy seriously, and do not perform any automated error collection. In order to improve the software, we rely on people to submit reports.

Thank you kindly!

Here is the report:

sagan@DESKTOP-A5G4IFN MINGW64 ~/Documents/sagan-software/wasm-bindgen (master)
$ cat ~/AppData/Local/Temp/report-bdf0ec94-6888-4e78-8f8d-de9b9f0043bb.toml
name = 'wasm-pack'
operating_system = 'windows'
crate_version = '0.6.0'
explanation = '''
Panic occurred in file 'C:\Users\sagan\.cargo\registry\src\github.com-1ecc6299db9ec823\binary-install-0.0.1\src\lib.rs' at line 231
'''
method = 'Panic'
backtrace = '''
stack backtrace:
   0: <no info> (0x7ff60834cbf5)
   1: <no info> (0x7ff60834bdbc)
   2: <no info> (0x7ff60834bcca)
   3: <no info> (0x7ff6082b7ab7)
   4: <no info> (0x7ff6082b745a)
   5: <no info> (0x7ff6080bb408)
   6: <no info> (0x7ff608379bf5)
   7: <no info> (0x7ff608379704)
   8: <no info> (0x7ff608379652)
   9: <no info> (0x7ff608160ad3)
  10: <no info> (0x7ff6080d26c9)
  11: <no info> (0x7ff6080fadc5)
  12: <no info> (0x7ff6080f97a5)
  13: <no info> (0x7ff6080cb6d6)
  14: <no info> (0x7ff6080bafa4)
  15: <no info> (0x7ff6080b9476)
  16: <no info> (0x7ff608379547)
  17: <no info> (0x7ff608385b62)
  18: <no info> (0x7ff608379f12)
  19: <no info> (0x7ff6080bb487)
  20: <no info> (0x7ff6083cf200)
  21: BaseThreadInitThunk (0x7ff933147e94)'''

🤔 Expected Behavior

It should build without crashing.

👟 Steps to reproduce

1. Use a Windows 10 machine
2. Clone the wasm-bindgen repo
3. run wasm-pack build examples/hello_world/

🌍 Your environment

$ wasm-pack --version
wasm-pack 0.6.0

$ rustc --version
rustc 1.32.0 (9fda7c223 2019-01-16)

[ashleygwilliams]

hi @liamcurry ! thanks for the report and sorry for the trouble. we know about this issue and are currently working on fix (#510). this is a bug in our cargo install wasm-bindgen-cli fallback. we usually attempt to install wasm-bindgen from a binary- but the latest version of wasm-bindgen accidentally did not produce a windows binary.

anyways- to circumvent the issue you can cargo install wasm-bindgen and then run wasm-pack build and be all set! we're really sorry about the inconvenience and hope to publish a patch soon. additionally, the bug should be irrelevant once wasm-bindgen publishes a new version and produces a binary (or adds a binary to the existing release)- which i hope they will do soon :)

[ashleygwilliams]

fun news! wasm-bindgen just published a new version so there will be windows binaries (once https://ci.appveyor.com/project/alexcrichton/wasm-bindgen/builds/21733448 completes). let me know if that works for you once the binary's been published!

[liamcurry]

It works! Thanks!