\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```",[3045,3048,3049],{"name":3046,"color":3047},"bug","d73a4a",{"name":3023,"color":3024},{"name":3050,"color":3051},"triage","ffffff",3883,"[Carousel] Unable to differentiate item sizes","2025-04-14T08:19:21Z","https://github.com/nuxt/ui/issues/3883",0.75076187,{"description":3058,"labels":3059,"number":3066,"owner":3026,"repository":3026,"state":3028,"title":3067,"updated_at":3068,"url":3069,"score":3070},"### Describe the feature\n\nNuxt and its great, out-of-the-box DX are really enjoyable. However, I still prefer explicit imports over automatic ones, with exception for very well-known utilities and composables; such as the ones exposed by Vue's core.\n\nWhile configuring Nuxt to disable the auto-importing of almost everything, I noticed the API isn't really intuitive and could be improved. The problem is that in addition to having set `imports: { autoImport: false }`, we have to explicitly disable component auto-imports using `components: false` or `components: { dirs: [] }`. Even though everything is documented well, having to separately disable component auto-imports feels like an extra, not-really-obvious step. TBH, this isn't a big deal. However, things get worse when it comes to not just disabling auto-imports, but rather customizing it.\n\nI wanted to disable all auto-imports, and only have the presets of Vue & Vitest auto-imported. Unfortunately, the API isn't flexible enough to let me do something like this and call it a day:\n```ts\nimports: {\n autoImport: 'presets', // Boolean | 'presets'\n presets: ['vitest', /* Vue's preset seems to be included by default. */],\n},\n```\n\nSo, I came up with this solution by playing around with different `imports` hooks:\n```ts\n// Disable auto-importing custom components, composables, and utilities.\ncomponents: {\n dirs: [],\n},\nimports: {\n presets: ['vitest'],\n},\nhooks: {\n 'imports:extend': (imports) => {\n imports.length = 0;\n },\n}, \n```\n\n\u003Cbr />\nI'd really appreciate it if the team considers a more flexible and intuitive API.\n\n### Additional information\n\n- [ ] 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://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3060,3063],{"name":3061,"color":3062},"enhancement","8DEF37",{"name":3064,"color":3065},"pending triage","E99695",29275,"Better API for Auto Imports Customization","2024-10-08T08:40:01Z","https://github.com/nuxt/nuxt/issues/29275",0.7527337,{"description":3072,"labels":3073,"number":3079,"owner":3026,"repository":3027,"state":3080,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nI know you guys are working hard on V3, but I really like to see this feature still in V2. We all know that not everybody will move over to V3 right away.\n\nI have to set my `strategy` to `override`, because tailwind-merge doesn't know about my custom tailwind extends. This is quite a pain in the ass, since this is causing other issues as well. Take the [Pro LandingGird](https://ui.nuxt.com/pro/components/landing-grid) as example. Classes are added to the grid items to set the right cols. By doing this with `strategy` set to `override`, all other classes will be overridden.\n\nI saw some sort of solution in [#925 ](https://github.com/nuxt/ui/issues/925#issuecomment-1857910586), but that didn't work. It's also not documented and can't find it in the module either.\n\nI know have to create my own merge config, but that will not work for Nuxt UI.\n\n\n### Additional context\n\nYou may wonder why I need this. Thats because I'm also using Tailwind Fluid, and try to replicate a design library that uses different spacings etc.\n\n",[3074,3077],{"name":3075,"color":3076},"duplicate","cfd3d7",{"name":3061,"color":3078},"a2eeef",2893,"closed","Extend tailwind-merge configuration","2024-12-13T15:04:57Z","https://github.com/nuxt/ui/issues/2893",0.70359004,{"description":3086,"labels":3087,"number":3091,"owner":3026,"repository":3027,"state":3080,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Description\n\nI'm basically trying to display the week day full name in the Calendar header slot.\n\nInstead of having `S - M - T - W - T - F -S` as week day headers, I'd like to show `Sunday - Monday - Tuesday - Wednesday - ...`\n\nThe `#week-day` slot only provides the day's letter, so there's no way to reformat it.\n\n```\n\u003Ctemplate #week-day=\"item\">\n {{ item }}\n\u003C/template>\n```\n\nIt simply displays \n```\n{\n \"day\": \"M\"\n}\n```\nWhich is not super helpful\n\nWould it be possible to have, like, the weekday number (0 to 6) ? \n\nSuggestion:\n```\n{\n \"day\": \"M\",\n \"dayNumber\": \"1\",\n}\n```\n\n### Additional context\n\n_No response_",[3088,3089,3090],{"name":3061,"color":3078},{"name":3023,"color":3024},{"name":3050,"color":3051},3714,"Pass more complete data to Calendar week-day slots","2025-04-01T11:52:50Z","https://github.com/nuxt/ui/issues/3714",0.71880823,{"labels":3097,"number":3101,"owner":3026,"repository":3026,"state":3080,"title":3102,"updated_at":3103,"url":3104,"score":3105},[3098],{"name":3099,"color":3100},"2.x","d4c5f9",9641,"third party library, lazy loading, dev server complains, static build is fine","2023-01-18T15:28:51Z","https://github.com/nuxt/nuxt/issues/9641",0.73201925,{"description":3107,"labels":3108,"number":3111,"owner":3026,"repository":3027,"state":3080,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Environment\n\n```\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.39\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@https://pkg.pr.new/@nuxt/ui@1b3c919\n- Build Modules: -\n```\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3 latest commit\n\n### Description\n\nIn WebStorm interfaces cant be resolved as if they dont exist:\n\n\u003Cimg width=\"653\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/5d98f435-fc3d-4b9b-a83f-3f9e2380c12d\" />\n\nPossibly because types/index.d.ts exports vue files.\n\n\n### Additional context\n\nPossibly an issue with WebStorm because auto completion and type checking is working\n\n\u003Cimg width=\"492\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ba1dce0a-4dd8-4a03-9dcb-b3e045e0b9d7\" />",[3109,3110],{"name":3046,"color":3047},{"name":3023,"color":3024},2947,"v3: Interfaces cant be resolved in WebStorm","2025-04-16T13:18:50Z","https://github.com/nuxt/ui/issues/2947",0.7386999,{"description":3117,"labels":3118,"number":3120,"owner":3026,"repository":3026,"state":3080,"title":3121,"updated_at":3122,"url":3123,"score":3124},"There is the bug on `index.vue` in `Page` folder that we need to change from\r\n `import logo from '~components/logo.vue` \r\nto\r\n`import logo from '~/components/logo.vue`\r\n\r\nThis will make new people come in the first time struck in this point and some will drop-off which mean we lost number of user.\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/c1313\">#c1313\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3119],{"name":3099,"color":3100},1473,"Please fix the Starter Template for god sake ","2023-01-18T15:41:50Z","https://github.com/nuxt/nuxt/issues/1473",0.74451125,{"description":3126,"labels":3127,"number":3132,"owner":3026,"repository":3027,"state":3080,"title":3133,"updated_at":3134,"url":3135,"score":3136},"### Environment\n\nJust reporting an issue on the nuxt docs site. \n\n### Version\n\nhttps://ui.nuxt.com/components/button\n\n### Reproduction\n\nGo on to the nuxt website, this section in particular: \n\nhttps://ui.nuxt.com/components/button#icon\n \nand click 'trailing'. this should reproduce the issue. \n\n\n### Description\n\nWhen on the live docs site, on the button page, clicking 'trailing' docs this happens: \n\n\n\nThe page is: \n\nhttps://ui.nuxt.com/components/button#icon\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3128,3129],{"name":3046,"color":3047},{"name":3130,"color":3131},"documentation","0075ca",2425,"Bug on live docs site","2024-10-21T10:20:07Z","https://github.com/nuxt/ui/issues/2425",0.7463118,["Reactive",3138],{},["Set"],["ShallowReactive",3141],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fs0Entxx-iyAU1RffwowqPSNg5nOXOId1HeCvXT4Qfms":-1},"/nuxt/ui/2866"]