Repository navigation
Closed
Labels
Description
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
labeltype 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
ButtonsPropslikelinks,actions, etc. intobuttons - Uniformize duplicated components like
CardandPageCard - Bump
--ui-containerto90remas it seems to be the defaults nowadays - Rename
inputandsearchInputprops respectively from CommandPalette and SelectMenu tofilterfor consistency with feat(DropdownMenu): addfilterprop #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) +actionsslot (custom buttons + close) feat(Sidebar): new component #6038 - Rework NavigationMenu
collapsedbehavior: use CSS transitions (opacity/width) instead ofdisplay: noneso labels animate smoothly with sidebar width transitions, decouple visual collapse (CSS-driven) from behavioral collapse (tooltip/popover activation), and eliminate the need for manual:collapsedwiring - 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/*andembla-*topeerDependencieshttps://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
useFilterlike SelectMenu, InputMenu, etc. - Consistent use of
start/endinstead ofleft/rightorleading/trailingv5 #5473 (comment) - Migrate
ColorPickerto use https://reka-ui.com/docs/components/color-area / https://reka-ui.com/docs/components/color-slider - Configure default Toast
expandtofalseso 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.
Reacted by Estéban, Hugo, Jascha Pearson, Dmitriy Brolnickij, Raku, Tuguldur, Dewdew, Hau Nguyen, Sadegh Barati, Adarsh Madrecha and 32 more
Reacted by Huseyn Guliyev, DOMArtist, Eita Kobayashi, Thiago Ferreira, endersz1, Max, mbrankovicwork and Riccardo Bergamaschi
Activity
yeonjulee1005 commentedon Nov 17, 2025
niusia-ua commentedon Nov 18, 2025
maximepvrt commentedon Nov 26, 2025
It would be great to harmonize the
linksandactionsprops across components likePageCTAandEmpty, as they serve similar purposes and a unified naming would improve consistency.septatrix commentedon Nov 30, 2025
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 commentedon Dec 1, 2025
It would be great if the
ChatMessagescomponent could be changed to support messaging between different people or group chats as well as ai. Currently it has therole: "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 commentedon Dec 4, 2025
@septatrix you can try my preset that enables Nuxt UI to work with Unocss https://github.com/lehuuphuc/unocss-preset-nuxt-ui
benjamincanac commentedon Dec 4, 2025
@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).
12 remaining items
al1maher commentedon Apr 6, 2026
I'd go a bit further and I'd love a better right locale layout (e.g. Arabic, Farsi, etc..) support in general.
maxdzin commentedon Apr 15, 2026
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.
abhishek-junghare commentedon Apr 15, 2026
Uniform Attribute Names
The
UButtoncomponent accepts an icon via theiconattribute:The
UIconcomponent, however, uses thenameattribute for the same purpose:These attributes could be standardized across components. In this case, the
UIconcomponent could also use theiconattribute, consistent with other components:maxdzin commentedon Apr 19, 2026
UIconcomponentcolorproperty.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'] | IconPropsabhishek-junghare commentedon May 19, 2026
Improvised
UContainerImagine 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 -
abhishek-junghare commentedon May 27, 2026
There should be different css variables set depending on the elevation of the surface.
Look at the cards below.
variant="soft", which usesbg-mutedfor their backgrounds.text-highlightedtext-mutedYou can see that the
There are many scenarios where we want these kinds of elevated backgrounds, especially in dashboards.
So, instead of assigning fixed css variables, the implementation could look something like this:
benjamincanac commentedon Jun 9, 2026
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!
al1maher commentedon Jun 9, 2026
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
maximepvrt commentedon Jun 17, 2026
#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
UChatMessagecomponents 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:
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?
maxdzin commentedon Jun 17, 2026
@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.
maxdzin commentedon Jun 17, 2026
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
it could be like this, so TS knows the shape of custom fields:
Or maybe even cleanest way - to avoid index signature and collision with interface props, like this:
Also it might be good idea to get rid of
any, if possible, and useunknowninstead.Blechlawine commentedon Jun 19, 2026
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,elevatedits not totally clear if muted or dimmed is lighter (in dark mode).elevatedmakes sense to me, but the other 2 are kinda confusing. I don't know what names would be better though. Maybe something likemutedandmuted-stronger?