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
I'm playing with compiling C++ libraries to WASM modules over here, it's been great so far, but the issue with loading .wasm from a different directory kills any attempt of making an npm package that can seamlessly work in both node and browsers. So I have two questions here:
Is there some accepted workaround to fix this?
How can I manually load the .wasm file and feed it to the module? Just setting Module.wasmBinary doesn't seem to work:
Hi guys,
I'm playing with compiling C++ libraries to WASM modules over here, it's been great so far, but the issue with loading .wasm from a different directory kills any attempt of making an npm package that can seamlessly work in both node and browsers. So I have two questions here:
Module.wasmBinary
doesn't seem to work:The text was updated successfully, but these errors were encountered: