ianjsikes / rust-wasm-webpack-tutorial Goto Github PK

Please advice how to resolve the following issue in running the tutorial:

[Thu Apr 26 2018 08:05:55 GMT-0700 (PDT)] "GET /" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36"
[Thu Apr 26 2018 08:05:55 GMT-0700 (PDT)] "GET /build/bundle.js" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36"
[Thu Apr 26 2018 08:05:55 GMT-0700 (PDT)] "GET /rust_wasm_webpack_tutorial.wasm" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36"
[Thu Apr 26 2018 08:05:55 GMT-0700 (PDT)] "GET /rust_wasm_webpack_tutorial.wasm" Error (404): "Not found"
[Thu Apr 26 2018 08:05:55 GMT-0700 (PDT)] "GET /rust_wasm_webpack_tutorial.wasm" "Mozilla/5.0 (X11; Linux x86_64) AppleWebKit/537.36 (KHTML, like Gecko) Chrome/66.0.3359.117 Safari/537.36"
[Thu Apr 26 2018 08:05:55 GMT-0700 (PDT)] "GET /rust_wasm_webpack_tutorial.wasm" Error (404): "Not found"

I just compiled and ran the code and I ran into an error when I tried to look at the console output. This is the error I received:

abort("on the web, we need the wasm binary to be preloaded and set on Module['wasmBinary']. emcc.py will do that for you when generating HTML (but not JS)")

Is there a problem with my wasm toolchain?

I got this error trying to load the webpage. How can I solve it?

Uncaught TypeError: n(...).initialize is not a function (bundle.js:1)

The size of bundle.js is quite large with 884kB. In my version I've managed to reduce the size to 129KB in release mode, but the config is not very nice:
https://github.com/bwasty/rust-wasm-webpack-template/blob/f0d3cf5437333700baf18f46f825594e9105271c/webpack.config.js#L33-L85

I don't fully understand how all those dependencies are pulled in - do you have an idea how to do this better?

Note: I'd have opened this on rust-wasm-loader, but the issue tracker is switched off.

I get this in the console: Assertion failed: the runtime was exited (use NO_EXIT_RUNTIME to keep it alive after main() exits). This is after I see Calling rust functions from javascript! but I do not see the result of calling the function.