\n\u003C/template>\n```\n\n### Description\n\nWhen using the `USlider` component to render more than 100 `SliderThumbs`, the following error occurs:\n\n```\nUncaught (in promise) Maximum recursive updates exceeded in component \u003CSliderThumb>.\n```\n\nThis error seems to happen due to recursive reactive updates when the number of slider thumbs exceeds a certain limit.\n\n**Steps to Reproduce:**\n\n1. Create a Nuxt 3 project.\n2. Install Nuxt UI 3.\n3. Add the following code to a component:\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport { range } from 'lodash';\nimport { ref } from 'vue';\n\nconst value = ref(range(100)); // 100 sliders\n\u003C/script>\n\n\u003Ctemplate>\n \u003CUSlider v-model=\"value\" />\n\u003C/template>\n```\n\n4. Run the project and attempt to render the component.\n\n**Expected Result:**\nThe `USlider` component should render more than 100 `SliderThumbs` without any errors.\n\n**Actual Result:**\nThe following error is shown in the browser console, and the application fails to work properly:\n\n```\nUncaught (in promise) Maximum recursive updates exceeded in component \u003CSliderThumb>.\n```\n\n### Additional context\n\n- This issue seems to be caused by recursive reactive updates within the `USlider` component.\n- No documented limitations regarding the number of `SliderThumbs` were found in the Nuxt UI 3 documentation.\n\n### Logs\n\n```shell-script\n\n```",[2865,2868,2871],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"v3","49DCB8",{"name":2872,"color":2873},"triage","ffffff",3174,"nuxt","ui","open","`USlider`: Maximum recursive updates exceeded with more than 100 SliderThumbs","2025-01-25T10:51:38Z","https://github.com/nuxt/ui/issues/3174",0.73793185,{"description":2883,"labels":2884,"number":2890,"owner":2875,"repository":2876,"state":2877,"title":2891,"updated_at":2892,"url":2893,"score":2894},"### 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_",[2885,2886,2889],{"name":2866,"color":2867},{"name":2887,"color":2888},"pro","5BD3CB",{"name":2872,"color":2873},2057,"LandingFAQ component in Pro ignores the \"slot\" property of an item","2024-09-10T20:23:57Z","https://github.com/nuxt/ui/issues/2057",0.73830456,{"description":2896,"labels":2897,"number":2900,"owner":2875,"repository":2876,"state":2877,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.11.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.6\n- Package Manager: pnpm@9.5.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@8.0.0, @nuxt/ui@2.16.0, @nuxtjs/tailwindcss@6.12.0, @pinia/nuxt@0.5.1, @nuxtjs/google-fonts@3.2.0, @nuxtjs/eslint-module@4.1.0, @nuxt/test-utils/module@3.13.1\n- Build Modules: -\n------------------------------\n\n\n\n### Version\n\nv.2.15.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-1f7znf?file=app.vue,nuxt.config.ts\n\n### Description\n\nWhen providing custom animations through tailwindcss config, some Nuxt UI animations stop working. I have provided an example of a `UButton` with `loading` set in the repro link above.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2898,2899],{"name":2866,"color":2867},{"name":2872,"color":2873},2732,"Adding custom animations disable Nuxt UI ones","2024-11-22T15:38:35Z","https://github.com/nuxt/ui/issues/2732",0.76410407,{"description":2906,"labels":2907,"number":2914,"owner":2875,"repository":2915,"state":2877,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Describe the feature\n\nI have a project where I've written multiple test files, each with their own `setup()` inside the top `describe()`\r\n\r\n```ts\r\ndescribe('/api/pen', async () => {\r\n await setup(setupConfig())\r\n...\r\n```\r\n\r\nWhen I run these tests it creates a nuxt instance for each test file, demonstrated here: https://github.com/fumeapp/bio/actions/runs/10505024117/job/29101731333#step:12:48\r\n\r\nI'm not sure if I have this setup incorrectly, or maybe if there was a way to have all test files share the same nuxt instance?\r\n\r\nP.S. I am working on a potential GH action version that will run nuxt in the background and allow a possible setup({host: ...}) version, if i get this working i'll share it.\n\n### Additional information\n\n- [X] 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).",[2908,2911],{"name":2909,"color":2910},"enhancement","a2eeef",{"name":2912,"color":2913},"pending triage","5D08F5",923,"test-utils","Ability to avoid a new nuxt instance for each test file","2024-08-22T09:25:17Z","https://github.com/nuxt/test-utils/issues/923",0.76683617,{"description":2921,"labels":2922,"number":2928,"owner":2875,"repository":2876,"state":2929,"title":2930,"updated_at":2931,"url":2932,"score":2933},"### Environment\n\n```\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/content@2.13.4, @nuxt/eslint@0.7.4, @nuxt/fonts@0.10.3, @nuxt/image@1.8.1, @nuxt/ui@2.20.0, @nuxthq/studio@2.2.1, @vueuse/nuxt@12.2.0, nuxt-og-image@4.0.2\n- Build Modules: -\n------------------------------\n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.15.0\n\n\n### Description\n\nHi, what did i do wrong ?\n\n\n\n```\nuser ~/d/nuxt> npx nuxi init -t github:nuxt-ui-pro/saas my-saas\n\n\n✔ Which package manager would you like to use?\nnpm\n◐ Installing dependencies... 2:59:28 PM\nnpm warn deprecated inflight@1.0.6: This module is not supported, and leaks memory. Do not use it. Check out lru-cache if you want a good and tested way to coalesce async requests by a key value, which is much more comprehensive and powerful.\nnpm warn deprecated glob@7.2.3: Glob versions prior to v9 are no longer supported\n\n> postinstall\n> nuxt prepare\n\nℹ Using default Tailwind CSS file nuxt:tailwindcss 3:00:48 PM\nℹ Nuxt Icon server bundle mode is set to local 3:00:49 PM\n[3:00:50 PM] ✔ Nuxt Icon discovered local-installed 3 collections: heroicons, simple-icons, vscode-icons\nℹ Running with compatibility version 4 3:00:50 PM\n✔ Types generated in .nuxt 3:00:50 PM\n\nadded 1277 packages, and audited 1279 packages in 1m\n\n347 packages are looking for funding\n run `npm fund` for details\n\nfound 0 vulnerabilities\n✔ Installation completed. 3:00:50 PM\n\n✔ Initialize git repository?\nYes\nℹ Initializing git repository... 3:26:30 PM\n\nInitialized empty Git repository in /Users/amine-smahi/dev/nuxt/my-saas/.git/\n 3:26:30 PM\n✨ Nuxt project has been created with the nuxt-ui-pro-saas template. Next steps:\n › cd my-saas 3:26:30 PM\n › Start development server with npm run dev 3:26:30 PM\nuser ~/d/nuxt> cd my-saas/\nuser ~/d/n/my-saas (main)> npm run dev\n\n> dev\n> nuxt dev\n\nNuxt 3.15.0 with Nitro 2.10.4 3:26:37 PM\n 3:26:37 PM\n ➜ Local: http://localhost:3000/\n ➜ Network: use --host to expose\n\n\n ╭──────────────────────────────────────────────────────────────────────────────────────────────────────╮\n │ │\n │ Nuxt UI Pro │\n │ │\n │ Missing NUXT_UI_PRO_LICENSE env variable, please add it to your .env. │\n │ │\n │ Purchase Nuxt UI Pro at https://ui.nuxt.com/pro/pricing to build your app in production. │\n │ │\n ╰──────────────────────────────────────────────────────────────────────────────────────────────────────╯\n\nℹ Using default Tailwind CSS file nuxt:tailwindcss 3:26:38 PM\n ➜ DevTools: press Shift + Option + D in the browser (v1.7.0) 3:26:39 PM\n\nℹ Nuxt Icon server bundle mode is set to local 3:26:40 PM\n[3:26:41 PM] ✔ Nuxt Icon discovered local-installed 3 collections: heroicons, simple-icons, vscode-icons\nℹ Running with compatibility version 4 3:26:41 PM\n[nuxt:tailwindcss 3:26:41 PM] ℹ Tailwind Viewer: http://localhost:3000/_tailwind/\n✔ Vite client built in 19ms 3:26:42 PM\n✔ Vite server built in 94ms 3:26:42 PM\n✔ Nuxt Nitro server built in 1353 ms nitro 3:26:44 PM\nℹ Vite client warmed up in 372ms 3:26:45 PM\nℹ Vite server warmed up in 3607ms 3:26:48 PM\n\n ERROR [nuxt] [request error] [unhandled] [500] Unexpected token ';'\n\n\n\n ERROR [nuxt] [request error] [unhandled] [500] Unexpected token ';'\n\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2923,2924,2927],{"name":2866,"color":2867},{"name":2925,"color":2926},"duplicate","cfd3d7",{"name":2869,"color":2870},2991,"closed","ERROR [nuxt] [request error] [unhandled] [500] Unexpected token ';'","2024-12-28T17:43:05Z","https://github.com/nuxt/ui/issues/2991",0.72287196,{"description":2935,"labels":2936,"number":2941,"owner":2875,"repository":2876,"state":2929,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Description\n\nMight have missed this in the beta 2 docs, but curious how we're supposed to close the current `Modal` or `Slideover` instance from within the component using the new `useOverlay` composable. I see a few references to `useOverlayInstance` in other issue but that composable doesn't seem to be available in the current beta.\n\nThanks!",[2937,2940],{"name":2938,"color":2939},"question","d876e3",{"name":2869,"color":2870},3429,"How to get current modal/slideover instance?","2025-03-02T17:44:50Z","https://github.com/nuxt/ui/issues/3429",0.7339839,{"description":2947,"labels":2948,"number":2954,"owner":2875,"repository":2876,"state":2929,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### 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?",[2949,2950,2951],{"name":2938,"color":2939},{"name":2869,"color":2870},{"name":2952,"color":2953},"vue","42b883",3001,"How likely is it that we'll see a routerless version?","2025-04-14T08:47:28Z","https://github.com/nuxt/ui/issues/3001",0.7473891,{"description":2960,"labels":2961,"number":2964,"owner":2875,"repository":2876,"state":2929,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Description\n\nI think the docs havent been updated or this . The docs say to do this to theme components in nuxt config \n\n\n\nbut i get this i think this has been moved\n\n\ni am on version\n\n`3.0.0-alpha.12`",[2962,2963],{"name":2938,"color":2939},{"name":2869,"color":2870},3208,"How To Customize Nuxt Components","2025-01-30T18:42:31Z","https://github.com/nuxt/ui/issues/3208",0.7476908,{"description":2970,"labels":2971,"number":2972,"owner":2875,"repository":2973,"state":2929,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### 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.74876654,{"description":2979,"labels":2980,"number":2987,"owner":2875,"repository":2876,"state":2929,"title":2988,"updated_at":2989,"url":2990,"score":2991},"### 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```",[2981,2982,2983,2986],{"name":2866,"color":2867},{"name":2869,"color":2870},{"name":2984,"color":2985},"typescript","3A629E",{"name":2872,"color":2873},3670,"v-model typescript error when using label-key InputMenu/SelectMenu","2025-03-24T20:38:15Z","https://github.com/nuxt/ui/issues/3670",0.7557745,["Reactive",2993],{},["Set"],["ShallowReactive",2996],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fyQLvn5lBbc9WhLxMUKB9rsU-duE8qMuhjbuTKSpeaEg":-1},"/nuxt/ui/3245"]