Let's keep Vue open, together.

Hey Vue community,

We are long-time PrimeVue users who believe that a great UI component library should remain free, open, and community-driven forever. When PrimeVue v5 launched with a license change that moved the library away from open source, we knew we had to do something.

Openvi Foundation is an independent, community-driven organization dedicated to maintaining and evolving open source UI tooling for the Vue ecosystem. We are not affiliated with the PrimeVue team or Primetek.

OpenVue is a fork of PrimeVue v4, the last fully open source version. Our goal is simple: keep it MIT licensed, keep it maintained, and keep it free for every Vue developer, forever.

We are in the early stages, but we are committed to this for the long run. If you want to help, star the repo, join the discussion, or just spread the word.

This is day one. Let's keep Vue open together.
— Openvi Foundation

Why we chose to continue this library

We have used PrimeVue daily for few years across many big and small projects. We think it was one of the best UI libraries in the Vue ecosystem, and we did not want to see it disappear behind a closed license. Continuing it felt like the natural thing to do, not a business opportunity.

Our roadmap

We are organizing the project first, before we touch individual issues. Here is the order we are working in.

1. Stabilize OpenVue as a maintained fork. Fix critical issues, apply patches, and keep dependencies up to date.
2. Build a documentation website aimed at people who already know PrimeVue, so almost nothing feels unfamiliar.
3. Ship a migration tool so a PrimeVue project can move to OpenVue with as little manual work as possible.
4. Once the foundation is stable, start adding new features together with the community.

Why we have not started triaging issues yet

We know it can look like we are ignoring the issue tracker. We are not. We have migrated real projects between UI libraries before, and we know how painful it is when documentation and tooling lag behind. So instead of picking off individual bugs right away, we are spending this early period on documentation and a migration tool, because that is what most daily users need first.

Once those foundations are in place, we will move into regular issue triage, patches, and dependency upgrades as an ongoing process, not a one time effort.

Try the alpha

OpenVue is published to npm under an alpha tag while we stabilize the fork.

npm install openvue@alpha

Or with pnpm: pnpm add openvue@alpha