\n \u003C/UCarousel>\n\u003C/template>\n\n### Description\n\nSimulate the behavior of https://m3.material.io/components/carousel/overview, Carousel will repeatedly calculate is-snapped in an infinite loop\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2913,2916,2919],{"name":2914,"color":2915},"bug","d73a4a",{"name":2917,"color":2918},"v3","49DCB8",{"name":2920,"color":2921},"triage","ffffff",3883,"ui","[Carousel] Unable to differentiate item sizes","2025-04-14T08:19:21Z","https://github.com/nuxt/ui/issues/3883",0.73690915,{"description":2929,"labels":2930,"number":2931,"owner":2903,"repository":2932,"state":2905,"title":2933,"updated_at":2934,"url":2935,"score":2936},"It would be nice if you could alias and entire collection instead of just an icon.\n\nRight now I do it this way.\n```ts\nconst createIconAliases = (newPrefix: string, iconifyJson: IconifyJSON) => {\n const exisitngPrefix = iconifyJson.prefix;\n const icons = Object.keys(iconifyJson.icons);\n\n return icons.reduce(\n (object, value) => {\n object[`${newPrefix}:${value}`] = `${exisitngPrefix}:${value}`;\n return object;\n },\n {} as Record\u003Cstring, string>,\n );\n};\n```",[],362,"icon","[feature request] Allow aliasing entire collection","2025-02-21T20:10:51Z","https://github.com/nuxt/icon/issues/362",0.74573374,{"description":2938,"labels":2939,"number":2947,"owner":2903,"repository":2923,"state":2948,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### Description\n\nI really love all the work that went into this, but it's currently connected to vue-router for `Link` and `Pagination` components. I would love to see these become optional dependencies so it can be used with projects that do not use `vue-router`.\n\nMaybe there is some way to stub out the link components to enable support for Inertia \\ default HTML?",[2940,2943,2944],{"name":2941,"color":2942},"question","d876e3",{"name":2917,"color":2918},{"name":2945,"color":2946},"vue","42b883",3001,"closed","How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.7064072,{"description":2954,"labels":2955,"number":2956,"owner":2903,"repository":2957,"state":2948,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.16.0`\n- CLI Version: `3.22.5`\n- Nitro Version: `2.11.5`\n- Package Manager: `bun@1.2.4`\n- Builder: `-`\n- User Config: `runtimeConfig`, `modules`, `app`, `site`, `sitemap`, `robots`, `css`, `icon`, `image`, `ui`, `devtools`, `future`, `unhead`, `compatibilityDate`\n- Runtime Modules: `@nuxt/ui@3.0.0-beta.3`, `@pinia/nuxt@0.10.1`, `@nuxt/scripts@0.10.5`, `@nuxt/image@1.9.0`, `@nuxtjs/seo@2.2.0`\n- Build Modules: `-`\n\n### Reproduction\n\nnda\n\n### Describe the bug\n\nnr dev\n$ nuxt dev\nNuxt 3.16.0 with Nitro 2.11.5 nuxi 8:23:08 PM\n 8:23:08 PM\n ➜ Local: http://localhost:3003/\n ➜ Network: use --host to expose\n\n ➜ DevTools: press Shift + Option + D in the browser (v2.2.1) 8:23:10 PM\n\n\n✔ Nuxt Icon loaded local collection elfi with 70 icons 8:23:10 PM\nℹ Running with compatibility version 4 nuxt 8:23:10 PM\n✔ Vite client built in 190ms 8:23:11 PM\n✔ Vite server built in 528ms 8:23:12 PM\n\n[nitro 8:23:14 PM] ERROR Error: Could not load /\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs (imported by node_modules/nuxt-og-image/dist/runtime/server/og-image/satori/instances.js): ENOENT: no such file or directory, open '/\u003Cmy-path>/node_modules/unenv/dist/runtime/runtime/mock/empty.mjs'\n\n\nundefined\n\n### Additional context\n\nUpgraded by \"nuxi upgrade -f\" from 3.15.4 and couldn't able to start properly with provided error.\nTried with unhead flag in nuxt.config - same error\n```\nunhead: {\n legacy: true,\n }\n```\n\n### Logs\n\n```shell-script\n\n```",[],414,"scripts","Nuxt 3.16.0 won't start properly nor dev nor build","2025-03-07T18:58:03Z","https://github.com/nuxt/scripts/issues/414",0.71654576,{"description":2963,"labels":2964,"number":2969,"owner":2903,"repository":2923,"state":2948,"title":2970,"updated_at":2971,"url":2972,"score":2973},"### Description\n\nHey!\n\nIt would be nice to have the primary/secondary/neutral/etc colours defined in `app.config.ts` directly as tailwind variables (ex: text-primary-500)\n\nRight now we have to define the colours both in `app.config.ts` and `tailwind.config.js` to be able to do that. (the new `main.css` would require to create a variable for each sub-colour manually so not worth using it) \n\nFor `neutral`, since it's a tailwind colour, it could be named `text-neutr-500`\nOr maybe name all colours with something like `text-Uneutral-500`\n\n\n### Additional context\n\n_No response_",[2965,2968],{"name":2966,"color":2967},"enhancement","a2eeef",{"name":2917,"color":2918},2948,"Add theme colors as tailwind variables","2025-02-06T16:29:04Z","https://github.com/nuxt/ui/issues/2948",0.7227849,{"description":2975,"labels":2976,"number":2981,"owner":2903,"repository":2923,"state":2948,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\n2.18.6\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/aloulouamine/nuxt-ui-select-menu-issue\n\n### Description\n\nSelectMenu with paginated search has an issue with default count placeholder.\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2977,2978],{"name":2914,"color":2915},{"name":2979,"color":2980},"duplicate","cfd3d7",2313,"SelectMenu paginated search count issue","2024-10-06T17:49:40Z","https://github.com/nuxt/ui/issues/2313",0.72555685,{"description":2987,"labels":2988,"number":2995,"owner":2903,"repository":2923,"state":2948,"title":2996,"updated_at":2997,"url":2998,"score":2999},"### Environment\n\n- Operating System: Linux\n- Node Version: v20.18.1\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: yarn@1.22.22\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, modules\n- Runtime Modules: @nuxt/ui@3.0.1, @pinia/nuxt@0.10.1, pinia-plugin-persistedstate/nuxt@4.2.0\n- Build Modules: -\n- Typescript: 5.8.2\n- Vue-tsc: 2.2.8\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.1\n\n### Reproduction\n\n```\n// will trigger typescript error on v-model\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n label-key=\"email\"\n/>\n// will trigger typescript error on v-model\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n label-key=\"email\"\n :value-key=\"undefined\"\n/>\n// will work but i need to handle label display manually using slot\n\u003CUSelectMenu\n v-model=\"memberForm.user\"\n :items=\"addableUsers\"\n/>\n```\n\n### Description\n\nI'm currently migrate my project to NuxtUi V3 and I have some issues with `\u003CUInputMenu />` and `\u003CUSelectMenu />`. On my selects I want to retrieve the full object selected so I don't set `value-key` but for display purpose I use the `label-key` props, however when I do this I get this typescript error on the `v-model` :\n```\nUnable to assign type 'User | undefined' to type 'string | undefined'.\nUnable to assign type 'User' to type 'string'. ts-plugin(2322)\n```\nAfter some research, I think the `label-key` alter the `value-key` type and that's what triggers the error.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2989,2990,2991,2994],{"name":2914,"color":2915},{"name":2917,"color":2918},{"name":2992,"color":2993},"typescript","3A629E",{"name":2920,"color":2921},3670,"v-model typescript error when using label-key InputMenu/SelectMenu","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3670",0.73013926,{"description":3001,"labels":3002,"number":3005,"owner":2903,"repository":2923,"state":2948,"title":3006,"updated_at":3007,"url":3008,"score":3009},"### Description\n\nThe Nuxt UI v2 dropdown has the option to open on hover or click. In v3 the only option available is click. \n\n\n\n### Additional context\n\n_No response_",[3003,3004],{"name":2966,"color":2967},{"name":2917,"color":2918},3322,"[DropdownMenu] (v3) missing mode prop for hover/click","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3322",0.7312917,{"description":3011,"labels":3012,"number":3015,"owner":2903,"repository":2923,"state":2948,"title":3016,"updated_at":3017,"url":3018,"score":3019},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\n[CommandPalette](https://ui3.nuxt.dev/components/command-palette) is great but I wish it could display only an input by default and then open the content in a popper when clicking in the input. I think this is currently not possible but a very common use case. \n\nThis is what I would like to archive, screenshots from Shopify:\n\n\n\n\n\n\n\n### Additional context\n\n_No response_",[3013,3014],{"name":2966,"color":2967},{"name":2917,"color":2918},2832,"v3 CommandPalette: Open only content within popper","2024-12-05T13:24:12Z","https://github.com/nuxt/ui/issues/2832",0.73377657,["Reactive",3021],{},["Set"],["ShallowReactive",3024],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkXX6SZML8IcWJdy8oOGpVw_EDa40nD5nVAH9mcuATPc":-1},"/nuxt/ui/3429"]