\n \u003C/slot> \n```\n\n### Additional context\n\nI believe this is common throughout the library, and was wondering to post this issue or not given that there might already be a specific reason. But alas, I couldn't find one in the issues.\n\ncc, from #4411",[2934,2935,2936],{"name":2904,"color":2905},{"name":2907,"color":2908},{"name":2910,"color":2911},4435,"InputNumber increment/decrement button props not being passed to their respective slots","2025-07-01T17:13:20Z","https://github.com/nuxt/ui/issues/4435",0.7642912,{"description":2943,"labels":2944,"number":2948,"owner":2913,"repository":2914,"state":2915,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Description\n\nThis feature request proposes that the InputNumber component be enhanced with leading and trailing slot support. \n\nCurrently, components such as **Input**, **InputMenu**, **Select**, and **SelectMenu** already offer these slots for inserting custom content. For consistency across the UI library and to provide developers with a uniform customization experience, it is imperative that InputNumber is updated to include both leading and trailing slots. \n\n### Additional context\n\n_No response_",[2945,2946,2947],{"name":2904,"color":2905},{"name":2907,"color":2908},{"name":2910,"color":2911},4201,"[InputNumber] Add support for leading & trailing slots","2025-05-21T13:07:28Z","https://github.com/nuxt/ui/issues/4201",0.76560456,{"description":2954,"labels":2955,"number":2959,"owner":2913,"repository":2913,"state":2960,"title":2961,"updated_at":2962,"url":2963,"score":2964},"### 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```",[2956],{"name":2957,"color":2958},"pending triage","E99695",31522,"closed","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.73842436,{"description":2966,"labels":2967,"number":2975,"owner":2913,"repository":2914,"state":2960,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nTo control the rows of the table, I need a slot for them. For instance, if I want to implement a reorder feature using drag and drop, I require a \u003Ctr> element to loop through.\n\n### Additional context\n\n_No response_",[2968,2969,2970,2973],{"name":2904,"color":2905},{"name":2910,"color":2911},{"name":2971,"color":2972},"closed-by-bot","ededed",{"name":2974,"color":2972},"stale",2685,"[UTable] Add the functionality to include a slot for all \u003Ctr> elements, as well as a 'default' slot.","2025-06-18T09:05:45Z","https://github.com/nuxt/ui/issues/2685",0.7442374,{"description":2981,"labels":2982,"number":2992,"owner":2913,"repository":2914,"state":2960,"title":2993,"updated_at":2994,"url":2995,"score":2996},"### 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_",[2983,2986,2989,2990,2991],{"name":2984,"color":2985},"bug","d73a4a",{"name":2987,"color":2988},"nuxt/ui-pro","00dc82",{"name":2910,"color":2911},{"name":2971,"color":2972},{"name":2974,"color":2972},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.7482176,{"description":2998,"labels":2999,"number":3008,"owner":2913,"repository":2913,"state":2960,"title":3009,"updated_at":3010,"url":3011,"score":3012},"### 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).",[3000,3002,3005],{"name":2904,"color":3001},"8DEF37",{"name":3003,"color":3004},"discussion","538de2",{"name":3006,"color":3007},"3.x","29bc7f",15380,"Allow fallback slot server side for .client components","2023-01-19T17:49:21Z","https://github.com/nuxt/nuxt/issues/15380",0.7546537,{"description":3014,"labels":3015,"number":3019,"owner":2913,"repository":2914,"state":2960,"title":3020,"updated_at":3021,"url":3022,"score":3023},"### Description\n\nThe [popover](https://ui.nuxt.com/components/popover) uses the content of the default slot to create a trigger, but there is no way to provide a custom anchor. A `\u003Ctemplate #anchor>` slot for this purpose would be great.\n\n```html\n\u003CUFormField label=\"name\" name=\"name\">\n \u003CUPopover :open=\"isAutoCompleteOpen\">\n \u003Ctemplate #anchor>\n \u003CUInput v-model=\"state.name\" />\n \u003C/template>\n \u003Ctemplate #content>\n \u003CPlaceholder class=\"size-48 m-4 inline-flex\" />\n \u003C/template>\n \u003C/UPopover>\n\u003C/UFormField>\n```\n\nMy use case is building an autocomplete for a text input. The `InputMenu` is not suitable because the dropdown is too intrusive.\n\n### Additional context\n\n_No response_",[3016,3017,3018],{"name":2904,"color":2905},{"name":2907,"color":2908},{"name":2910,"color":2911},4013,"Add ability to provide an anchor for the popover","2025-05-22T15:04:18Z","https://github.com/nuxt/ui/issues/4013",0.7553188,{"description":3025,"labels":3026,"number":3029,"owner":2913,"repository":2913,"state":2960,"title":3030,"updated_at":3031,"url":3032,"score":3033},"### Environment\n\nNuxt 3.0.0-rc.11\n\n### Reproduction\n\nStackBlitz: https://stackblitz.com/edit/nuxt3-layout-slot-bug\n\n### Describe the bug\n\nLayout slots not working with default layout, generate error (see reproduction):\r\n\r\n```\r\nError: Codegen node is missing for element/if/for node. Apply appropriate transforms first.\r\n```\r\n\r\nNote the use of `app.vue`.\r\n\r\nExplicitly using `\u003CNuxtLayout>` with `layout: false` in page meta works but leads to full re-render of the layout and kinda defies the purpose of a default layout.\r\n\r\nNot sure if I'm doing something wrong with the setup, but following the docs, the code in the repro should work. Also, best in terms of DX IMO.\n\n### Additional context\n\nThis is a typical use case where you for instance have a nav and want to add additional items via a slot on specific pages.\n\n### Logs\n\n_No response_",[3027,3028],{"name":3006,"color":3007},{"name":2957,"color":2958},15158,"Layout slots not working in default layout","2023-09-26T14:37:01Z","https://github.com/nuxt/nuxt/issues/15158",0.75903773,["Reactive",3035],{},["Set"],["ShallowReactive",3038],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fiArkJ05Yq1vgV3h_LxDRCWSH2ZvDIVNfLoreVSgGWRA":-1},"/nuxt/ui/4424"]