spinframework / spinframework/spin
Test ability to build in wasm in CI for a few crates.
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 6.5k
- Forks
- 310
- Avg merge
- 1d 20h
- Merged PRs (30d)
- 24
Description
The following list of crates are known to be used as wasm dependencies in spin-test. Since we rely on their ability to be built in wasm, we should enforce that they remain so in CI.
spin-routes(introduced in https://github.com/spinframework/spin/pull/3169)spin-outbound-networking-configspin-serdespin-locked-appspin-expressionsspin-manifest
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 inspecting the repository's existing CI configuration and the wasm build setup used by spin-test; use the six listed crates as the scope. Done means CI explicitly builds those crates for wasm and fails when one no longer builds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- build-system, ci-cd
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100