tursodatabase / tursodatabase/libsql
Regression: Cannot use libsql remote in wasm contexts
Open
Nobody has claimed this yet.
- Dominant language
- C
- Stars
- 17.2k
- Forks
- 531
- Avg merge
- 1h 12m
- Merged PRs (30d)
- 1
Description
When turning on the libsql remote feature flag, the mio dependency gets added via tokio.
This breaks WASM compilation.
So currently the WASM feature flag only allows local usage but not connecting to a remote turso instance.
In the past this worked (eg thats why the cloudflare feature exists) but regressed over time...
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 libsql remote feature flag and trace how tokio brings in mio during WASM compilation. Compare the current setup with the cloudflare feature, which the issue identifies as historical context. Done means WASM builds with remote enabled and can connect to a remote Turso instance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, sqlite, wasm
- Domain
- databases
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100