\n\n \u003C!-- With logo and download button -->\n \u003CUQRCode \n value=\"https://github.com/nuxt/ui\"\n logo=\"https://nuxt.com/favicon.ico\"\n logoSize=\"20\"\n showDownloadButton\n downloadName=\"nuxt-ui-qrcode\"\n />\n\u003C/template>",[3157,3158,3159],{"name":3138,"color":3139},{"name":3144,"color":3145},{"name":3160,"color":3142},"v4",4932,"[Component Request] Add QRCode component (support customization & accessibility)","2025-09-09T13:53:02Z","https://github.com/nuxt/ui/issues/4932",0.7007968,{"description":3167,"labels":3168,"number":3172,"owner":3147,"repository":3147,"state":3149,"title":3173,"updated_at":3174,"url":3175,"score":3176},"### Describe the feature\n\nAdd documentation for Nuxt Components \n\n\n\n\nComparison between Vue template Component and Nuxt Layout Component, there is no documentation for hovering over the element unlike others\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3169],{"name":3170,"color":3171},"pending triage","E99695",32330,"Better IDE Docs","2025-06-08T03:26:08Z","https://github.com/nuxt/nuxt/issues/32330",0.7033397,{"description":3178,"labels":3179,"number":3182,"owner":3147,"repository":3148,"state":3149,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### Description\n\nIn the Nuxt UI documentation, the theme configuration JSON for components is extremely helpful for understanding default styles and customizing them. However, these blocks currently do not support expanding/collapsing of nested sections like slots, variants, or size, which makes navigation and readability difficult—especially for large configuration trees.\n\n**Feature Request:**\nAdd interactive expand/collapse support to nested JSON blocks in the theme section of the Nuxt UI docs. This can be similar to how most code editors and browser devtools handle JSON structures, allowing users to collapse/expand objects or arrays.\n\n**Use Cases:**\n- Improved UX for developers customizing UI themes\n- Faster navigation when working with deeply nested or verbose configurations\n- Easier understanding of available slots and variants without scrolling through long blocks\n\n**Alternatives Considered:**\n- Copying the JSON into a code editor to navigate — which breaks the in-context experience\n- Searching for keys manually, which is slow and error-prone\n\n**Prototype / Reference:**\nAlthough no direct prototype is available, the expected behavior is similar to how Vue DevTools or VSCode handles collapsible JSON structures.\n\n\u003Cimg width=\"844\" height=\"619\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/14f7ccb8-3e7e-41f5-8b6e-6ffc5f2ba150\" />\n\n### Additional context\n\n_No response_",[3180,3181],{"name":3138,"color":3139},{"name":3144,"color":3145},4606,"✨ Expand/Collapse Support for Component Theme JSON in Nuxt UI Docs","2025-07-26T11:50:47Z","https://github.com/nuxt/ui/issues/4606",0.7115098,{"description":3188,"labels":3189,"number":3195,"owner":3147,"repository":3147,"state":3149,"title":3196,"updated_at":3197,"url":3198,"score":3199},"### 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_",[3190,3192],{"name":3138,"color":3191},"8DEF37",{"name":3193,"color":3194},"🍰 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.72220165,{"description":3201,"labels":3202,"number":3204,"owner":3147,"repository":3147,"state":3149,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Describe the feature\n\n### Context\n\nCurrently, Nuxt supports layouts via the `layouts/` directory and supports nested UI sections using **nested routes** (e.g., `pages/profile.vue` wrapping `pages/profile/favorite.vue`). While this works, once the project grows with many folders and files, the pattern of mixing `parent.vue` (used as a wrapper) alongside actual child routes can get confusing and lose context.\n\nFor example:\n\n```\npages/\n ├─ profile.vue // Parent layout wrapper\n └─ profile/\n ├─ index.vue // Child route\n └─ favorite.vue // Child route\n```\n\nHere, `profile.vue` is conceptually acting as a **nested layout**, but it is treated as a page, which can make code organization less clear.\n\n### Problem\n\n* `parent.vue` files inside `pages/` double as both “layout” and “page,” which can blur their purpose.\n* As the folder structure deepens, it becomes harder to distinguish what is a layout wrapper and what is an actual page.\n* The developer has to “remember” which `.vue` file is serving as a pseudo-layout.\n\n### Proposal / Suggestion\n\nIntroduce a **dedicated convention** for nested layouts within route groups.\n\nFor example:\n\n```\npages/\n └─ profile/\n ├─ @layout.vue // Explicitly marks this as the wrapper layout\n ├─ index.vue // Child route\n └─ favorite.vue // Child route\n```\n\nUsage:\n\n```vue\n\u003C!-- pages/profile/@layout.vue -->\n\u003Ctemplate>\n \u003Cdiv class=\"flex\">\n \u003CSidebar />\n \u003CNuxtPage /> \u003C!-- renders children like index.vue, favorite.vue -->\n \u003C/div>\n\u003C/template>\n```\n\nThis improves clarity by:\n\n* Explicitly distinguishing **nested layout files** from **page files**.\n* Avoiding the overloaded role of `parent.vue`.\n* Making folder structures self-explanatory.\n\n### Benefits\n\n* More intuitive project structure for large apps.\n* Easier onboarding for new developers (clear separation of layouts vs. pages).\n* Cleaner, scalable convention that aligns with the mental model of “global layouts” vs. “section layouts.”\n\n### Additional information\n\n- [x] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3203],{"name":3170,"color":3171},33073,"[Enhancement] Better Syntax/Convention for Nested Layouts in Nuxt","2025-08-27T05:51:23Z","https://github.com/nuxt/nuxt/issues/33073",0.7224276,{"description":3210,"labels":3211,"number":3217,"owner":3147,"repository":3147,"state":3149,"title":3218,"updated_at":3219,"url":3220,"score":3221},"### Describe the feature\n\nHello,\r\n\r\nIt could help modules authors to have helps for adding things to the head.\r\n\r\nhttps://nuxt.com/docs/api/nuxt-config#head\n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3212,3213,3216],{"name":3138,"color":3191},{"name":3214,"color":3215},"good first issue","fbca04",{"name":3193,"color":3194},25469,"Add Nuxt Kit helpers for `app.head`","2025-02-03T11:53:20Z","https://github.com/nuxt/nuxt/issues/25469",0.72262335,{"description":3223,"labels":3224,"number":3228,"owner":3147,"repository":3148,"state":3229,"title":3230,"updated_at":3231,"url":3232,"score":3233},"### Description\n\nDescription:\nI am currently using the UTable component from Nuxt UI and have encountered a limitation regarding the customization of table headers. Specifically, I need to create a table with multi-row headers and the ability to merge columns using colspan. For example, the multi-row spanning column headers shown in the image.However, the current implementation of the UTable component does not seem to support this feature.\n\n\nCurrent Behavior:\n\nThe header property allows for custom content using the h function, but it is limited to single-column customization.\nThe available slots are primarily designed for single-column or specific row customization and do not support multi-column header customization.\nExpected Behavior:\n\nAbility to define headers that span multiple rows and columns.\nSupport for colspan and rowspan attributes in the header configuration to allow for more complex table layouts.\nEnhanced slot functionality to support multi-column header customization.\nUse Case:\nThis feature is essential for creating complex data tables where grouped headers are necessary for better data organization and presentation. It is particularly useful in scenarios where data needs to be categorized under broader headings.\n\nProposed Solution:\n\nIntroduce a mechanism in the UTable component to allow for multi-row and multi-column header definitions.\nProvide examples and documentation on how to implement these features using the existing API or through new enhancements.\nConsider expanding the slot functionality to support more complex header customizations.\nAdditional Context:\n\nThis feature is commonly supported in other table libraries and would greatly enhance the flexibility and usability of the UTable component in Nuxt UI.\nEnvironment:\n\nNuxt UI version: [3.0.0-alpha.12]\nNuxt version: [^3.15.4]\n\nRelated Issues Link:\nhttps://github.com/nuxt/ui/issues/1289#issuecomment-2652919275\nhttps://github.com/nuxt/ui/issues/1651\nhttps://github.com/nuxt/ui/issues/2053\n\nRelated Documentation Link:\nhttps://ui3.nuxt.dev/components/table\n\n### Additional context\n\n_No response_",[3225,3226,3227],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},3296,"closed","Support for Multi-Row and Colspan Headers in UTable Component","2025-07-01T12:05:35Z","https://github.com/nuxt/ui/issues/3296",0.67282695,{"description":3235,"labels":3236,"number":3249,"owner":3147,"repository":3148,"state":3229,"title":3250,"updated_at":3251,"url":3252,"score":3253},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools, extends, modules\r\n- Runtime Modules: @nuxt/ui@2.18.4\r\n- Build Modules: -\n\n### Version\n\n2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-qsqtmc?file=app.vue\n\n### Description\n\nLandingFAQ being built on top Accordion, when an item has a specified \"slot\" property, it should allow to display custom content in a corresponding slot. In my reproduction, you can see i have an faq item with a slot property equal to \"risks\". When using \u003Ctemplate #risks> risks \u003C/template> to show a specific content for that item, it works well in the accordion but is ignored in the LandingFAQ where the content property is shown instead.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3237,3240,3243,3244,3247],{"name":3238,"color":3239},"bug","d73a4a",{"name":3241,"color":3242},"nuxt/ui-pro","00dc82",{"name":3144,"color":3145},{"name":3245,"color":3246},"closed-by-bot","ededed",{"name":3248,"color":3246},"stale",2057,"LandingFAQ component in Pro ignores the \"slot\" property of an item","2025-06-18T09:06:25Z","https://github.com/nuxt/ui/issues/2057",0.6915347,{"labels":3255,"number":3260,"owner":3147,"repository":3147,"state":3229,"title":3261,"updated_at":3262,"url":3263,"score":3264},[3256,3257],{"name":3138,"color":3191},{"name":3258,"color":3259},"2.x","d4c5f9",6668,"Proposal to replace \u003Cnuxt> and \u003Cnuxt-child> by normal slots","2023-01-22T15:51:03Z","https://github.com/nuxt/nuxt/issues/6668",0.6919185,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3iuIZt7e15xubsSaFt0g-ES2SM6gwAETSzlciVMc2yM":-1},"/nuxt/ui/4782"]