v5

Nuxt UI v5 is a theming-led major. The full plan and the discussion live in #6610, this issue tracks what has landed.

We're working on the v5 branch, prereleases are published under the next npm tag and the docs for the alpha will be available at https://ui5.nuxt.com. Breaking changes are listed in the migration guide as they land.

Tasks

• Epic A: Design Tokens v2
• Epic B: Prop & class renames
• Epic C: Component restructures
  • Migrate Drawer to Reka UI's Drawer primitive and drop vaul-vue: https://github.com/nuxt/ui/pull/6691
  • Declare every theme class under a slot, single-element components included: https://github.com/nuxt/ui/pull/6998
  • Rename the base slot to root on layout containers: https://github.com/nuxt/ui/pull/7000
  • Namespace data-slot with the component name: https://github.com/nuxt/ui/pull/7003
• Epic D: Defaults & behavior
• Epic E: Foundation & install contract
  • Optional peer dependencies for Editor, Carousel and Table: https://github.com/nuxt/ui/pull/6951
• Epic F: Migration & rollout (migration guide, codemod)
• Epic G: Launch (landing, theme playground)
• Epic H: Own the styling engine
  • Replace tailwind-variants with an in-tree variants engine: https://github.com/nuxt/ui/pull/6964
  • Call tv with the theme and its overrides, keyed by content: https://github.com/nuxt/ui/pull/6975
  • Let app.config.ui slot classes win over theme variants: https://github.com/nuxt/ui/pull/6976
  • Resolve app.config.ui variants after the theme variants, activeClass after the theme: https://github.com/nuxt/ui/pull/6978
  • Rename the ui.tv merge keys and drop deprecated gradient utilities: https://github.com/nuxt/ui/pull/7007
  • Swap tailwind-merge for cn (on hold): https://github.com/nuxt/ui/pull/7011

Release

• Release v5.0.0-alpha.0
• Deploy ui5.nuxt.com from the v5 branch
• Release v5.0.0
• Update templates to v5
• Transfer ui.nuxt.com from v4 to v5, move v4 docs to ui4.nuxt.com
• Publish release notes, blog post and tweet

Feedback

Feedback on the plan goes in #6610, keep this issue for progress. New feature requests and component requests aren't tied to v5 and can be opened as regular issues.