clearly says that I have Message component inside Chat directory. \r\n* When I say `\u003CChatMessage />` I have no idea if that is ChatMessage.vue file or Chat/Message.vue. \r\n* If I have large application with lots of nested components, I end up with something like `\u003CAdminDashboardModelsUserProfile />` which is tragic to read.\r\n\r\nThanks for all the hard work!\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3171,3174],{"name":3172,"color":3173},"enhancement","8DEF37",{"name":3175,"color":3176},"discussion","538de2",23287,"nuxt","open","Can template compiler please understand \u003CChat/Message /> syntax?","2024-06-30T11:07:32Z","https://github.com/nuxt/nuxt/issues/23287",0.7021263,{"description":3185,"labels":3186,"number":3191,"owner":3178,"repository":3178,"state":3179,"title":3192,"updated_at":3193,"url":3194,"score":3195},"- [ ] `useAsyncData.pending`\n - `pending`\n - `experimental.pendingWhenIdle`\n- [x] `ObjectPluginInput`\n- [x] `isNuxt2`\n- [x] `isNuxt3`\n- [x] `nuxtCtx` (remove export)\n- [x] `useId`\n- [x] `getRouteRules(url)`\n- [x] `setResponseStatus(code, message)`\n- [x] `TagPositionProps.body`\n- [ ] `globalProps.renderPriority`\n- [x] Head: `\u003Clink methods />`\n- [x] Head: `\u003Clink target />`\n- [x] Head: `\u003Cstlye scoped>`\n- [x] `useServerHead`\n- [x] `useServerHeadSafe`\n- [x] `useServerSeoMeta`\n- [x] `NuxtPlgin.ssr`\n- [x] `ConfigSchema.app.rootId`\n- [x] `ConfigSchema.app.teleportId`\n- [ ] `experimental.serverAppConfig`\n\nToDos:\n- Codemods?",[3187,3188],{"name":3175,"color":3176},{"name":3189,"color":3190},"5.x","006b75",32960,"Possible removals of deprecated features with v5","2025-08-22T09:32:56Z","https://github.com/nuxt/nuxt/issues/32960",0.76009005,{"description":3197,"labels":3198,"number":3202,"owner":3178,"repository":3203,"state":3204,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 4.0.0\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.0\n- Package Manager: pnpm@10.10.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, colorMode, fonts, icon\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxt/eslint@1.4.1, @vueuse/nuxt@13.5.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.3\n\n### Reproduction\n\n- \n\n### Description\n\n Description\n\n The UChatMessage component has two issues with the parts prop:\n 1. The parts prop appears to be completely non-functional - it doesn't render any parts regardless of configuration\n 2. The content prop is required even when using parts, but providing both causes conflicts\n\n Expected Behavior\n\n 1. When parts prop is provided, it should render structured message content (text, reasoning, tool invocations, etc.) as documented\n 2. The content prop should be optional when parts is provided, or at minimum not interfere with parts rendering\n\n Actual Behavior\n\n 1. The parts prop doesn't render anything - no text parts, reasoning parts, or tool invocation parts appear\n 2. Removing the content prop causes Vue warnings about missing required prop and the page doesn't render at all\n 3. When both content and parts are provided, only the content is shown\n\n Reproduction Steps\n\n 1. Test parts alone (breaks completely):\n \u003CUChatMessage\n :parts=\"[\n { type: 'text', text: 'Main message' },\n { type: 'reasoning', reasoning: 'This is the reasoning' }\n ]\"\n />\n 1. Result: Vue warning \"Missing required prop: 'content'\" and nothing renders\n 2. Test parts with content (parts ignored):\n \u003CUChatMessage\n content=\"Main message\"\n :parts=\"[\n { type: 'text', text: 'Main message' },\n { type: 'reasoning', reasoning: 'This is the reasoning' }\n ]\"\n />\n 2. Result: Only \"Main message\" displays, reasoning part is completely ignored\n 3. Test different part types:\n \u003CUChatMessage\n content=\"fallback\"\n :parts=\"[\n { type: 'text', text: 'Text part' },\n { type: 'tool-invocation', toolInvocation: { /* tool data */ } }\n ]\"\n />\n 3. Result: Only \"fallback\" content shows, no parts render\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3199],{"name":3200,"color":3201},"v4","49DCB8",4685,"ui","closed","UI Pro: ChatMessage: parts prop not working and content prop is required even when using parts","2025-08-12T08:32:49Z","https://github.com/nuxt/ui/issues/4685",0.6718313,{"description":3210,"labels":3211,"number":3220,"owner":3178,"repository":3178,"state":3204,"title":3221,"updated_at":3222,"url":3223,"score":3224},"### Describe the feature\n\nA component to render it slot only during dev would be useful in some cases.\r\n\r\nThe content should be tree shaken during build\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://v3.nuxtjs.org/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3212,3213,3214,3217],{"name":3172,"color":3173},{"name":3175,"color":3176},{"name":3215,"color":3216},"3.x","29bc7f",{"name":3218,"color":3219},"🍰 p2-nice-to-have","0E8A16",15066,"Add `DevOnly` component","2023-01-19T17:44:35Z","https://github.com/nuxt/nuxt/issues/15066",0.7350015,{"description":3226,"labels":3227,"number":3242,"owner":3178,"repository":3203,"state":3204,"title":3243,"updated_at":3244,"url":3245,"score":3246},"### 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_",[3228,3231,3234,3237,3240],{"name":3229,"color":3230},"bug","d73a4a",{"name":3232,"color":3233},"nuxt/ui-pro","00dc82",{"name":3235,"color":3236},"triage","ffffff",{"name":3238,"color":3239},"closed-by-bot","ededed",{"name":3241,"color":3239},"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.7376436,{"description":3248,"labels":3249,"number":3256,"owner":3178,"repository":3178,"state":3204,"title":3257,"updated_at":3258,"url":3259,"score":3260},"First I really have to say I love what you do with the framework amazing just started yesterday and creating my first project with nuxt.js already!\r\n\r\nI was wondering what will be the best approach on the following? this is my default layout:\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cnav-bar />\r\n \u003Cnuxt/>\r\n \u003Cmy-footer/>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\nI want to reuse the layout but to add additional logic or props based on routes so it works really well for `/` but when ever I go to `/search` I want an extra prop for `\u003Cnav-bar />` something like that:\r\n\r\n````\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cnav-bar :logo=\"true\" />\r\n \u003Cnuxt/>\r\n \u003Cmy-footer/>\r\n \u003C/div>\r\n\u003C/template>\r\n````\r\n\r\nBecause the routes are hidden/generated I'm not really sure what the best way to approach this without duplicating the layout?\r\n\r\nThanks a lot\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/c152\">#c152\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3250,3253],{"name":3251,"color":3252},"question","cc317c",{"name":3254,"color":3255},"2.x","d4c5f9",180,"conditional logic or props to layouts?","2023-01-18T15:38:32Z","https://github.com/nuxt/nuxt/issues/180",0.74154204,{"labels":3262,"number":3268,"owner":3178,"repository":3178,"state":3204,"title":3269,"updated_at":3270,"url":3271,"score":3272},[3263,3264,3267],{"name":3241,"color":3236},{"name":3265,"color":3266},"pending triage","E99695",{"name":3254,"color":3255},7274,"Page Props","2023-01-22T15:34:50Z","https://github.com/nuxt/nuxt/issues/7274",0.7429638,{"description":3274,"labels":3275,"number":3278,"owner":3178,"repository":3178,"state":3204,"title":3279,"updated_at":3280,"url":3281,"score":3282},"Button Component\r\n\r\n\r\nUsage of Button\r\n\r\n\r\n\r\n### Versions\r\n- nuxt: 3 latest beta\r\n- node: 14.17.1\r\n\r\n### What is Expected?\r\nIntellisense should detect component prop in template\r\n\r\nProbably related to issue https://github.com/johnsoncodehk/volar/issues/460\r\n",[3276,3277],{"name":3265,"color":3266},{"name":3254,"color":3255},9920,"Prop type inference error in template","2023-01-22T15:45:05Z","https://github.com/nuxt/nuxt/issues/9920",0.74809384,{"description":3284,"labels":3285,"number":3291,"owner":3178,"repository":3178,"state":3204,"title":3292,"updated_at":3293,"url":3294,"score":3295},"### Environment\n\nnuxt rc 13\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-g7nvjf?file=app.vue\n\n### Describe the bug\n\nHi :wave: this is a very small issue, currently it seems that `ClientOnly` is trying to make its default slot inherit its attributes. It triggers a warn message in the console since the default slot is rendered using a Fragment.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3286,3287,3288],{"name":3215,"color":3216},{"name":3229,"color":3230},{"name":3289,"color":3290},"🔨 p3-minor","FBCA04",15444,"ClientOnly attrs are passed to the default slot","2023-01-19T17:50:34Z","https://github.com/nuxt/nuxt/issues/15444",0.75132906,{"labels":3297,"number":3300,"owner":3178,"repository":3178,"state":3204,"title":3301,"updated_at":3302,"url":3303,"score":3304},[3298,3299],{"name":3215,"color":3216},{"name":3265,"color":3266},14410,"createClientOnly return a component that cannot transfer the ref of its child","2023-01-19T17:35:09Z","https://github.com/nuxt/nuxt/issues/14410",0.75270444,["Reactive",3306],{},["Set"],["ShallowReactive",3309],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUGzkUhVLzAYx01pc6vvG7-FSOdoBCyGneX2M6tM8hI8":-1},"/nuxt/ui/4423"]