add WASM testing to CI
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 4k
- Forks
- 534
- PR merge metrics
- No merged PRs in 30d
Description
Someone on reddit mentioned that they are hoping WASM support continues to work through the release migration.
The regex crate has never promised WASM support and it is not being tested in CI. With that said, there are plenty of folks using the regex crate in a WASM context, notably regex101.com, so breaking that is not really an option. But given that we aren't doing any testing with WASM, that seems like a problem.
I personally don't have a ton of experience with WASM (yet), so I would love if someone with more expertise in that domain could contribute a patch that adds testing to CI. If there are many different ways of testing CI, then we should have a discussion first. I would definitely like to minimize dependencies on external tooling as much as possible, unless they are mature and not likely to break.
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 reviewing the regex crate's existing CI configuration and how its tests are invoked. Compare mature WASM testing approaches while minimizing external dependencies, then add CI coverage that exercises the crate in a WASM context. Done means WASM support is tested during CI and remains covered through release migrations.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- ci-cd, testing
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100