-
Notifications
You must be signed in to change notification settings - Fork 10
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Uncaught error from WebAssembly #21
Comments
Hoping @Fr0stbyteR has an idea here. |
@friskgit how is you code deployed ? Which kind of server ? |
Yes the server need to be configured for *.wasm files to be sent as |
Great, that's what I thought. I will let my web host know that and in the mean time I'm using the hack that works for now. |
Ah, I will check that out, but as i wrote, the simple python server actually does work. It was my web server that didn't work. Sorry for being unclear. |
Hi,
Just for infformation: After compiling a simple Faust patch with faustwasm -wpa I received the following error message from WebAssembly:
Response has unsupported MIME type 'application/octet-stream' expected 'application/wasm'
In my interpretation this would be an error on the part of the server? The same page loads fine on a local server (python3 -m http.server). Changing the following line in create-node.js:
const dspModule = await WebAssembly.compileStreaming(await fetch("./dsp-module.wasm"));
to:
const dspModule = await WebAssembly.compile(await fetch("./dsp-module.wasm").then(res => res.arrayBuffer()));
got rid of the problem and is fine in this particular context. Again, this likely has to do with the servers erroneous response, right?
Best,
/Henrik
The text was updated successfully, but these errors were encountered: