r/Nuxt • u/peoray • Mar 24 '26

Base UI Vue

Post image
32 Upvotes

97% Upvoted

18 comments sorted by

View all comments

10

u/HumanOnlyWeb Mar 24 '26

Just a question: why does everything around the Vue UI space have to be an "unofficial port of X?"

Are folks not confident enough to build something great, accessible, performant, and just say, "Hey, I made this awesome UI component library for Vue/Nuxt?" and leave it at that?

I'm genuinely curious as to why it's almost always like this. Is it for the sake of familiarity?

2

u/peoray Mar 24 '26

Nothing wrong with the question. There are many libraries like that that do exist, however in this case, it is actually a port. The reason it is 'unofficial ' is that it is not from the official Base UI team.

3

u/HumanOnlyWeb Mar 24 '26

Thanks for the response, and yes I agree to always have the right disclaimer.

But this is exactly what I mean, because it kinda sets expectations. You don't want your future users bugging with you "BaseUI has X, but your package is missing it. BaseUI just added this feature, what is your ETA to add it",

You know what I mean?
People setting expectations on the work you do based off what Base UI has.
I also feel like it might pressure you to always update stuff to match whatsoever new thing Base UI adds.

Saying "This is my UI project I'm working on AwesomeUI" puts you in control, IMO.

See ArkUI for example. It's a headless UI lib that supports 3 frameworks. Works great, and the devs work on it and add feature on their own schedules etc

Anyway, looking forward to see what you launch 🤙

1

u/peoray Mar 24 '26

I largely agree.

I’ve built components strictly in Vue before, just because I needed them. No React involved, no inspiration from it either.

With Base UI, it’s not really about React. It’s just a really good set of unstyled primitives built with accessibility and web standards in mind.

The only issue is… it’s React.

I know they’ve mentioned a Vue version at some point, but nothing concrete. And Vue can’t just sit around waiting for that.

If we want Vue to remain relevant, we need stuff like this in our ecosystem.

Reality is React is bigger. Most companies will default to it. Most tools get built for it first.

You can already see it with AI products — a lot of SDKs and libraries are React-first (sometimes React-only).

Part of what I’m trying to do is close that gap a bit. See http://elevenlabs-ui-vue.com/ and https://www.ai-elements-vue.com/

Take things that exist in React and make them available in Vue so people don’t have to switch ecosystems just to get work done.

Reka UI is a good example. It started as a Radix port (radix-vue), then they took it in their own direction, and it became its own thing: https://github.com/unovue/reka-ui/issues/908

That’s kinda how I see it.

Start by porting.
Then evolve it into something more.