| Age | Commit message (Collapse) | Author | |
|---|---|---|---|
| 2021-08-16 | fix(ext/fetch): better error if no content-type | Ben Noordhuis | |
| 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-11 | chore: move test files to testdata directory (#11601) | David Sherret | |
| 2021-08-05 | refactor(cli/tests): remove unnecessary void return types (#11577) | Leo K | |
| 2021-07-03 | feat: enable WebAssembly.instantiateStreaming and wasm async compilation ↵ | Andreu Botella | |
| (#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. | |||
 |
index : deno.git | |
| Unnamed repository; edit this file 'description' to name the repository. | User & |
| summaryrefslogtreecommitdiff |