\n \u003C/template>\n\n \u003Ctemplate v-else>\n \u003CDynamicRenderer :config=\"slotContent\" :key=\"slotContent.name || slotName\" />\n \u003C/template>\n \u003C/template>\n \u003C/component>\n\u003C/template>\n```\n\n\n\n#### `index.vue`\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { UButton, UCard, UContainer, UForm, UFormField, UInput } from '#components'\n\nconst config = {\n component: UContainer,\n class: 'h-screen flex justify-center items-center',\n slots: {\n default: [\n {\n component: UCard,\n slots: {\n default: [{\n component: UForm,\n class: 'space-y-4',\n slots: {\n default: [\n {\n component: UFormField,\n label: 'Username',\n name: 'username',\n required: true,\n slots: {\n default: [\n {\n component: UInput,\n placeholder: 'Enter Username',\n value: 'hh'\n }\n ]\n }\n },\n {\n component: UFormField,\n label: 'Password',\n name: 'password',\n required: true,\n slots: {\n default: [\n {\n component: UInput,\n type: 'password',\n placeholder: 'Enter Password',\n value: 'hh'\n }\n ]\n }\n },\n {\n component: UButton,\n label: 'Login',\n icon: 'i-lucide-user',\n variant: 'soft',\n type: 'submit',\n block: true\n }\n ]\n }\n }]\n }\n }\n ]\n }\n}\n\u003C/script>\n\n\u003Ctemplate>\n \u003CDynamicRenderer :config=\"config\" />\n\u003C/template>\n```\n\n### Result \n\n\nIt would also be great if using this approach could eliminate the need to manually import components like:\n\n```ts\nimport { UButton, UCard, UContainer, UForm, UFormField, UInput } from '#components'\n```\n\nand instead rely on automatic resolution by the renderer itself.\n\nThanks for your work on Nuxt UI – it’s a fantastic toolkit!\n\n### Additional context\n\n_No response_",[2873,2874],{"name":2857,"color":2858},{"name":2860,"color":2861},4138,"✨ Feature Request: Add `\u003CDynamicRenderer>` component for config-driven UI rendering","2025-05-12T16:36:30Z","https://github.com/nuxt/ui/issues/4138",0.754656,{"description":2881,"labels":2882,"number":2888,"owner":2863,"repository":2864,"state":2889,"title":2890,"updated_at":2891,"url":2892,"score":2893},"### Description\n\nAt the moment InputNumber does not react in any way to the presence of ButtonGroup.\n\n\n\n### Additional context\n\n_No response_",[2883,2884,2887],{"name":2857,"color":2858},{"name":2885,"color":2886},"v3","49DCB8",{"name":2860,"color":2861},4155,"closed","InputNumber ButtonGroup support","2025-05-15T12:30:59Z","https://github.com/nuxt/ui/issues/4155",0.71276116,{"description":2895,"labels":2896,"number":2899,"owner":2863,"repository":2864,"state":2889,"title":2900,"updated_at":2901,"url":2902,"score":2903},"### Description\n\nI saw that some components (like `Modal` or `Slideover`) have the \"trigger\" fully replaceable, meanwhile others like `Select` and `SelectMenu` cannot be fully replaced. Because of that, introducing another slot to replace the entire trigger would be nice imho. But I would define it as the default slot, not a named one (like `trigger` or something else) to remain consistent with the modal/slideover one.\nThe problem is that it would introduce a breaking change, so I don't know what is the way you want to proceed.\nWhat do you think about this?\nMentioning @sandros94 as I talked about this with him on Discord.\n\n### Additional context\n\nTo have a look on this, I did some changes in a branch in my fork: \u003Chttps://github.com/nuxt/ui/compare/v3...zAlweNy26:nuxt-ui:feat/select-trigger>",[2897,2898],{"name":2857,"color":2858},{"name":2885,"color":2886},4009,"Standardize trigger slot in components","2025-05-10T17:57:56Z","https://github.com/nuxt/ui/issues/4009",0.73783,{"description":2905,"labels":2906,"number":2912,"owner":2863,"repository":2864,"state":2889,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Description\n\nThe PinInput component expects the v-model to be a string array. However, when the type is set to number, I think it should support an array of numbers as values too.\n\n### Additional context\n\n_No response_",[2907,2908,2909],{"name":2857,"color":2858},{"name":2885,"color":2886},{"name":2910,"color":2911},"reka-ui","56d799",3751,"PinInput: v-model support Number-Array on type=number","2025-05-28T09:55:13Z","https://github.com/nuxt/ui/issues/3751",0.7455713,{"description":2918,"labels":2919,"number":2924,"owner":2863,"repository":2864,"state":2889,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Description\n\nIt is possible add an slot named `option-append` which will be after the menu content?\r\nFor example it will be useful to add an intersection observer when creating an infinite scroll select.\n\n### Additional context\n\n_No response_",[2920,2921,2923],{"name":2857,"color":2858},{"name":2922,"color":2861},"wontfix-v2",{"name":2885,"color":2886},1167,"`USelectMenu` option-append","2025-05-23T15:24:34Z","https://github.com/nuxt/ui/issues/1167",0.7463672,{"labels":2930,"number":2940,"owner":2863,"repository":2863,"state":2889,"title":2941,"updated_at":2942,"url":2943,"score":2944},[2931,2934,2937],{"name":2932,"color":2933},"3.x","29bc7f",{"name":2935,"color":2936},"components","05B979",{"name":2938,"color":2939},"🔨 p3-minor","FBCA04",13498,"Cant find components that have numbers in its name (only on dash case)","2023-01-19T16:58:01Z","https://github.com/nuxt/nuxt/issues/13498",0.7481032,{"labels":2946,"number":2953,"owner":2863,"repository":2863,"state":2889,"title":2954,"updated_at":2955,"url":2956,"score":2957},[2947,2950],{"name":2948,"color":2949},"pending triage","E99695",{"name":2951,"color":2952},"2.x","d4c5f9",3666,"\u003Cno-ssr> when check multiple default slot(no named) children , no tag, no name element counted Illegally.","2023-01-22T15:30:05Z","https://github.com/nuxt/nuxt/issues/3666",0.7504826,{"description":2959,"labels":2960,"number":2964,"owner":2863,"repository":2864,"state":2889,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Description\n\nI was looking to implement tooltip for NavigationMenu links as it was available in the DashboardSidebarLinks component in v2. But seems like the feature is no longer present in v3. \n\nhttps://ui2.nuxt.com/pro/components/dashboard-sidebar-links\n\nLet me know if there is still a simple way to implement tooltips specially in the collapsed Sidebar. I don't wanna go down with the slots approach. It looks dirty.\n\n\n\n### Additional context\n\nThis is what I have to do in order to get it to work. I believe this should be part of Nuxt UI already.\n\n``` js\n\u003CUNavigationMenu :collapsed=\"collapsed\" :items=\"links\" orientation=\"vertical\">\n \u003Ctemplate #item-leading=\"{ item }\">\n \u003CUTooltip :disabled=\"!collapsed\" :text=\"item.label\">\n \u003CUIcon\n :name=\"item.icon || ''\"\n class=\"text-dimmed group-hover:text-default size-5 shrink-0 transition-colors\"\n />\n \u003C/UTooltip>\n \u003C/template>\n\u003C/UNavigationMenu>\n```",[2961,2962,2963],{"name":2857,"color":2858},{"name":2885,"color":2886},{"name":2860,"color":2861},4050,"NavigationMenu has no way to apply a tooltip.","2025-05-10T11:36:41Z","https://github.com/nuxt/ui/issues/4050",0.75312316,{"description":2970,"labels":2971,"number":2973,"owner":2863,"repository":2863,"state":2889,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### 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```",[2972],{"name":2948,"color":2949},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.75833905,["Reactive",2979],{},["Set"],["ShallowReactive",2982],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fOwLi3wOx4FmpvkIRgildWuYHnKueS7H6Ea3CbMyUoWw":-1},"/nuxt/ui/4201"]