Skip to content

v5 #5473

Closed
Closed

Description

@benjamincanac

There is no v5 release planned at the moment, I'm just opening this issue to write and remember some breaking changes that we should consider in the future:

  • Simplify NavigationMenu to only support horizontal orientation
  • Create another NavigationMenu for vertical orientation and merge with ContentNavigation (maybe NavigationAccordion?)
  • DropdownMenu & ContextMenu item label type should have the same size as other components (we might need to introduce a new type)
  • Split components that contains multiple UI components like Header and DashboardSidebar mobile menus, it's hard to proxy every prop and events this way
  • Rework Dashboard components to use a single root div when resizable + rework provider context
  • Uniformize props that extends ButtonsProps like links, actions, etc. into buttons
  • Uniformize duplicated components like Card and PageCard
  • Bump --ui-container to 90rem as it seems to be the defaults nowadays
  • Rename input and searchInput props respectively from CommandPalette and SelectMenu to filter for consistency with feat(DropdownMenu): add filter prop #6153
  • Explore the idea of having elements (buttons, input, etc.) always square (same padding on x and y) as it creates issues for example in collapsed sidebar for NavigationMenu or for DropdownMenu alignment when the button is only an icon vs it has a label
  • Unify header structure across Modal, Slideover, and Drawer to match the Sidebar pattern with wrapper (title + description) + actions slot (custom buttons + close) feat(Sidebar): new component #6038
  • Rework NavigationMenu collapsed behavior: use CSS transitions (opacity/width) instead of display: none so labels animate smoothly with sidebar width transitions, decouple visual collapse (CSS-driven) from behavioral collapse (tooltip/popover activation), and eliminate the need for manual :collapsed wiring
  • Rework close buttons so they are no longer absolute positioned (Empty div on Slideover when title or description props are not used #5336 (comment))
  • Move @tiptap/* and embla-* to peerDependencies https://github.com/nuxt/ui/blob/v4/package.json#L144-L160 https://github.com/nuxt/ui/blob/v4/package.json#L168-L174
  • Maybe get rid of Fuse.js which is only used in CommandPalette? 🤔 We could use useFilter like SelectMenu, InputMenu, etc.
  • Consistent use of start / end instead of left / right or leading / trailing v5 #5473 (comment)
  • Migrate ColorPicker to use https://reka-ui.com/docs/components/color-area / https://reka-ui.com/docs/components/color-slider
  • Configure default Toast expand to false so it's stacked by default

Please don't comment for feature requests or new components, those aren't related to a major version and can be integrated into v4. Such comments will be hidden to prevent flood like it did in #1289.

Activity

  1. added
    questionFurther information is requested
    and removed
    questionFurther information is requested
    on Nov 17, 2025
  2. added and removed
    triageAwaiting initial review and prioritization
    v4#4488
    on Nov 17, 2025
  3. yeonjulee1005 commented on Nov 17, 2025

    @yeonjulee1005
  4. niusia-ua commented on Nov 18, 2025

    @niusia-ua
  5. maximepvrt commented on Nov 26, 2025

    @maximepvrt
    Contributor

    It would be great to harmonize the links and actions props across components like PageCTA and Empty, as they serve similar purposes and a unified naming would improve consistency.

  6. septatrix commented on Nov 30, 2025

    @septatrix

    I am not sure how much work this needs but supporting UnoCSS (with the tailwind preset) would be fantastic. Our team is used to it (or rather some of its other presets) instead of tailwind and new projects are currently split between Nuxt UI and another component library for that reason

  7. Blechlawine commented on Dec 1, 2025

    @Blechlawine

    It would be great if the ChatMessages component could be changed to support messaging between different people or group chats as well as ai. Currently it has the role: "assistant" property on messages, which makes it seem like it should only be used with an ai, not for messaging between different users.

    As for 4. (splitting components) I hope you won't go the way of shadcn/ui where you need to include 5 components just to show a nav menu with some links. I like the approach of using props and objects for that more. It's also more typesafe, since afaik there's no way of restricting the type of a child element/component.

  8. lehuuphuc commented on Dec 4, 2025

    @lehuuphuc
    Contributor

    @septatrix you can try my preset that enables Nuxt UI to work with Unocss https://github.com/lehuuphuc/unocss-preset-nuxt-ui

  9. benjamincanac commented on Dec 4, 2025

    @benjamincanac
    MemberAuthor

    @Blechlawine We won't go the shadcn way of course not, what I meant by splitting components is in some specific cases it would be easier to override if moved to its own component like for example the Header mobile menu (https://github.com/nuxt/ui/blob/v4/src/runtime/components/Header.vue#L178).

  10. 12 remaining items

  11. al1maher commented on Apr 6, 2026

    @al1maher
    Contributor

    Hi @benjamincanac I think instead of using right and left in components, we should use start and end to improve RTL support.

    Some components: https://ui.nuxt.com/docs/components/table#with-column-pinning https://ui.nuxt.com/docs/components/page https://ui.nuxt.com/docs/components/chat-message#side https://ui.nuxt.com/docs/components/footer#usage

    I'd go a bit further and I'd love a better right locale layout (e.g. Arabic, Farsi, etc..) support in general.

  12. maxdzin commented on Apr 15, 2026

    @maxdzin

    Greetings lovely people!

    How about adding v-tooltip directive to components for easier tooltips handling (for usual cases)? So that we can choose either to wrap something by UTooltip, or to specify by directive.

  13. abhishek-junghare commented on Apr 15, 2026

    @abhishek-junghare

    Uniform Attribute Names

    The UButton component accepts an icon via the icon attribute:

    <UButton icon="i-lucide-rocket" />
    

    The UIcon component, however, uses the name attribute for the same purpose:

    <UIcon name="i-lucide-rocket" />
    

    These attributes could be standardized across components. In this case, the UIcon component could also use the icon attribute, consistent with other components:

    <UIcon icon="i-lucide-rocket" />
    
  14. maxdzin commented on Apr 19, 2026

    @maxdzin

    UIcon component color property.
    For some cases (like icons in menus, etc.), it would be super convenient to set via props.
    Additionally, it needs to add the possibility to use full icon props instead of name only:
    icon?: IconProps['name'] | IconProps

  15. abhishek-junghare commented on May 19, 2026

    @abhishek-junghare

    Improvised UContainer

    Imagine you want to add a full-width bottom border or a full-width background color to a UContainer. We cannot simply add the border or background classes directly to the UContainer, because those styles would also be constrained within the set max width. Currently, we have to wrap the container inside an external div to get this. However, this could be implemented in the UContainer component itself, given how common this specific design pattern is.

    Instead of UContainer having a single wrapper, it could feature a nested, double-wrapper structure like this -

    <div :class="wrapperClass">
        <div :class="baseClass">
            <slot />
        </div>
    </div>
    
    <UContainer
        :ui="{
            wrapper: 'border-b border-default',
            base: 'max-w-[80rem] mx-auto w-full',
        }">
    </UContainer>
    
  16. abhishek-junghare commented on May 27, 2026

    @abhishek-junghare

    There should be different css variables set depending on the elevation of the surface.

    Look at the cards below.

    • Badge and Button is set to variant="soft", which uses bg-muted for their backgrounds.
    • Heading is set to text-highlighted
    • Paragraph is set to text-muted
    • The Badge in each card, tells which background is applied to the respective card.

    You can see that the

    • First card has the best contrast.
    • Second card has usable contrast.
    • Third card has no contrast. The badge and the button, has the same background as the card background.

    There are many scenarios where we want these kinds of elevated backgrounds, especially in dashboards.

    Image

    So, instead of assigning fixed css variables, the implementation could look something like this:

    .dark {
        --ui-bg: var(--ui-color-neutral-900);
        --ui-bg-muted: var(--ui-color-neutral-800);
        --ui-bg-elevated: var(--ui-color-neutral-800);
        --ui-bg-accented: var(--ui-color-neutral-700);
        --ui-bg-inverted: white;
    }
    
    .elevation-1 .dark {
        --ui-bg: var(--ui-color-neutral-800);
        --ui-bg-muted: var(--ui-color-neutral-700);
        --ui-bg-elevated: var(--ui-color-neutral-700);
        --ui-bg-accented: var(--ui-color-neutral-600);
        --ui-bg-inverted: white;
    }
    
    .elevation-2 .dark {
        --ui-bg: var(--ui-color-neutral-700);
        --ui-bg-muted: var(--ui-color-neutral-600);
        --ui-bg-elevated: var(--ui-color-neutral-600);
        --ui-bg-accented: var(--ui-color-neutral-500);
        --ui-bg-inverted: white;
    }
    
    /* There could be a negative elevation as well? */
    .depth-1 .dark {
        --ui-bg: var(--ui-color-neutral-1000);
        --ui-bg-muted: var(--ui-color-neutral-900);
        --ui-bg-elevated: var(--ui-color-neutral-900);
        --ui-bg-accented: var(--ui-color-neutral-800);
        --ui-bg-inverted: white;
    }
  17. benjamincanac commented on Jun 9, 2026

    @benjamincanac
    MemberAuthor

    Would love any feedback from you guys on #6576, this focus rewrite was supposed to go in v5 but it's achievable without too much class change. I wonder if this can be seen as a breaking change or just an improvement and is acceptable to be shipped inside a minor. I've attached screenshots, also let me know if you like it 😊 Thanks!

  18. al1maher commented on Jun 9, 2026

    @al1maher
    Contributor

    Would love any feedback from you guys on #6576, this focus rewrite was supposed to go in v5 but it's achievable without too much class change. I wonder if this can be seen as a breaking change or just an improvement and is acceptable to be shipped inside a minor. I've attached screenshots. Thanks!

    I think it's okay to ship it inside a minor as I see no real need to be in a major release, maybe some snaps failing but that's acceptable at least for me

  19. maximepvrt commented on Jun 17, 2026

    @maximepvrt
    Contributor

    #5473 (comment)
    #6598

    I think it would be a great addition to generalize the Chat components to make them fully agnostic. Currently, I've managed to build chat UIs by using the UChatMessage components and manually positioning them to the right or left depending on the sender. I already improved the situation a bit with these two PRs: #6407 and #6460.

    However, for v5, we should take it a step further and consider the following improvements:

    • Remove strict/hardcoded types directly tied to the Vercel AI SDK within the core component.
    • Create a utility helper that allows users to easily map/transform Vercel AI SDK objects into Nuxt UI message objects.

    This approach keeps the core component ultra-flexible and clean, while still providing an easy bridge for developers working with popular AI SDKs. What do you think?

  20. maxdzin commented on Jun 17, 2026

    @maxdzin

    @maximepvrt Recently I experimented with Chat components in some project and thinking about somewhat similar. It would be great if Nuxt UI will provide the generic Chat as basic set: input + message + messages components, + easy way to enhance it by adding some custom things for messages (attachment previews, charts, whatever else can be imagined, ...) - something like current AI Chat can support via custom tools. And that generic Chat components should be easily turned into AI chat by adding current Chat components - reasoning, shimmer, tool, prompt, submit.

  21. maxdzin commented on Jun 17, 2026

    @maxdzin

    Nuxt UI is a great lib, and I’ve been using it a lot lately.
    What I’m missing is better TS support for types like NavigationMenuItem, DropdownMenuItem, SelectMenuItem, etc. All of such types could use generic to provide better DX.

    For example, instead of

    export interface NavigationMenuItem extends Omit<LinkProps, 'type' | 'raw' | 'custom'> {
      // ...
      [key: string]: any;
    }

    it could be like this, so TS knows the shape of custom fields:

    export type NavigationMenuItem<
      TMeta extends Record<string, unknown> = {}
    > =
      Omit<LinkProps, "type" | "raw" | "custom"> &
      TMeta & {
        label?: string;
        icon?: IconProps["name"];
        // ...
        [key: string]: unknown;
      }

    Or maybe even cleanest way - to avoid index signature and collision with interface props, like this:

    export interface NavigationMenuItem<TMeta = unknown> {
      label?: string;
      icon?: IconProps["name"];
      // ...
      meta?: TMeta;
    }

    Also it might be good idea to get rid of any, if possible, and use unknown instead.

  22. Blechlawine commented on Jun 19, 2026

    @Blechlawine

    For the css variables it would also be great if the names were more clear if they're lighter/darker than the background. With the current names muted, dimmed, elevated its not totally clear if muted or dimmed is lighter (in dark mode). elevated makes sense to me, but the other 2 are kinda confusing. I don't know what names would be better though. Maybe something like muted and muted-stronger?

  23. locked and limited conversation to collaborators on Jun 19, 2026
  24. converted this issue into a discussion #6610 on Jun 19, 2026
  25. unpinned this issue on Jun 19, 2026
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions