Closed andreubotella closed 1 year ago
Can we make sure to explicitly reference that the Web API is in scope too? (Many server runtimes initially didn't support it.)
Can we make sure to explicitly reference that the Web API is in scope too? (Many server runtimes initially didn't support it.)
Added. This PR should not be merged before #45 though, since that adds the fetch APIs.
As discussed in today's WinterCG meeting, although the WebAssembly JS API (as well as the web API) is built into all mainstream JS engines, it is not officially part of the JS language. (In fact, Ladybird, the Serenity OS browser, implements the JS and wasm engines separately.)
As such, since web-interoperable runtimes are expected to support WebAssembly, it follows that the WebAssembly JS and Web API should be included in the list.
(The WebAssembly Web API should be included as well, but cannot be included at the moment because fetch'sResponse
class is a precondition for it. See #27.)