testcontainers / testcontainers/testcontainers-rs
Maybe make wasm a feature switch?
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 1.1k
- Forks
- 197
- PR merge metrics
- No merged PRs in 30d
Description
I'm working on a project that uses indicatif, and I'm trying to add testcontainers-rs for testing. Both crates can compile to WebAssembly even though my project is not targeting WebAssembly.
Unfortunately, each crate pulls in a different version of the WebAssembly toolchain, and since only one WebAssembly linker can exist in a source tree, this causes a conflict that prevents me from using both crates together.
It would be helpful if testcontainers-rs could make its WebAssembly support optional behind a feature flag, similar to how chrono handles it.
Thanks :)
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
No file or test is named in the issue. Start by inspecting testcontainers-rs's dependency and feature configuration, then compare how chrono handles optional WebAssembly support. Done means WebAssembly support can be enabled through an optional feature without forcing the toolchain into projects that do not target WebAssembly.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- build-system, testing
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 38/100