Solidify plan for WASI Preview 2
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 20/100
- Issue type
- Feature
- Clarity
- Needs clarification
- Activity status
- Stale
- Tech stack
- c, node.js, wasm
- Domain
- operating-systems
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.
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.
- Dominant language
- C
- Stars
- 272
- Forks
- 60
- PR merge metrics
- No merged PRs in 30d
Getting set up
- No Dockerfile or Docker Compose file
- No pull request template
- Read the contributing 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.
More from nodejs/uvwasi
-
path_filestat_get returns inval for empty pathsPossibly taken @dannyward630 claimed this 2 days ago. Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 1/5 Under an hour Newbie friendliness 25/100
-
Difficulty 1/5 Under an hour Newbie friendliness 15/100
-
Difficulty 1/5 Under an hour Newbie friendliness 20/100
-
Difficulty 4/5 3-5 days Newbie friendliness 35/100
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
micropython/micropython#19786 ·
Maintainers usually reply within 1 day
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
vercel-labs/zerolang#442 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
Maintainers usually reply within 1 day
-
triage
Difficulty 2/5 1-3 hours Newbie friendliness 67/100
Maintainers usually reply within 1 day
-
mewencode: base256[] and base128[] are indexed out of bounds by a non-ASCII octetPossibly taken @kazu-yamamoto claimed this today. Open
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
kazu-yamamoto/Mew#276 ·
Maintainers usually reply within 1 day