WASM function fails to accept arguments, sometimes

[0x009922]

Steps to reproduce

1. Open crypto-wasm dir in hyperledger-iroha/iroha-javascript repo
2. Bump wasm-bindgen to 0.2.100 in Cargo.toml (as required by @deno/wasmbuild)
3. Run deno run -A jsr:@deno/wasmbuild, it outputs the lib< directory
4. Create and run the following test.ts file:

import { KeyPair } from './lib/iroha_crypto_wasm.js'

// 1.
// console.log(KeyPair.random().public_key().to_multihash_hex())

// 2.
console.log(KeyPair.derive_from_seed({ t: 'hex', c: 'beef' }).public_key().to_multihash_hex())

// 3.
console.log(KeyPair.derive_from_seed({ t: 'hex', c: 'beef' }, 'ed25519').public_key().to_multihash_hex())

Expected

ed01201F69AD5DEF05D7EEF87E257D6184E7B1BBE178FC8B4CA1F1422A5F6225A7A5DA
ed01201F69AD5DEF05D7EEF87E257D6184E7B1BBE178FC8B4CA1F1422A5F6225A7A5DA

Actual

• When running case 2. alone: Error: invalid type: JsValue(Object({"t":"hex","c":"ab"})), expected unit
• When running case 3. alone: Error: invalid type: string "ed25519", expected unit
• When uncommenting case 1.: all three cases work (?)

---

Worth mentioning: I see that @deno/wasmbuild uses --target bundler, so I tried to build the package with wasm-pack build --target bundler and check if I observe the same issues with its output. It works without issues, however.

[0x009922]

Found a difference between the output of @deno/wasmbuild build and wasm-pack build --target bundler - the latter one adds this:

wasm.__wbindgen_start();

So, it started to work after modifying the output of @deno/wasmbuild into this:

import * as wasm from "./iroha_crypto_bg.wasm";
export * from "./iroha_crypto_bg.js";
import { __wbg_set_wasm } from "./iroha_crypto_bg.js";
__wbg_set_wasm(wasm);
+ wasm.__wbindgen_start();

I guess @deno/wasmbuild should output this too.