WebAssembly / WebAssembly/binaryen
standalone (non-js) binaryen.wasm
Nobody has claimed this yet.
- Dominant language
- WebAssembly
- Stars
- 8.6k
- Forks
- 885
- Avg merge
- 1d 19h
- Merged PRs (30d)
- 69
Description
Toolchains such as TinyGo have the ability to run wasm (ex via wazero), but are currently forking processes in order to optimize wasm they generate. It would be great to have a standalone or wasi target of Binaryen so that non-browser compilers can use tools here without forking.
Tips on how to achieve this are thanks to @kripken https://github.com/WebAssembly/binaryen/issues/1051#issuecomment-1298890256
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 with the guidance linked from WebAssembly/binaryen issue 1051, then inspect Binaryen's existing optimizer and toolchain entry points. Done means providing a standalone or WASI Binaryen target that non-browser toolchains such as TinyGo can use without forking a process.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- wasm
- Domain
- compilers
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 25/100