Create uvwasi executable based on C API ?
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, wasm
- Domain
- operating-systems
Research direction
The issue names uvwasi, the WASI C API, wee8, and a dynamically linked libwasm.so, but no files or tests. Start by reviewing uvwasi's existing runtime integration and the referenced C API requirements; completion would require a defined executable design that works with a replaceable WASM engine.
Written by the indexing model from the issue text.
Description
Can we take uvwasi and hooks it up the wasm runtime with the C API?
Then we could have a common WASI runtime that would work with any wasm engine that exposes the C-API.
For example we could take uivwasi and wee8 (https://docs.google.com/document/d/1oFPHyNb_eXg6NzrE6xJDNPdJrHMZvx0LqsD6wpbd9vY/edit#heading=h.4tfb7x3beh2l) and create something like node but without any JS.
Ideally the uvwasi executable would dynamically link to libwasm.so (providing the C API) so that any wasm engine would be dropped in without even re-compiling.
- 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
FujiNetWIFI/fujinet-firmware#2079 ·
Maintainers usually reply within 1 day
-
bug
Difficulty 1/5 Under an hour Newbie friendliness 84/100
VirusTotal/yara#2255 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 66/100
-
state:needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
zed-industries/zed#65836 · 1 reaction ·
Maintainers usually reply within 1 day
-
bug
Difficulty 2/5 1-3 hours Newbie friendliness 76/100
neutralinojs/neutralinojs#1861 ·
Maintainers usually reply within 1 day