Replies: 3 comments
-
Hey, I'm pretty much in the same situation and of the same mind - we're currently using Chakra but considering switching to Lit, and hence I've been investigating Zag. I've created a framework package adapted and refined from #1210). I started it as a POC, but now working on an e2e testing suite and hoping it can turn into something fully supported. Hopefully a contribution for a |
Beta Was this translation helpful? Give feedback.
-
We're definitely open to a community contribution for |
Beta Was this translation helpful? Give feedback.
-
Very much in WIP still, but open for comments: #2698 Screen.Recording.2025-09-09.at.12.46.26.mov |
Beta Was this translation helpful? Give feedback.
Uh oh!
There was an error while loading. Please reload this page.
-
Hi 👋,
I’m evaluating Zag for building an enterprise design system based on Web Components (Lit).
Currently, I see wrappers for React, Vue, Solid, and Svelte, but not for Lit.
I also found community experiments (like #1210), but they seem incomplete (e.g. dropdown issues).
My questions are:
Is official Lit support on the roadmap?
If yes, do you have an ETA or milestones?
If no, what would be your recommended approach for integrating Zag with Lit today?
I also believe Lit support would perfectly align with Zag’s philosophy: Write the logic once, render anywhere.
With Lit and Web Components, it becomes possible to build accessible, framework-agnostic components once and then consume them in React, Vue, Angular, or any other environment with simple wrappers.
This could open up a huge adoption opportunity for Zag, especially in enterprise contexts where companies are moving toward design systems based on Web Components for cross-framework compatibility.
Thanks a lot for your amazing work 🙏
Beta Was this translation helpful? Give feedback.
All reactions