UI components powered by Finite State Machines. Created by @thesegunadebayo

Zag.js retweeted
Would also 100% recommend checking out other projects from @thesegunadebayo - Panda CSS, Zag and Ark are really good.. and compatible with almost every framework, not just React.
Zag.js was nominated for the React Open Source Awards 2024 🎉 Kindly vote for Zag.js in the “PRODUCTIVITY BOOSTER” category 👇🏻 docs.google.com/forms/d/e/1F…
2
5
1,574
Zag.js was nominated for the React Open Source Awards 2024 🎉 Kindly vote for Zag.js in the “PRODUCTIVITY BOOSTER” category 👇🏻 docs.google.com/forms/d/e/1F…
2
5
22
3,539
ShadCN hype is cool and all but.. 😅 ZERO COVERAGE ANYWHERE on.. @zag_js, @ark_ui_, and Park UI... OOH, a beauty! 🤯🔥❤️ Components for all major frameworks: React, Solid, and Vue! FINALLY! @t3dotgg check it out!
1
4
788
Let's build some state machines 🚀
Join @farzad_yz and me on Wednesday as we wrap up the Draggable Panel state machine we've been building in public. 🔴 Save the date and link below 👇🏻 Link here: youtube.com/live/YosVwyHNEHE We'll add two new features: Panel Boundary and Dockable Region. As always, using Stately and XState v5.
3
742
.@zag_js implements common component patterns using the state machine methodology, offering a Vue wrapper 💚📦️ - madewithvuejs.com/zag-for-vu…
3
11
2,795
Agree with @filrakowski - Customizability - Composition - Upgradability Are the main thing. Accessibility could also be a really great touch ! If you want to build components from scratch, you can use something like @zag_js so that you focus on the Vue implem not logic!
1
3
344
Really glad to see that Svelte 5 supports events in spread props. Big kudos to @izznatsir for working on the @zag_js integration for Svelte🔥 Feels good to have a machine logic drive multiple frameworks: React, Vue, Solid, and soon Svelte
2
6
57
4,216
This reminds me why we model most UI components in @zag_js with vanilla DOM methods and State machines. Most components can be built without framework-specific code. The DOM is quite robust ✨ Frameworks are tools; our role as engineers is to know which tool to use per time.
Replying to @ryanflorence
specifically felt like an idiot because a younger version of me would have written the same code just had let the framework infect too much of my brain and was forcing it into every situation
2
6
83
15,744
With @sveltejs 5 $props, event props spreading is now possible 👀 svelte.dev/blog/runes#runtim… youtu.be/gGwnF-lxS_Q?si=Pxls… Time for @zag_js to support svelte? github.com/chakra-ui/zag/iss… github.com/chakra-ui/zag/dis… So @ark_ui_ will also support svelte 👀🔥 cc @thesegunadebayo
1
1
10
2,364
👉 @zag_js is a new approach to the component design process, designed to help you avoid re-inventing the wheel and build better UI components regardless of framework. zagjs.com/ #vuejsfeed #vuejs #UI
4
10
2,188
If you're into state machines, I'm pretty sure you're gonna love @zag_js 😊
1
2
880
.@zag_js implements common component patterns using the state machine methodology, offering a Vue wrapper 💚📦️ - madewithvuejs.com/zag-for-vu…
7
22
6,443
I was struggling a bit trying to leverage some of the new hotness in @zag_js with @chakra_ui . Turns out the examples on the zag website leverage Chakra. Problem solved. github.com/chakra-ui/zag/tre…
1
1
1
1,361
9/9 🧵 Zag.js @zag_js By chance, I tried to use Zag.js, oh man it's awesome experience! Back to familiar HTML tags. And bind attr. Full customization, Clean docs and types. Enough unstyled components. It only took me three hours to migrate from Headless UI in the end ~ 🤗
1
1
17
2,256
Replying to @marcelpociot
Over my pass 3 moths constant experimentation. My answer Zag.js . Please have try ~ 🤗 @zag_js zagjs.com/
1
5
1,137
.@zag_js implements common component patterns using the state machine methodology, offering a Vue wrapper 💚📦️ - madewithvuejs.com/zag-for-vu…
6
19
5,107
i’ve long wished for an accessible unstyled accessible component library like @radix_ui for other frameworks. it’s a huge reason i tend to pick react for new projects. recently someone pointed me to @zag_js and 🤯
2
1
3
2,068
Totally agree! The same applies to component and styling libraries.
Libraries that work with a specific framework benefit only that framework’s ecosystem. Libraries that work with any framework benefit all framework ecosystems. Let’s make libraries framework-independent whenever feasible.
2
25
6,066