You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When following the instructions for wasm2js (https://rustwasm.github.io/wasm-bindgen/examples/wasm2js.html) it appears the JS glue code generated by wasm-pack still retains the old .wasm filename. I also had to update package.json to replace .wasm . Even doing this my local www server still remained nonfunctional (no evidence of execution).
I didn’t spend much time on this as the larger project was more of a proof-of-concept as to what order of magnitude effort would be required to compile backend code for frontend.
My next try would probably be to look at the generated js to see if the glue code is still necessary. I suspect I should have pointed my test server directly to the wasm2js output (this would still require changing package.json though)
That being said, I suspect I may have been doing something wrong since neither of the above steps were mentioned in the manual, and it seems like IE10 compatibility is something someone would have looked into before now.
The text was updated successfully, but these errors were encountered:
This needed and update now that we're explicitly importing `*.wasm` to
import `*.js` instead. Additionally this was moved over to the `web`
target to avoid needing Webpack
Closesrustwasm#1743
This needed and update now that we're explicitly importing `*.wasm` to
import `*.js` instead. Additionally this was moved over to the `web`
target to avoid needing Webpack
Closes#1743
When following the instructions for wasm2js (https://rustwasm.github.io/wasm-bindgen/examples/wasm2js.html) it appears the JS glue code generated by wasm-pack still retains the old .wasm filename. I also had to update package.json to replace .wasm . Even doing this my local www server still remained nonfunctional (no evidence of execution).
I didn’t spend much time on this as the larger project was more of a proof-of-concept as to what order of magnitude effort would be required to compile backend code for frontend.
My next try would probably be to look at the generated js to see if the glue code is still necessary. I suspect I should have pointed my test server directly to the wasm2js output (this would still require changing package.json though)
That being said, I suspect I may have been doing something wrong since neither of the above steps were mentioned in the manual, and it seems like IE10 compatibility is something someone would have looked into before now.
The text was updated successfully, but these errors were encountered: