-
Notifications
You must be signed in to change notification settings - Fork 5.4k
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
WebAssembly.instantiateStreaming does not work with Response #7259
Comments
@caspervonb do we have a test for this? |
Hmm, apparently I used a buffer source in the test when I enabled that flag 🤔 |
@caspervonb Do we need to temporarily disable instantiateStreaming? Or implement it with Response? Because modules using Response are broken since they check for the existence of instantiateStreaming before if (WebAssembly.instantiateStreaming) {
// use instantiateStreaming()
} else {
// get the buffer then use instantiate()
} |
Oh right, that's bad.. uhm, I'll get back to you. |
I'm able to make this work by doing |
Ahh, saw that Deno had WebAssembly.{compileStreaming, instantiateStreaming}, and thought that it would be fun to try to instantiate ~6 wasm files and set up a project. Then some particularly misleading errors appeared :) In my opinion, If it doesn't work correctly, it should not be exposed at all. Can we get the PR that caused this to be reverted until this is properly sorted out? |
Hey folks, is there any progress here? I'd like to use Deno for testing my wasm compiled from Rust with |
Temporary workaround could be to call |
The WebAssembly streaming APIs used to be enabled, but used to take buffer sources as their first argument (see denoland#6154 and denoland#7259). This change reenables it, requiring a Promise<Response> instead.
The WebAssembly streaming APIs used to be enabled, but used to take buffer sources as their first argument (see denoland#6154 and denoland#7259). This change reenables them, requiring a Promise<Response> instead, as well as enables asynchronous compilation of WebAssembly modules.
hazae41/foras#1
Since Deno 1.3.1, WebAssembly.instanciateStreaming throws the following error when module is an instance of Response (from fetch)
The text was updated successfully, but these errors were encountered: