4 commits

Author	SHA1	Message	Date
Ben Noordhuis	6ced7b0383	fix(ext/fetch): better error if no content-type ... The streaming WASM support code inspects the Response object's Content-Type header but if that was missing, it failed with a fairly inscrutable "String.prototype.toLowerCase called on null or undefined" exception. Now it raises a more legible "Invalid WebAssembly content type" exception.	2021-08-16 19:45:37 +02:00
David Sherret	15a763152f	chore: move test files to testdata directory (#11601)	2021-08-11 10:20:47 -04:00
Leo K	3f0cf9619f	refactor(cli/tests): remove unnecessary void return types (#11577)	2021-08-05 13:08:58 +02:00
Andreu Botella	ffa75be480	feat: enable WebAssembly.instantiateStreaming and wasm async compilation (#11200) ... The WebAssembly streaming APIs used to be enabled, but used to take buffer sources as their first argument (see #6154 and #7259). This change re-enables them, requiring a Promise<Response> instead, as well as enabling asynchronous compilation of WebAssembly modules.	2021-07-03 23:33:36 +02:00