\n\n\n### Additional context\n\n_No response_",[3019,3022,3025],{"name":3020,"color":3021},"enhancement","a2eeef",{"name":3023,"color":3024},"v3","49DCB8",{"name":3026,"color":3027},"triage","ffffff",4424,"nuxt","ui","open","Ability to not use button container for tree custom slot","2025-06-30T07:50:57Z","https://github.com/nuxt/ui/issues/4424",0.7308687,{"description":3037,"labels":3038,"number":3039,"owner":3029,"repository":3040,"state":3031,"title":3041,"updated_at":3042,"url":3043,"score":3044},"According to the [Vue-Iconify Docs](https://iconify.design/docs/icon-components/vue/transform.html#rotation) one can pass a `rotate` and `flip` Prop to transform the Icon, to display it in different orientations.\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003CIcon name=\"ic:round-double-arrow\" size=\"26\" :rotate=\"flip && '2'\" />\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst flip = ref(false);\r\n\u003C/script>\r\n```\r\n\r\nWhile this works fine with nuxt-icon during development, it breaks in a Prod build. The transformations no longer get applied.\r\n\r\nIt would be great if nuxt-icon could also support these props, if possible. I'm open to help with this issue if someone could give me some pointers where to start.",[],138,"icon","[Feature Request] Support Iconify Transformations","2024-03-15T09:15:14Z","https://github.com/nuxt/icon/issues/138",0.739843,{"description":3046,"labels":3047,"number":3052,"owner":3029,"repository":3030,"state":3031,"title":3053,"updated_at":3054,"url":3055,"score":3056},"### Description\n\n## No Clear Documentation for Targeting Active Styles in `NavigationMenu` Component\n\n### Description\n\nI'm trying to apply custom styles to the active state of a menu item in the `NavigationMenu` component, but there doesn't seem to be any clear documentation on how to do this.\n\nThe [theming docs](https://ui.nuxt.com/getting-started/theme#props) mention using the `:ui` attribute to target internal parts of a component, and the [theme structure for `NavigationMenu`](https://ui.nuxt.com/components/navigation-menu#theme) shows a large theme object. However, attempting to follow that structure often results in unexpected behavior—like rendering `[object Object]`, which suggests that it doesn't expect an object or the nested configuration isn’t being parsed correctly.\n\nEven large language models get tripped up when referencing the documentation. Some approaches I've tried (unsuccessfully) include:\n\n```js\nlink: {\n base: 'px-3 py-2 rounded-md',\n active: 'bg-primary text-white font-medium'\n},\nvariants: {\n active: {\n true: {\n item: 'bg-primary text-white font-medium'\n }\n }\n}\n```\n\nThe only working solution so far is using data-* attributes like this:\n```js\nlink: 'text-md data-active:bg-primary data-active:text-white'\n```\nWhile this works, it’s undocumented and feels fragile—it could easily break with a future update if it’s not the intended method.\n\n### Question\nWhat is the official and supported way to apply styles based on active state for subcomponents like link in NavigationMenu?",[3048,3051],{"name":3049,"color":3050},"question","d876e3",{"name":3023,"color":3024},4279,"Targeting active menu styles","2025-06-02T10:32:24Z","https://github.com/nuxt/ui/issues/4279",0.7502956,{"description":3058,"labels":3059,"number":3065,"owner":3029,"repository":3029,"state":3031,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.17.1\r\n- Nuxt Version: 3.8.0\r\n- CLI Version: 3.9.1\r\n- Nitro Version: 2.7.0\r\n- Package Manager: npm@9.6.7\r\n- Builder: -\r\n- User Config: devtools, nitro\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-jcxvar?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\nThe problem is when using layout named slots within pages to show different piece of data for each page. For example different menu, toolbar, header info or whatever. On each page/route change, whole layout gets re-executed. So if you have components or subcomponents with fetch calls, everything is refetched every time, event listeners are duplicated and memory usage goes up.\r\n\r\nIf NuxtLayout is added to app.vue instead pages, everything works fine. But in that case, I am unable to use named slots within pages.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3060,3062],{"name":3020,"color":3061},"8DEF37",{"name":3063,"color":3064},"🍰 p2-nice-to-have","0E8A16",23929,"named layout slots directly within pages","2025-03-12T15:13:00Z","https://github.com/nuxt/nuxt/issues/23929",0.765747,{"description":3071,"labels":3072,"number":3075,"owner":3029,"repository":3030,"state":3031,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Description\n\nHey! Thanks for trying to make nuxt/ui even more awesome.\n\nI've been struggled with adding NavigationMenu items animation on toggling collapsed of/off states. \nI'd like to make it work smoothly and keep only icons with popovers in collapsed state and show the rest only when collapsed is off. out of the box its only toggled on/off without transitions.\nI see no option to pass slot to wrap labels with vue Transition component or use Motion-vue and either css animations like data-[collaped=true]:animate.... not working well because whole inner content of nav is wrapped with \"v-if\" and switched on collapsed. \n\nIn some components data-[state] animations works well, but not in collapsed NavigationMenu. Or am I doing something wrong?\nOnly a way I see is to override whole item slot. But for now I've just get rid of NavigationMenu and made my own custom component with fancy transitions.\nPlease point me to right direction and suggest best practices, cuz I'd like to use most of components and make it work with smooth transitions/animations, but sometimes got stucked with limitations/lack of knowledge. \n\nofftop: For example, wasted many hours trying to achieve smooth slide-down transition for table expanded rows. Ended up with expanded slot with UCollapsible plus exclusive inner state for it, changed with setTimeout(() => { ... }, 300), Ugly, hucky, but it works.",[3073,3074],{"name":3049,"color":3050},{"name":3023,"color":3024},4254,"NavigationMenu transitions/animations on toggle collapsed state","2025-05-29T21:37:50Z","https://github.com/nuxt/ui/issues/4254",0.7667649,{"description":3081,"labels":3082,"number":3091,"owner":3029,"repository":3030,"state":3092,"title":3093,"updated_at":3094,"url":3095,"score":3096},"### Description\n\nHow can i custom content slot in NavigationMenu with orientation is vertical. It just work with orientation is horizontal\n\n\n\n",[3083,3084,3087,3088],{"name":3049,"color":3050},{"name":3085,"color":3086},"needs reproduction","CB47CF",{"name":3023,"color":3024},{"name":3089,"color":3090},"closed-by-bot","ededed",4097,"closed","Custom content slot in NavigationMenu","2025-05-16T02:10:16Z","https://github.com/nuxt/ui/issues/4097",0.5586042,{"description":3098,"labels":3099,"number":3103,"owner":3029,"repository":3029,"state":3092,"title":3104,"updated_at":3105,"url":3106,"score":3107},"Hey!\r\n\r\nWith our current project, me and the team was wondering what was the reasoning behind the decision to not support slots in layouts?\r\n\r\nWe ran into it when we realized that a CSS grid layout would work best for our responsive view, since each page knows what kind of sidebar or extra content is required in this specific case. For that the structure would need to be like this:\r\n\r\n```\r\nhtml\r\n head\r\n ...\r\n body\r\n my-header\r\n nuxt\r\n #content\r\n slot\r\n #sidebar\r\n slot(name=\"sidebar\")\r\n #extra\r\n slot(name=\"extra\")\r\n my-footer\r\n```\r\nRight now the two options we see are using a separate layout component or somehow coordinating sidebar and extra components to make their own requests according to current route, but both feel at odds with overall simplicity Nuxt aims for.\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c941\">#c941\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3100],{"name":3101,"color":3102},"2.x","d4c5f9",1079,"Why no slots in layouts?","2023-01-18T15:40:44Z","https://github.com/nuxt/nuxt/issues/1079",0.74793977,{"description":3109,"labels":3110,"number":3113,"owner":3029,"repository":3030,"state":3092,"title":3114,"updated_at":3115,"url":3116,"score":3117},"### Description\n\nIn the vertical pill variant I want the background of the active item to be white. It's not clear how to achieve this through the `ui` prop\n\n\n\n```\n\u003CUNavigationMenu\n orientation=\"vertical\"\n variant=\"pill\"\n :items=\"items\"\n\n :ui=\"{\n variants: {\n compoundVariants: [\n {\n variant: 'pill',\n active: true,\n highlight: false,\n class: {\n link: 'before:bg-white' // tried this but it's not working\n }\n }\n ]\n }\n }\"\n/>\n```",[3111,3112],{"name":3049,"color":3050},{"name":3023,"color":3024},3517,"How To Style NavigationMenu items","2025-05-10T11:36:22Z","https://github.com/nuxt/ui/issues/3517",0.7494991,{"description":3119,"labels":3120,"number":3123,"owner":3029,"repository":3029,"state":3092,"title":3124,"updated_at":3125,"url":3126,"score":3127},"Hello,\r\n\r\nit would be nice if `slot` areas would assignable in layout files. Often parts of the pages need to be rendered inside of the top toolbar. Thanks\r\n\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c162\">#c162\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3121,3122],{"name":3020,"color":3061},{"name":3101,"color":3102},190,"support the use of slot in layout files","2023-01-22T15:50:41Z","https://github.com/nuxt/nuxt/issues/190",0.7599283,{"labels":3129,"number":3132,"owner":3029,"repository":3029,"state":3092,"title":3133,"updated_at":3134,"url":3135,"score":3136},[3130,3131],{"name":3020,"color":3061},{"name":3101,"color":3102},6668,"Proposal to replace \u003Cnuxt> and \u003Cnuxt-child> by normal slots","2023-01-22T15:51:03Z","https://github.com/nuxt/nuxt/issues/6668",0.76024675,["Reactive",3138],{},["Set"],["ShallowReactive",3141],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fD7xhc9iLrcBnsib32pG5hi-pK1NO7sfSFSpu31N0uWQ":-1},"/nuxt/ui/4616"]