\r\n \u003C/AppButton>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n```vue\r\n\u003C!-- App.vue -->\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CServerComp>\r\n Some slot content here\r\n \u003C/ServerComp>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3065,3068,3071],{"name":3066,"color":3067},"3.x","29bc7f",{"name":3069,"color":3070},"馃敤 p3-minor","FBCA04",{"name":3024,"color":3025},25423,"closed","Respect named slots in server components","2024-03-06T15:26:20Z","https://github.com/nuxt/nuxt/issues/25423",0.7163974,{"description":3079,"labels":3080,"number":3084,"owner":3027,"repository":3027,"state":3073,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Environment\n\nWorking directory: /Users/guillermolopez/drite/server-component nuxi 9:05:10 PM\nNuxt project info: (copied to clipboard) nuxi 9:05:10 PM\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.12.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@9.4.0\n- Builder: -\n- User Config: compatibilityDate, devtools, experimental, future, modules\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/fonts@0.11.0, @nuxt/icon@1.11.0, @nuxt/image@1.10.0, @nuxt/ui@3.0.1\n- Build Modules: -\n------------------------------\n\n馃憠 Report an issue: https://github.com/nuxt/nuxt/issues/new?template=bug-report.yml\n馃憠 Suggest an improvement: https://github.com/nuxt/nuxt/discussions/new\n馃憠 Read documentation: https://nuxt.com\n\n### Reproduction\n\nCreate new project\n\nCreate a button component:\n```\n\u003Cscript lang=\"ts\" setup>\u003C/script>\n\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cslot />\n \u003C/div>\n\u003C/template>\n\n```\n\ncreate a index.server.page:\n```\n\u003Cscript lang=\"ts\" setup>\u003C/script>\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cp>Hello world\u003C/p>\n \u003CVButton> Text \u003C/VButton>\n \u003C/div>\n\u003C/template>\n\n```\n\nnuxt.config\n```\nexperimental: {\n componentIslands: {\n selectiveClient: \"deep\",\n },\n },\n future: {\n compatibilityVersion: 4,\n },\n```\n\n### Describe the bug\n\nThe button component is not rendering the content when selectiveClient: \"deep\" but if selectiveClient is true it worked, but as we know we can not use nuxt-client without using \"deep\"\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3081],{"name":3082,"color":3083},"pending triage","E99695",31522,"Slots are not working in components inside a server only page when selectiveClient is deep","2025-03-25T19:12:58Z","https://github.com/nuxt/nuxt/issues/31522",0.74230963,{"description":3090,"labels":3091,"number":3095,"owner":3027,"repository":3027,"state":3073,"title":3096,"updated_at":3097,"url":3098,"score":3099},"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>",[3092],{"name":3093,"color":3094},"2.x","d4c5f9",1079,"Why no slots in layouts?","2023-01-18T15:40:44Z","https://github.com/nuxt/nuxt/issues/1079",0.7437143,{"description":3101,"labels":3102,"number":3105,"owner":3027,"repository":3027,"state":3073,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Environment\n\nnpx nuxi info\n\n### Reproduction\n\nRead in additional context\n\n### Describe the bug\n\nRead in additional context\n\n### Additional context\n\nThere is such a component (screenshot 1), it recursively renders blocks that are specified in the CMS. A block can have slots, such as the GridBlock block (screenshot 2). The names of all slots are set dynamically, and also in the component that draws the blocks, I also pass the name of the slot dynamically to v-slot, but vue-tsc throws an error (screenshot 3), according to the types slotName is STRING (screenshot 4). In dev mode, everything works fine, rendering goes as it should! The problem is that the project does not build due to this error (Blocks may not have slots! To do this, you can check for the presence of slots in the block object, but everything works fine in dev mode anyway). Help what can be done?\r\n\r\n\r\n\r\n\r\n\n\n### Logs\n\n_No response_",[3103,3104],{"name":3066,"color":3067},{"name":3082,"color":3083},21557,"Nuxt3 - v-slot","2023-06-14T08:13:36Z","https://github.com/nuxt/nuxt/issues/21557",0.7462621,{"description":3111,"labels":3112,"number":3116,"owner":3027,"repository":3027,"state":3073,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.0\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n[StackBlitz](https://stackblitz.com/edit/nuxt-issues-25011)\r\n\r\n0. Enable `experimental.componentIslands` by setting it to `'local'`\r\n1. Create a `CtaButton.server.vue` component in `components`\r\n2. Render a `slot` in there:\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cbutton>\r\n \u003Cslot />\r\n \u003C/button>\r\n\u003C/template>\r\n```\r\n\r\n3. Render it in `app.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CCtaButton>Test\u003C/CtaButton>\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n\r\n4. See hydration error in the console\r\n\r\n### Describe the bug\r\n\r\nA hydration error occurs.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3113,3114,3115],{"name":3066,"color":3067},{"name":3069,"color":3070},{"name":3024,"color":3025},25011,"Slot in server component causes hydration issues","2024-01-17T14:11:07Z","https://github.com/nuxt/nuxt/issues/25011",0.7539962,{"description":3122,"labels":3123,"number":3127,"owner":3027,"repository":3027,"state":3073,"title":3128,"updated_at":3129,"url":3130,"score":3131},"### Describe the feature\r\n\r\nhttps://github.com/nuxt/framework/pull/8713#discussion_r1014787331\r\n\r\nCurrently, the treeshake module treeshakes the non-fallback slots within `\u003CClientOnly>` components.\r\nBut fallback slot does not exists in [`ServerPlaceholder`](https://github.com/nuxt/framework/blob/main/packages/nuxt/src/app/components/server-placeholder.ts) that is used server-side for .client component that are converted with [`createClientOnly()`](https://github.com/nuxt/framework/blob/fe433a4222dd9248ec04bd17b366ffa1aa00f94e/packages/nuxt/src/app/components/client-only.mjs#L23-L-74). We can add a `fallback` slot to `ServerPlaceholder` so the users can have a fallback if they wish instead of a `\u003Cdiv>` with inherited attributes\r\n\r\n\r\n\r\n### Additional information\r\n\r\n- [x] 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://v3.nuxtjs.org/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/framework/discussions) and [issues](https://github.com/nuxt/framework/issues).",[3124,3125,3126],{"name":3037,"color":3038},{"name":3054,"color":3055},{"name":3066,"color":3067},15380,"Allow fallback slot server side for .client components","2023-01-19T17:49:21Z","https://github.com/nuxt/nuxt/issues/15380",0.75464386,{"description":3133,"labels":3134,"number":3149,"owner":3027,"repository":3150,"state":3073,"title":3151,"updated_at":3152,"url":3153,"score":3154},"### 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_",[3135,3138,3141,3144,3147],{"name":3136,"color":3137},"bug","d73a4a",{"name":3139,"color":3140},"nuxt/ui-pro","00dc82",{"name":3142,"color":3143},"triage","ffffff",{"name":3145,"color":3146},"closed-by-bot","ededed",{"name":3148,"color":3146},"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.75636417,["Reactive",3156],{},["Set"],["ShallowReactive",3159],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fgLdgKyvcaJ1XXkHpdtdFVq3X-q-6p4z1i3sbSqLN_9o":-1},"/nuxt/nuxt/18853"]