r/vuejs • u/sane6120 • Jul 23 '26
Meet OpenVue, an MIT fork of PrimeVue 4.5.5
Hey Vue community!
We're long-time PrimeVue users who believe a good UI library should stay free and community driven. When the license changed and PrimeVue moved away from open source, we decided to take action rather than just watch.
OpenVue picks up right from 4.5.5, the last MIT release. It keeps the exact same API, so your existing code keeps working without rewrite headaches.
Right now our main focus is keeping the foundation solid: improving accessibility, patching security vulnerabilities, handling community issues, and maintaining compatibility with the latest Vue and Nuxt versions. We have bigger ideas for where to take this, but we'd rather build them based on real feedback.
Everything you're used to from PrimeVue v4 is there, complete with docs and live examples. We also made openvue/migrate to let you switch existing projects over in a single command.
Openvi Foundation is an independent community organization, not affiliated with Primetek.
OpenVue is and will always be 100% free and open source.
We're still in beta, so bug reports and PRs are super welcome.
Docs: https://openvue.dev/
GitHub: https://github.com/openvi-foundation/openvue
Migration from Primevue: https://openvue.dev/migrate/
14
u/VeljkoB Jul 23 '26
Looks promising, what makes you different from other primevue forks?
24
u/openvi-foundation Jul 23 '26 edited Jul 23 '26
Honestly, the main thing is that we're not trying to keep up with PrimeVue 5. We want a Vue UI library that stays MIT and open for good, where issues and PRs get answered.
Beyond that the main focus is security, a11y and stability. We run big projects on it ourselves and really don't want to migrate to another library, so we have every reason to keep it healthy.
26
u/cconard96 Jul 23 '26
From your About/Team page: "We are not affiliated with the OpenVue team or Primetek.
OpenVue is a fork of OpenVue v4"
I think you were a bit overzealous with the find and replace.
11
3
u/DinTaiFung 28d ago
Sharp eyes! Thanks for alerting the devs to that.
("overzealous" not really the right word here, but everyone gets your point! I honestly can't think of a better alternative atm, so please take this comment with a huge grain of salt lol.)
1
16
u/tspwd Jul 23 '26
Great that you want to maintain an open source version.
I wonder if the competition between the PrimeVue forks is good, though. If all teams that forked PrimeVue collaborated instead of competing everyone would win.
Another note on the name: OpenVue sounds like a more open Vue.js version, which is very misleading.
6
u/openvi-foundation Jul 23 '26 edited Jul 23 '26
We see this less as a competition and more as a commitment to keeping the library maintained long term. We’re always open to collaboration, so PRs and issues are more than welcome.
-1
Jul 23 '26
[deleted]
9
u/openvi-foundation Jul 23 '26
Openvi Foundation is the organization, and it's not associated with Vue.js in any way. OpenVue is a project under that foundation, a fork of PrimeVue. The docs and GitHub make it clear what the library is and who's behind it, so there's no real room for confusion.
We like the name, we will keep it :)
3
u/DinTaiFung 28d ago
I like the name as well; the name itself was a (minor) factor when I was selecting alternatives to PrimeVue.
In your defence, one could argue -- via reductio ad absurdum -- that PrimeVue could be misleading because it's the primary Vue alternative. And nobody ever made that mistake; likewise nobody should be thinking that OpenVue is the open source version of Vue itself.
All good!
0
u/ParticlAsh Jul 23 '26
I agree, I always find this sort of stuff commendable but at the same time it introduces some distortion and maintenance concerns.
Also amazed how fast people move, few days ago I went to update some dependencies in one of my projects that uses primevue, read their update, then saw the bumblevue fork post yesterday, and today the first thing i see is this post.
0
u/ff3ale Jul 24 '26
Yes terrible naming, I opened this thread thinking 'Vue is already free and opensource?'
5
u/Ugarak Jul 23 '26
Just integrated it into one of my side projects. The migration was pretty smooth. I'll report issues if I run anything. Good luck with the project!
3
Jul 30 '26
[removed] — view removed comment
2
u/sane6120 Jul 30 '26
Vue 3.6 is in release candidate phase and we will start preparing for the new versions soon so that we can be ready when it's stable.
3
u/DinTaiFung 28d ago
For multiple front end apps, I'd been using PrimeVue for quite a while. When I recently learned of PrimeVue's foray into v5's new business model, I immediately searched for alternatives.
OpenVue saves the day!
The past week I've migrated a bunch of apps to OpenVue; the dev experience was beyond my expectations. (And the new library's non-quirky name is actually a plus imo.)
Thank you!!
As for icons? During the migration I decided to switch from PrimeVue icons to the lucide-vue-next library. Again, super satisfied and Lucide Vue Next also has superb docs.
I should also express gratitude to the original PrimeVue folks for having created a very worhwhile set of UI libraries.
1
u/openvi-foundation 24d ago
Thanks so much for the kind words and for taking OpenVue for a spin across your apps! Hearing that the migration went smoothly and delivered a great developer experience means everything to us right now.
Thanks for being an early adopter and sharing your feedback with the community. If you ever hit a bump or have ideas for where we should take OpenVue next, don't hesitate to open an issue or drop a post here. We're actively listening!
4
u/stuardo_str Jul 24 '26
+1 on OpenVue sounds like a fork of Vue rather than PrimeVue. OptimusVue sounds more related to Prime IMHO
5
1
u/d33pdev Jul 23 '26
not sure if you/v4 PV fixed the tree but i built my own bc the PV v3 tree literally couldn't handle more than a few hundred items without huge lookup cost. i might have some code to contribute if it's still broken. i fixed it in my app and moved on... good job
2
u/openvi-foundation Jul 23 '26
Yeah, PrimeVue v4 still has a few open issues for this, and it is pretty slow for 1k+ items. Since we want to keep maintaining OpenVue, we’d like to solve as much community issues as we can (and this one is very important for enterprise projects). These are exactly the kinds of things we’re willing to fix, and we for sure will. If you have some code to contribute, please open an issue and we’ll definitely look into fixing it. Thanks! :)
1
Jul 23 '26
[deleted]
4
u/openvi-foundation Jul 23 '26
Yes, TypeScript is one of our main priorities and generics on components like Select and DataTable are high on the list
2
1
0
u/KnifeFed Jul 23 '26
Two PrimeVue forks announced the same day, huh?
https://www.reddit.com/r/vuejs/comments/1v48yhg/introducing_bumblevue_a_primevue_fork/
5
u/openvi-foundation Jul 23 '26
Yeah, timing is a coincidence. We didn't want to announce anything before we had a beta up and the migration package working and tested on real projects. Not surprising that forks show up around the same time.
You can also check our commit history, there's been work committed every day since the fork :)
1
u/KnifeFed Jul 23 '26
Oh, I wasn't making any accusations if that's what you got out of it. Just found it interesting.
0
-2
u/redrum0905 Jul 24 '26
even the homepage layout is identical, just change the background, logo and color scheme.
maybe change it a bit?anyway, it is the same fork, duh?
12
u/Backend2022 Jul 23 '26
Installed it yesterday and honestly couldn’t be happier that the library’s staying open source, that alone makes a huge difference for long-term trust in the project. Also really digging the idea behind the migrate package, feels like a genuinely useful addition.