\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).",[3177],{"name":3154,"color":3155},33073,"[Enhancement] Better Syntax/Convention for Nested Layouts in Nuxt","2025-08-27T05:51:23Z","https://github.com/nuxt/nuxt/issues/33073",0.7520925,{"description":3184,"labels":3185,"number":3192,"owner":3157,"repository":3193,"state":3194,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v18.20.2`\n- Nuxt Version: `3.14.159`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.0.6`\n- Builder: `-`\n- User Config: `default`\n- Runtime Modules: `@nuxt/eslint@0.7.1`, `@nuxt/ui@3.0.0-alpha.7`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.7\n\n### Reproduction\n\nhttps://github.com/juretopolak/nuxt-ui3-toasts\n\nhttps://codesandbox.io/p/github/juretopolak/nuxt-ui3-toasts/main\n\n### Description\n\nI’ve noticed an issue where toasts fail to render properly when multiple toasts are triggered in quick succession, such as within a loop. This leads to unexpected behavior, such as:\n\n\t•\tSome toasts not appearing at all.\n\t•\tOverlapping toasts.\n\nIn the reproduction, every time a button is clicked 2 toasts should appear.\n\n### Additional context\n\nhttps://github.com/user-attachments/assets/161918f9-7ab2-45d9-aebb-493977ebbc52\n\n\n### Logs\n\n```shell-script\n\n```",[3186,3189],{"name":3187,"color":3188},"bug","d73a4a",{"name":3190,"color":3191},"v3","49DCB8",2686,"ui","closed","Problem with multiple toasts in succession","2025-01-24T14:24:11Z","https://github.com/nuxt/ui/issues/2686",0.7232441,{"description":3200,"labels":3201,"number":3204,"owner":3157,"repository":3193,"state":3194,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Environment\n\n------------------------------\n- Operating System: Windows_NT\n- Node Version: v20.9.0\n- Nuxt Version: 3.13.1\n- CLI Version: 3.13.1\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: devtools, modules, css, ui, colorMode, compatibilityDate, icon, sourcemap, experimental, nitro, future, pwa, routeRules, spaLoadingTemplate, runtimeConfig\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @vueuse/nuxt@10.11.1, @nuxtjs/mdc@0.6.1, @formkit/auto-animate/nuxt@0.8.2, @vite-pwa/nuxt@0.10.5\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.9\n\n### Reproduction\n\n`style tag`\n\n`Use`\n\n`debug`\n\n\n\n### Description\n\nSorry, I don't know if it's a bad configuration on my part, however the styles in which I use @apply don't work for me.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3202,3203],{"name":3187,"color":3188},{"name":3190,"color":3191},2763,"postcss style not applying","2024-12-05T13:48:59Z","https://github.com/nuxt/ui/issues/2763",0.73238814,{"description":3210,"labels":3211,"number":3214,"owner":3157,"repository":3215,"state":3194,"title":3216,"updated_at":3217,"url":3218,"score":3219},"\n",[3212],{"name":3187,"color":3213},"ff281a",728,"nuxt.com","Newsletter submission fails","2023-02-15T12:32:48Z","https://github.com/nuxt/nuxt.com/issues/728",0.7414913,{"description":3221,"labels":3222,"number":3227,"owner":3157,"repository":3193,"state":3194,"title":3228,"updated_at":3229,"url":3230,"score":3231},"### Description\n\nHi 👋 and thank you for the amazing work on v3!\n\nI noticed that in v3 many component have an `as` prop that is directly bound to the `as` prop of a component from RekaUI (in many cases, `Primitive`). In NuxtUI, this prop is always typed as `any | undefined`, whereas in RekaUI the type is more constrained (a string representing a HTML tag, or a component). This can cause TypeScript, and, as a consequence, linters and IDEs, to miss some obvious errors, like if someone were to write\n\n```vue\n\u003CUInput :as=\"1\" />\n```\n\nThe `as` prop type could be retrieved from the RekaUI component prop type directly using something like this\n\n```ts\ninterface InputProps {\n as?: InstanceProps\u003Ctypeof Primitive>['$props']['as']\n // Other props...\n}\n```\n\nIs there a reason that eludes me as to why this was not done?\n\nIf this seems like a good idea, I'd be happy to submit a PR.\n\nCheers!",[3223,3226],{"name":3224,"color":3225},"question","d876e3",{"name":3190,"color":3191},3068,"[v3] `as` props typing","2025-01-10T17:28:25Z","https://github.com/nuxt/ui/issues/3068",0.74185705,{"description":3233,"labels":3234,"number":3235,"owner":3157,"repository":3236,"state":3194,"title":3237,"updated_at":3238,"url":3239,"score":3240},"\r\nI get warn: `Avoid app logic that relies on enumerating keys on a component instance. The keys will be empty in production mode to avoid performance overhead.` when I use an icon component and use multiple slots at the same time.\r\n\r\n# Replication:\r\nnuxt.config.ts\r\n```javascript\r\nexport default defineNuxtConfig({\r\n devtools: { enabled: true },\r\n modules: ['@nuxt/content', \"nuxt-icon\"],\r\n content: {\r\n documentDriven: {\r\n trailingSlash: false\r\n }\r\n }\r\n})\r\n```\r\ncomponents/content/ComponentWithIcon.vue\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n Component with icon:\r\n \u003CIcon name=\"bxl:python\" class=\"w-8 h-8\" />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncomponents/content/Container.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nlayouts/full.vue:\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"custom-layout\">\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\ncontent/index.md:\r\n```markdown\r\n---\r\nlayout: 'full'\r\n---\r\n\r\n:component-with-icon\r\n\r\n::container\r\nSlot nr 1\r\n::::container\r\nSlot nr 2\r\n::::\r\n::\r\n```\r\n\r\nThis bug prevents the site from being used in development mode due to the infinity loop. The problem does not occur in the latest beta version of nuxt-icon, but in the original project I use nuxt-ui, which uses the old version \r\n",[],157,"icon","Infinite WARN loop with slots and nuxt-content","2024-09-06T11:17:31Z","https://github.com/nuxt/icon/issues/157",0.743597,{"description":3242,"labels":3243,"number":3250,"owner":3157,"repository":3157,"state":3194,"title":3251,"updated_at":3252,"url":3253,"score":3254},"### Environment\n\nReproduced with minimum Nuxt 3 environment on StackBlitz, as well as locally on a MacOS computer with Node 19.\n\n### Reproduction\n\nLink can be found here: https://stackblitz.com/edit/github-umca8w?file=app.vue\r\n\r\nA `\u003CTitle>` component will use a comment, if specified first, as the actual title.\r\n\r\n```vue\r\n\u003CTitle>\u003C!-- this will be the title --> not this\u003C/Title>\r\n```\n\n### Describe the bug\n\nA `\u003CTitle>` component will read the first element, even if it is a comment. This causes comments to be displayed as a title, not the intended text afterwords.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3244,3247],{"name":3245,"color":3246},"3.x","29bc7f",{"name":3248,"color":3249},"🍰 p2-nice-to-have","0E8A16",19716,"Head (\u003CTitle>) components should validate input better","2023-06-17T21:37:07Z","https://github.com/nuxt/nuxt/issues/19716",0.7449327,{"description":3256,"labels":3257,"number":3265,"owner":3157,"repository":3193,"state":3194,"title":3266,"updated_at":3267,"url":3268,"score":3269},"### Description\n\nIn Vue it's easy to use HTML in every component using v-html. It would be very helpful in Nuxt UI to have this feature without workarounds like slots with additional span tags. In our case we often have some html tags like: b,i,... or nbsp in our database driven app. \n\n### Additional context\n\n_No response_",[3258,3261,3262],{"name":3259,"color":3260},"enhancement","a2eeef",{"name":3190,"color":3191},{"name":3263,"color":3264},"triage","ffffff",4396,"Use HTML in label or in a new prop","2025-08-17T13:51:05Z","https://github.com/nuxt/ui/issues/4396",0.7459968,["Reactive",3271],{},["Set"],["ShallowReactive",3274],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fN4YMi38Of8D7hJCCXhdpwbD6YdXjZFOPAJwKkf_3QF0":-1},"/nuxt/ui/3103"]