Compatibility with Qwik
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 23
- Forks
- 0
- PR merge metrics
- No merged PRs in 30d
Description
Currently, Qwik does not natively support Declarative Shadow DOM, which wesc relies on. Qwik's design philosophy focuses on delaying the execution and download of JavaScript for as long as possible, which is different from traditional SSR frameworks that wesc is designed to work with.
While it's theoretically possible to use wesc to add Shadow DOM boundaries to a Qwik application, it would likely require significant modifications to both wesc and Qwik applications, and may not align with Qwik's design philosophy.
We are very interested in using the selectlist polyfill web component, but the major tradeoff seems to be hydration in polyfill browsers breaking the layout (Qwik does not have hydration, the JavaScript is serialized into the HTML). If anyone has any ideas for how this might work, we would love to hear it. We've been trying to figure out a way to get this to work natively in Qwik without breaking the design philosophy of the framework.
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, tests, or entry points are named. Start by examining wesc's Declarative Shadow DOM integration and Qwik's serialized-JavaScript, no-hydration behavior; done would be a documented or demonstrated compatibility approach that avoids layout breakage in polyfill browsers.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- javascript
- Domain
- frontend, web-dev
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100