[QUIC Phase 1] Fix WASM Build Dependencies
Open
Nobody has claimed this yet.
phase-1
quic-implementation
- Dominant language
- TypeScript
- Stars
- 812
- Forks
- 175
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
Task
Resolve aws-lc-sys/bindgen dependency issues to enable WASM compilation.
Agent
system-architect
Current Issue
error: failed to compile aws-lc-sys with bindgen
Solution Options
- Use ring feature exclusively (no aws-lc-sys)
- Pre-generate bindings for WASM target
- Use wasm32-wasi target instead of wasm32-unknown-unknown
Acceptance Criteria
-
cargo build --target wasm32-unknown-unknown --features wasmsucceeds - OR
wasm-pack buildsucceeds - WASM binary generated (<500KB)
- No bindgen errors
Parent Epic
#15
Estimated Effort
30-60 minutes
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
No files or tests are named. Start by running cargo build --target wasm32-unknown-unknown --features wasm and inspect the aws-lc-sys bindgen failure; compare the listed ring, pre-generated bindings, and wasm32-wasi options. Done means a WASM build succeeds without bindgen errors and produces a binary under 500KB, or wasm-pack build succeeds.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust, wasm
- Domain
- build-system
- Issue type
- Bug
- Difficulty
- 3/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100