OpenVi Foundation
Docs

Projects / OpenVue / Roadmap

OpenVue roadmap

Stability first, growth second. What has shipped, what is being worked on now, and where 2.0 is headed.

5 done, 1 in progress, 4 planned. The order is decided in the OpenVue README, and this page follows it.

Getting to 1.0

Stability first: the fork published, documented, migratable and frozen at a stable API.

  • Publish to npm

    Done

    Every OpenVue package is live under the @openvue scope.

  • Launch openvue.dev

    Done

    The full documentation with interactive component demos, at openvue.dev.

  • Ship a PrimeVue migration tool

    Done

    npx @openvue/migrate moves a PrimeVue v4 project to OpenVue in one command. See the migration guide.

  • Release 1.0.0

    Done

    The public API is stable and follows semantic versioning from here. Release notes.

    Shipped

OpenVue 1.x

Fixes before features, then the pieces of the ecosystem that were still missing.

  • Work through the backlog

    In progress

    Open issues, accessibility and performance come before new surface area. What has landed since 1.0.0 is under Unreleased in the changelog.

  • Bring Volt back

    Done

    OpenVolt is live: npx openvolt-vue copies Tailwind-native components into your own codebase.

    Shipped

  • Ship a new theme

    Planned

    A preset of our own, so OpenVue has its own visual identity alongside Aura, Lara, Material and Nora.

  • More free templates

    Planned

    Further application templates and layouts, building on Deni.

OpenVue 2.0

Modernised internals, without leaving existing applications behind.

  • Vapor mode

    Planned

    Full compatibility with Vue Vapor. Traditional virtual DOM rendering stays supported.

  • Composition API and TypeScript at the source

    Planned

    The components rewritten around the Composition API with TypeScript as the source language. The Options API keeps working for the applications that use it.

Something missing that you need? Open an issue or start a thread in GitHub discussions. Requests with a concrete use case behind them are the ones that move up the list.