WebAssembly / WebAssembly/WASI
Add build test
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 5.8k
- Forks
- 333
- Avg merge
- 2d 13h
- Merged PRs (30d)
- 3
Description
I'm trying to figure out what signatures the current source build as, and there are some dependencies to get this to build which are also in flux. One thing that could make things more easy is to add a github workflow that not just parses the files, but actually constructs wasm out of it. Personally, I want to understand some API impact with less guessing about what the signatures will end up as. It is important to be able to do this without a lot of thinking or cognitive load, and one way to minimize that is to look at a GH workflow that can successfully compile this to wasm and just copy/pasta that.
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 reading the current source-build setup and its dependencies, then inspect how a GitHub workflow can compile the source into WebAssembly. The work is done when the workflow successfully constructs wasm rather than only parsing files, making the resulting signatures easier to inspect for API impact.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions, rust, wasm
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100