Skip to content

Commit

Permalink
doc: update WebAssembly strategy with Wasm Web API
Browse files Browse the repository at this point in the history
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>
  • Loading branch information
tniessen authored and targos committed Jul 12, 2022
1 parent bd2eb92 commit 9f2df9e
Showing 1 changed file with 3 additions and 3 deletions.
6 changes: 3 additions & 3 deletions doc/contributing/maintaining-web-assembly.md
Expand Up @@ -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
Expand Down

0 comments on commit 9f2df9e

Please sign in to comment.