Solidify plan for WASI Preview 2
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 270
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Description
Currently, users who are interested in using WASI Preview 2 APIs are directed to the jco project.
We want to provide this functionality in Node directly, but need a plan on how we want to accomplish this. One idea is to introduce a dependency on jco directly to immediately provide experimental APIs and subsequently implement various Preview 2 interfaces in uvwasi directly where appropriate, such as for https://github.com/WebAssembly/wasi-clocks or https://github.com/WebAssembly/wasi-filesystem.
We should discuss this in our next meeting.
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by reviewing the current jco-based guidance and the proposed wasi-clocks and wasi-filesystem interfaces. Use the next project meeting discussion to compare adding jco as a dependency with implementing Preview 2 interfaces in uvwasi. Done means the project has an agreed, documented implementation plan.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- c, node.js, wasm
- Domain
- operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100