Review/Add more libraries

[brc-dd]

Hi, there! The following libraries can also be added to the data 🙌

• https://github.com/chakra-ui/zag -- https://zagjs.com/
• https://github.com/chakra-ui/ark -- https://ark-ui.com/
• https://github.com/chakra-ui/chakra-ui-vue-next -- https://next.vue.chakra-ui.com/

---

• https://github.com/radix-vue/radix-vue -- https://radix-vue.com/
• https://github.com/oku-ui/primitives -- https://oku-ui.com/primitives
• https://github.com/agnosticui/agnosticui -- https://www.agnosticui.com/

---

• https://github.com/jd-solanki/anu -- https://anu-vue.netlify.app/
• https://github.com/uiv-lib/uiv -- https://uiv.wxsm.space/
• https://github.com/onu-ui/onu-ui -- https://onu.zyob.top/

---

[ddahan]

Hi there. Thanks for all the suggestions.
I don't know all libraries but I'll take a look for sure.

However, I'd like to point out that the purpose of this tool is not to be absolutely comprehensive by listing all UI libraries, but rather propose a curated list to users to help them make a choice. I'm afraid that if in the end there are too many libraries, it gets complicated for users to make this choice.

Among all the libraries you listed, do you think one should be absolutely present because it has something particular that others don't? Thanks.

[brc-dd]

I guess we can have some kind of threshold like number of stars or downloads to avoid adding too much libraries.

Among all the libraries you listed, do you think one should be absolutely present because it has something particular that others don't?

Yeah I can explain briefly about each. Feel free to choose from them.

• zag (primitives), ark (unstyled components built on top of zag), chakra UI (next) (components built on top of zag) -- these are built by the chakra team and are more accessible than any of the libraries that I know for vue. (like react-aria kind of a11y). Although chakra-ui for vue3 is still in beta.
• radix-vue and oku seem to have similar goals of porting radix to vue. These are unstyled components. radix-vue is used by shadcn-vue (already on the list).
• agnostic ui also have primitives and unstyled components. Although the focus is more on cross framework support rather than a11y or design.
• anu and onu are built on top of unocss. uiv is on top of bootstrap. These are styled components.

[ddahan]

Thanks for the summary!
I updated the README to be more specific about which library to include or discard.
Would you mind reading this section and make a first filter based on what it is said?
Thanks.

[brc-dd]

IG we can keep these:

• Ark UI
• Anu
• uiv

The others don't seem to meet the criteria

• Zag - low-level primitives not components
• Chakra - WIP
• Radix Vue - WIP? (actually this has all the components of Radix, but here since you mentioned this explicitly in readme)
• Oku - WIP
• Agnostic UI - no new commit in last six months
• Onu UI - WIP

[ddahan]

Thanks for the first filter! I'll take a look to these 3 libraries.

[kissu]

I feel like some of those are quite relevant to the topic: https://twitter.com/youyuxi/status/1695740094127456292

And Radix-Vue looks as ready as HeadlessUI in terms of quantity/quality of components tbh. 🤔

[ddahan]

@kissu You're right. It seems that Radix-Vue is evolving particularly quickly, as there are much more components that last time I checked. I'm considering adding it.

[ddahan]

Radix-Vue added! Libs to check:

• Ark UI
• Anu
• uiv
• oku-ui
• Storefront-ui
• Inkline
• Vexip-ui

[ZainW]

would highly recommend adding oku primitives and ark-ui to the list

while there are a lot of headless libraries popping up right now these in particular are extremely important to the ecosystem, these are the kind of libraries that bridge the gap between Vue ecosystem and React ecosystem.

[bobbyrahmanda13]

What do you think about the Vexip-ui which is already in the nuxt.com module, please review this

[ddahan]

Thanks @bobbyrahmanda13 I have added vexip-ui to the review list, in addition to inkline suggested by @alexgrozav

But as you can all see, the problem becomes more visible as more libraries are waiting for review: adding these 7 libraries to the list won't help users at all, as the choice will become harder for them. This app must not be a full directory of all libraries, but a curated list of advised one. That's how I designed it, and I don't want this to change.

I genuinely understand everyone wants to see its favorite library (or the one he has worked on) listed, but it will be counterproductive for end users.

I'm thinking of an arbitrary rule of:

• existing usage/popularity (XX stars and/or XX downloads) threshold
• except if the library has something very particular that worth mentioning it despite low popularity / newness (for example, Nuxt UI is not very popular yet but is the only library dedicated to Nuxt, which brings a great DX for Nuxt users, and is made by the Nuxt team itself).

If you have another idea that take care of users first, I'm open to discussion. Thanks.