doc: update WebAssembly strategy with Wasm Web API

tniessen · targos · commit 9b61ac2617d2 · 2022-04-28T06:57:24.000+02:00
Refs: #42660 Refs: #42701 PR-URL: #42836 Reviewed-By: Colin Ihrig <cjihrig@gmail.com> Reviewed-By: Akhil Marsonya <akhil.marsonya27@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Zeyu Yang <himself65@outlook.com> Reviewed-By: Jiawen Geng <technicalcute@gmail.com> Reviewed-By: Darshan Sen <raisinten@gmail.com>
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
