doc: update WebAssembly strategy with Wasm Web API

Refs: #42660 Refs: #42701 PR-URL: #42836 Reviewed-By: Colin Ihrig <[email protected]> Reviewed-By: Akhil Marsonya <[email protected]> Reviewed-By: Luigi Pinca <[email protected]> Reviewed-By: Zeyu Yang <[email protected]> Reviewed-By: Jiawen Geng <[email protected]> Reviewed-By: Darshan Sen <[email protected]>
nodejs · Jul 12, 2022 · 9f2df9e · 9f2df9e
1 parent bd2eb92
commit 9f2df9e
Showing 1 changed file with 3 additions and 3 deletions.
diff --git a/doc/contributing/maintaining-web-assembly.md b/doc/contributing/maintaining-web-assembly.md
@@ -35,9 +35,9 @@ APIs as important:
 * WebAssembly System Interface (WASI). This provides the ability for
   WebAssembly to interact with the outside world. Node.js currently
   has an implementation (see below for more details).
-* WebAssembly streaming APIs - As the Node.js implementation of
-  [WebStreams](https://nodejs.org/api/webstreams.html) matures,
-  implementing the embedder APIs to enable streaming with WebAssembly
+* [WebAssembly Web API](https://www.w3.org/TR/wasm-web-api-1/). Node.js
+  currently has an implementation of streaming module compilation and
+  instantiation. As this and other specifications evolve, keeping up with them
   will be important.
 * [WebAssembly Component Model](https://github.com/WebAssembly/component-model/).
   This API is still in the definition stage but the project should