OpenVue

The Vue UI component library, continued.

Documentation · Setup · Components · Migrate from PrimeVue · Changelog

About

OpenVue is a community-maintained fork of PrimeVue 4.5.5, one of the most widely adopted Vue.js component libraries, started after its original maintainers ended active open source development and moved new releases to a commercial license. The project is stewarded by openvi-foundation, an independent organization of experienced developers who use this library in production and are committed to keeping it maintained, stable, and open.

OpenVue is not affiliated with PrimeTek or PrimeUI. We started this project because a library with this much adoption, and this many teams depending on it, deserves a maintenance path that isn't tied to any single company's plans.

Migrating from PrimeVue

The migration tool is ready, try it out! One command moves an existing PrimeVue v4 project to OpenVue:

npx @openvue/migrate

It shows you a plan first (detected package manager, PrimeVue version, and every file it will change) and asks before writing anything. It renames dependencies, rewrites imports, and audits what's left, leaving a single reviewable diff. Use --dry for a preview that writes nothing.

Read the full guide at openvue.dev/migrate or the @openvue/migrate README.

Installation

npm install openvue @openvue/themes

Register a theme preset when installing the plugin:

import { createApp } from 'vue';
import OpenVue from 'openvue/config';
import Aura from '@openvue/themes/aura';
import App from './App.vue';

const app = createApp(App);

app.use(OpenVue, {
    theme: {
        preset: Aura
    }
});

app.mount('#app');

Additional packages (@openvue/forms, @openvue/nuxt-module, @openvue/mcp, ...) are opt-in. Install them only if you need form validation, Nuxt integration, or the MCP server.

Ecosystem

The fork spans the full toolchain, each piece maintained under the openvi-foundation organization.

Roadmap

Our priority is stability first, growth second. In order:

1. Publish to npm. Done: OpenVue packages are live under the @openvue org on the latest tag.
2. Launch the OpenVue website. Done: openvue.dev is live with the full documentation and interactive component demos.
3. Ship a PrimeVue migration tool. Done: npx @openvue/migrate moves a PrimeVue v4 project to OpenVue in one command.
4. Stabilize and release. Done: 1.0.0 is out. The public API is stable and follows semantic versioning from here.
5. Work through the backlog. Open issues, accessibility and performance come before new surface area.
6. Bring Volt back. The Tailwind-native components you copy into your own codebase, rebuilt under the OpenVue name.
7. Ship a new theme. A preset of our own, alongside the four inherited from upstream.
8. Release 2.0. Composition API, Vapor mode and TypeScript at the source. Existing applications keep working: OpenVue is getting full Vapor compatibility, but traditional virtual DOM rendering and Options API support are not going anywhere.

Contributing

We're building the initial maintainer team now. If you're an experienced developer interested in helping maintain or grow this library, issues and pull requests are open, and we'd welcome the help.

Start with the contributing guide for the development setup and how changes get reviewed. Participation is covered by our code of conduct. To report a security issue, follow the security policy rather than opening an issue.

Contributors ✨

Everyone who has helped build OpenVue since the fork: code, docs, design, bug reports, and ideas.

License

MIT, unchanged. Every release under the MIT license stays exactly as it is. This fork doesn't affect that in any way.