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).",[3019,3022],{"name":3020,"color":3021},"enhancement","8DEF37",{"name":3023,"color":3024},"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":3033,"labels":3034,"number":3043,"owner":3026,"repository":3026,"state":3044,"title":3045,"updated_at":3046,"url":3047,"score":3048},"### 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).",[3035,3036,3037,3040],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3038,"color":3039},"3.x","29bc7f",{"name":3041,"color":3042},"馃嵃 p2-nice-to-have","0E8A16",15066,"closed","Add `DevOnly` component","2023-01-19T17:44:35Z","https://github.com/nuxt/nuxt/issues/15066",0.7350015,{"description":3050,"labels":3051,"number":3066,"owner":3026,"repository":3067,"state":3044,"title":3068,"updated_at":3069,"url":3070,"score":3071},"### 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_",[3052,3055,3058,3061,3064],{"name":3053,"color":3054},"bug","d73a4a",{"name":3056,"color":3057},"nuxt/ui-pro","00dc82",{"name":3059,"color":3060},"triage","ffffff",{"name":3062,"color":3063},"closed-by-bot","ededed",{"name":3065,"color":3063},"stale",2057,"ui","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":3073,"labels":3074,"number":3081,"owner":3026,"repository":3026,"state":3044,"title":3082,"updated_at":3083,"url":3084,"score":3085},"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>",[3075,3078],{"name":3076,"color":3077},"question","cc317c",{"name":3079,"color":3080},"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":3087,"number":3093,"owner":3026,"repository":3026,"state":3044,"title":3094,"updated_at":3095,"url":3096,"score":3097},[3088,3089,3092],{"name":3065,"color":3060},{"name":3090,"color":3091},"pending triage","E99695",{"name":3079,"color":3080},7274,"Page Props","2023-01-22T15:34:50Z","https://github.com/nuxt/nuxt/issues/7274",0.7429638,{"description":3099,"labels":3100,"number":3103,"owner":3026,"repository":3026,"state":3044,"title":3104,"updated_at":3105,"url":3106,"score":3107},"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",[3101,3102],{"name":3090,"color":3091},{"name":3079,"color":3080},9920,"Prop type inference error in template","2023-01-22T15:45:05Z","https://github.com/nuxt/nuxt/issues/9920",0.74809384,{"description":3109,"labels":3110,"number":3116,"owner":3026,"repository":3026,"state":3044,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### 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_",[3111,3112,3113],{"name":3038,"color":3039},{"name":3053,"color":3054},{"name":3114,"color":3115},"馃敤 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":3122,"number":3125,"owner":3026,"repository":3026,"state":3044,"title":3126,"updated_at":3127,"url":3128,"score":3129},[3123,3124],{"name":3038,"color":3039},{"name":3090,"color":3091},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,{"description":3131,"labels":3132,"number":3134,"owner":3026,"repository":3026,"state":3044,"title":3135,"updated_at":3136,"url":3137,"score":3138},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools, modules\r\n- Runtime Modules: @nuxt/content@2.13.0\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-starter-mzb2e5\r\n\r\nOpen the console and click on the \"Link\".\r\n\r\n### Describe the bug\r\n\r\nIf you create a composable with `useLazyAsyncData` and then call it inside `ClientOnly` component it will log the below warning when you want to navigate between pages:\r\n\r\n```\r\nchunk-2XHGWBZJ.js?v=008d553a:1512 [Vue warn]: Slot \"default\" invoked outside of the render function: this will not track dependencies used in the slot. Invoke the slot function inside the render function instead. \r\n at \u003CRouterView name=undefined route=undefined > \r\n at \u003CNuxtPage> \r\n at \u003CDefault ref=Ref\u003C Proxy(Object)聽{鈥 > > \r\n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \r\n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \r\n at \u003CNuxtLayout> \r\n at \u003CApp key=3 > \r\n at \u003CNuxtRoot>\r\n```\r\n\r\n### Additional context\r\n\r\nUsing `useLazyAsyncData` directly inside the component is Okay and works without problem.\r\n\r\n### Logs\r\n\r\n_No response_",[3133],{"name":3038,"color":3039},27752,"Slot \"default\" invoked outside of the render function when using a composable (contains useLazyAsyncData) inside ClientOnly component","2024-06-24T10:03:48Z","https://github.com/nuxt/nuxt/issues/27752",0.7529646,{"description":3140,"labels":3141,"number":3143,"owner":3026,"repository":3026,"state":3044,"title":3144,"updated_at":3145,"url":3146,"score":3147},"Hi!\r\n\r\nRight now there is no context in the layouts.\r\n\r\nI can understand why there is no context in components and it is not a problem. I can inject needed variables from pages to components via props. As described [here ](https://nuxtjs.org/faq/async-data-components)\r\n\r\nBut how I can do it with layout?\r\n\r\nFor example I would love to do things like this:\r\n```html\r\n\u003Cdiv v-if=\"isDev\"> [...] \u003C/div>\r\n```\r\nor like to change some layouts component according to the ``http.Request`` etc.\r\n\r\n\r\nIs it possible to add context to the layouts or maybe there is some workaround?\r\n\r\n\r\nThanks in advance,\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/c238\">#c238\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3142],{"name":3079,"color":3080},280,"Context support in layouts","2023-01-18T15:38:41Z","https://github.com/nuxt/nuxt/issues/280",0.75548613,["Reactive",3149],{},["Set"],["ShallowReactive",3152],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUGzkUhVLzAYx01pc6vvG7-FSOdoBCyGneX2M6tM8hI8":-1},"/nuxt/ui/4423"]