microsoft / microsoft/vscode-wasm
Leverage WASI Preview2
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 456
- Forks
- 40
- Avg merge
- 3d 2h
- Merged PRs (30d)
- 4
Description
I believe a lot could be simplified by leveraging the WASI preview2 + WIT work that is happening here. From the JavaScript binding generation perspective, you might have a look in this repo too: https://github.com/bytecodealliance/jco.
Contributor guide
No contributing guide indexed for this repository
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 reading the WASI Preview2 and WIT work in the linked preview2-prototyping repository, then review jco for JavaScript binding generation. Compare those approaches with this repository’s VS Code extension-host implementation and define which simplifications are feasible. Done means a concrete, agreed scope for adopting Preview2 and WIT.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- typescript, wasm
- Domain
- devtools, operating-systems
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100