v5

[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
• Rework focus styles like on shadcn/ui feat(theme): rework focus styles #6080
• 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

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.

[yeonjulee1005]

I like this Tour Button Idea!💡
How about It!?🥹
#5431

[niusia-ua]

What about #4251?

[maximepvrt]

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.

[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

[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.

[lehuuphuc]

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

[benjamincanac]

@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).