You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Ever since v2, there have been some occasional mentions that v3 is planned to be framework-agnostic. Now that v3 came out, it seems like it is not yet framework-agnostic, but can be adapted to other frameworks much more easily, since there is no Framer Motion dependency anymore, and all the styles were decoupled into a separate package.
The biggest hurdle as of right now is the React-Aria dependency.
The most similar framework-agnostic alternative is Ark-UI, but there is some mismatch between "components", e.g., Accordion doesn't have Accordion.Heading, has a different name for Accordion.Panel, absence of data-pressed, etc.; so I assume there is bound to be some friction in rewriting it in Ark-UI.
Another alternative seems to be the Zag.JS (library behind Ark-UI components). With Zag.JS I think it is possible to match the exact components React-Aria uses, and get the desired data attributes.
I just wanted to share my thoughts on how it can be made framework-agnostic. Perhaps there is an internal roadmap for a unified logic layer that I’m not aware of?
I’m considering creating a proof-of-concept to see if it is possible to replicate the existing API and data-attributes using Zag's machines and Vue.
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
-
Ever since v2, there have been some occasional mentions that v3 is planned to be framework-agnostic. Now that v3 came out, it seems like it is not yet framework-agnostic, but can be adapted to other frameworks much more easily, since there is no Framer Motion dependency anymore, and all the styles were decoupled into a separate package.
The biggest hurdle as of right now is the React-Aria dependency.
The most similar framework-agnostic alternative is Ark-UI, but there is some mismatch between "components", e.g., Accordion doesn't have
Accordion.Heading, has a different name forAccordion.Panel, absence ofdata-pressed, etc.; so I assume there is bound to be some friction in rewriting it in Ark-UI.Another alternative seems to be the Zag.JS (library behind Ark-UI components). With Zag.JS I think it is possible to match the exact components React-Aria uses, and get the desired
dataattributes.I just wanted to share my thoughts on how it can be made framework-agnostic. Perhaps there is an internal roadmap for a unified logic layer that I’m not aware of?
I’m considering creating a proof-of-concept to see if it is possible to replicate the existing API and
data-attributesusing Zag's machines and Vue.Beta Was this translation helpful? Give feedback.
All reactions