no ssvm mapping for bindgen

[Halkcyon]

Looking at one of your articles, I am running into issues with the first bit of sample.

maximilian@💻:~/repos/second-state$ yarn ssvmup build
yarn run v1.22.4
$ /home/maximilian/repos/second-state/node_modules/.bin/ssvmup build
[INFO]: Checking for the Wasm target...
[INFO]: Compiling to Wasm...
    Finished release [optimized] target(s) in 0.07s
:-) [WARN]: origin crate has no README
[INFO]: Installing wasm-bindgen...
thread 'main' panicked at 'called `Result::unwrap()` on an `Err` value: ErrorMessage { msg: "no ssvm mapping for bindgen 0.2.65" }', src/install/mod.rs:149:20

The sample didn't have any examples of Cargo.toml, so through some trial and error, I've used the latest wasm-bindgen version.

[dependencies]
wasm-bindgen = "0.2.65"

[lib]
crate-type = ["cdylib", "rlib"]

Lastly, the error report:

name = 'ssvmup'
operating_system = 'unix:Ubuntu'
crate_version = '0.1.11'
explanation = '''
Panic occurred in file 'src/install/mod.rs' at line 149
'''
method = 'Panic'
backtrace = '''
   0:     0x56133faa4387 - backtrace::backtrace::trace::h79139ee5ae83da42
   1:     0x56133faa2263 - backtrace::capture::Backtrace::new::h31ca4dd762c8d675
   2:     0x56133f9f3019 - human_panic::report::Report::new::hd0cfc07ee016080c
   3:     0x56133f9f283b - human_panic::handle_dump::haa417dfa47d59a1f
   4:     0x56133f6fdd4c - ssvmup::setup_panic_hooks::{{closure}}::h714a1c417cc0903a
   5:     0x56133fad6c55 - std::panicking::rust_panic_with_hook::h1f2449d529a25f22
                               at src/libstd/panicking.rs:474
   6:     0x56133fad676b - rust_begin_unwind
                               at src/libstd/panicking.rs:378
   7:     0x56133fafb251 - core::panicking::panic_fmt::h2c05f81b567d1861
                               at src/libcore/panicking.rs:85
   8:     0x56133fafb053 - core::option::expect_none_failed::ha9782a6ef355446f
                               at src/libcore/option.rs:1211
   9:     0x56133f751e5f - ssvmup::install::download_prebuilt::h1bc678da6002c711
  10:     0x56133f750543 - ssvmup::install::download_prebuilt_or_cargo_install::h7bbf3aa5a5724474
  11:     0x56133f70e44c - ssvmup::command::build::Build::step_install_wasm_bindgen::h7025f176e071b36b
  12:     0x56133f70cf00 - ssvmup::command::build::Build::run::h8b1711bc4be9e55f
  13:     0x56133f708dc3 - ssvmup::command::run_ssvmup::hfc4a5d1a287f4849
  14:     0x56133f6fd99f - ssvmup::main::h235fcfb9e09737b7
  15:     0x56133f6fe373 - std::rt::lang_start::{{closure}}::h0019f8b6a3fb92ea
  16:     0x56133fad6643 - std::rt::lang_start_internal::{{closure}}::h9a4aa16acf1cdc99
                               at src/libstd/rt.rs:52
                           std::panicking::try::do_call::h0b6fc9f6090c1e2b
                               at src/libstd/panicking.rs:303
  17:     0x56133fae0e07 - __rust_maybe_catch_panic
                               at src/libpanic_unwind/lib.rs:86
  18:     0x56133fad716c - std::panicking::try::h9eaeeaa81242ec77
                               at src/libstd/panicking.rs:281
                           std::panic::catch_unwind::h07d504c1b691e8fb
                               at src/libstd/panic.rs:394
                           std::rt::lang_start_internal::hcea4e704875ab132
                               at src/libstd/rt.rs:51
  19:     0x56133f6fddf2 - main
  20:     0x7f26694590b3 - __libc_start_main
  21:     0x56133f6f75da - _start
  22:                0x0 - <unknown>
'''

[Halkcyon]

I have found my issue from looking at the template project from a different article where it's pinned @ 0.2.61. If the project follows semver, you may want to consider changing the pinning to ~0.2.0

[juntao]

Thank you for the feedback. Yes, I agree we should make it more robust -- or at least give better error messages.