RFC 0001: Lazy components & code splitting
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 23
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Tracking issue for RFC 0001 (rfcs/0001-lazy-components.md).
Proposal: let a consumer load a component lazily via w-lazy on <link rel="definition">. wesc emits a self-describing placeholder (data-w-*) and ships the component's DSD fragment + JS as a separate bundle the client fetches on demand (the islands pattern, via Declarative Shadow DOM + slots).
See the RFC for the full design, drawbacks, prior art (Astro / RSC / webpack), and open questions. Discussion and review welcome here.
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 reading rfcs/0001-lazy-components.md, then review the linked discussion and its open questions about lazy loading, Declarative Shadow DOM, slots, and separate bundles. The issue does not define a concrete implementation boundary or completion criteria; those need to be established from the RFC before work begins.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript, rust
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100