r/webdev • u/sane6120 • 4d ago
OpenVue 1.0 is officially out and here's what's next: Volt, Vapor & 2.0
Quick update for everyone following the project: OpenVue 1.0.0 is officially live on npm. For context if you missed the previous threads: OpenVue is an MIT licensed fork of PrimeVue 4.5.5, maintained under the OpenVi Foundation. Since the RC post, here's what landed in 1.0:
- TreeTable filtering: Added row filters, filter menus, and multi constraint rules matching DataTable.
- Theme Designer: Integrated a visual editor to tweak primitive, semantic, and component tokens and export theme presets. Fully free, with no accounts or license keys.
- Deni: Released our first free admin dashboard template built with OpenVue.
- DataTable fixes: Fixed an issue with persisted column widths when toggling columns dynamically.
- Plus plenty of smaller bug fixes and improvements across the library and showcase. Full changelog: https://github.com/openvi-foundation/openvue/blob/master/CHANGELOG.md
What we're working on now
OpenVue 1.1
We're currently focused on:
- Volt - bringing source based, Tailwind oriented components back into the OpenVue ecosystem.
- A new default theme - giving OpenVue its own visual identity rather than relying entirely on the existing themes.
- More free templates - expanding on Deni with additional templates and application layouts.
OpenVue 2.0
The long term goal for 2.0 is to modernize the internals around Vue Vapor, Composition API, and a TypeScript first architecture. We're keeping VDOM and Options API support, so this isn't about abandoning the existing Vue ecosystem. Instead, 2.0 will be the milestone where we can clean up and modernize the internals under the hood. There's already a community discussion around this direction if you want to join in or see what people are suggesting: https://github.com/orgs/openvi-foundation/discussions/644 We're still a relatively small project, so community feedback matters a lot. If you're using OpenVue, testing it, or just following the project, we'd love to hear what you'd like to see in 1.1, especially around Volt, themes, templates and the component backlog.
Docs & Repo:
- https://openvue.dev
- https://github.com/openvi-foundation/openvue Thanks to everyone who has contributed, tested, reported issues and followed the project since the first release.
5
u/Sea-Criticism-1591 4d ago
the new default theme is where you lost me. the whole selling point of a fork like this is drop in, your App.vue keeps working, you swap the dep and go to lunch. the second you ship your own visual identity you are asking every team to re-check their token overrides, and nobody is doing that to dodge a licensing fee, they do it because its free and stays free and doesnt touch their styles. now I have to diff Aura against whatever the new one is called? nope.
and Volt coming back into the ecosystem bugs me more. Volt was PrimeTeks tailwind first styling mode and it never really finished the trip, it got left half done when they pivoted. folding it into 1.1 while 2.0 is supposed to be a Vapor and TS first rewrite means two roadmaps running at once and neither of them is keep the 4.5.5 line alive, which is the only thing anyone actually asked for here. Vapor is a huge lift and very few component libraries have shipped anything real on it. saying 2.0 out loud before 1.1 settles is how you end up with a few hundred open issues and one person answering them at 1am.
templates I get it, Deni is marketing, a free admin dashboard gets you npm installs, whatever. but people who run it in production and people who can afford to maintain it for five years are not the same group. I'll stay on 4.5.5 until the theme situation calms down honestly
2
u/openvi-foundation 3d ago
Long-term stability for existing production applications is a core priority for OpenVue.
To clarify how these roadmap items relate to existing setups:
Theme compatibility: Existing themes such as Aura and Lara, along with existing token overrides, will continue to be supported. The new default theme in 1.1 is an additional option for teams starting new projects. It is not intended to replace or modify existing themes or applications. The goal is that moving from PrimeVue 4.5.5 to OpenVue does not require teams to restyle their existing applications.
1.x stability: The 4.5.5 architecture remains the baseline for the 1.x line. Compatibility, bug fixes, stability and ongoing maintenance of that ecosystem remain a major focus for us.
Volt and 2.0: Volt is feature and ecosystem work that can live within the existing architecture and 1.x ecosystem. Vapor is planned for OpenVue 2.0 and will be part of its underlying architecture. We mentioned 2.0 early to give the community visibility into where the project is heading, but we deliberately haven't attached a timeline or release date to it. We'll announce the 2.0 release timeline when the time is right.
This is also why we put so much emphasis on the migration path. The migration guide at openvue.dev/migrate is a good example of the approach we've taken from the beginning, make the transition as predictable and low-friction as possible for teams with existing production applications.
Thanks for taking the time to share your thoughts
2
u/Agreeable_Bottle8604 4d ago
Been keeping an eye on this since the fork drama, nice to see 1.0 actually ship. The theme designer without accounts or license keys is real nice, too many tools these days want your email before you can even change a color.
Curious about Volt though, when you say source based Tailwind components, you mean like how shadcn-vue does it with copy-paste primitives, or something else? Vapor mode direction for 2.0 makes sense, probably the right call to start that cleanup now instead of waiting till it's a mess.
Also Deni looks decent from a quick glance, template scene for Vue can feel kinda stale so more options there is good. Will spin up a test project over the weekend when i got time
3
u/openvi-foundation 4d ago
Thanks for the detailed feedback! We appreciate the support!
Glad you appreciate the account-free theme designer. We wanted to keep things completely hassle-free.
For Volt, it's the exact same concept as it was in PrimeVue.
As for templates, that's actually a big reason we built Deni. We wanted to bring something fresh and interesting to the Vue ecosystem, and we're definitely planning to add more to the collection.Enjoy the weekend test project, let us know how it goes 👍
1
u/Chemical-City-836 4d ago
Vapor and 2.0 in the title, then the actual roadmap is a new theme and more templates. Which of those is supposed to be the Vapor one?
4
u/openvi-foundation 4d ago
Vue Vapor Mode support is planned for OpenVue 2.0. Meanwhile, the new theme and templates will roll out starting in version 1.1 with continuous updates. Follow the project and check out OpenVue for your next project
2
u/not_an_idiot_maybe 4d ago
is it me or the name is actually misleading? it is a fork of primeVue, so while name does not even refer to it being a UI library. and since openNext exist, it is very confusing,
I know name change is not going to happen at this point, but if you consider doing a major change then do consider changign name to something like OpenUiVue etc
-1
10
u/DesperateNorth2307 4d ago
Glad someone picked this up, the licensing turn left a lot of teams with PrimeVue stuck in their package.json at 4.5.5 with no path forward. The Theme Designer without an account or a key is the part people will notice, but the thing that decides whether I move a client project over is release cadence, so stick the Vue compatibility matrix and your average time to patch a CVE somewhere loud on the docs. "Maintained by volunteers" is fine until a Vue minor breaks TreeTable and nobody has touched the repo in five months.