\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```",[2004,2005,2008],{"name":1985,"color":1986},{"name":2006,"color":2007},"v3","49DCB8",{"name":1991,"color":1992},3174,"`USlider`: Maximum recursive updates exceeded with more than 100 SliderThumbs","2025-01-25T10:51:38Z","https://github.com/nuxt/ui/issues/3174",0.7463536,{"description":2015,"labels":2016,"number":2019,"owner":1994,"repository":1995,"state":1996,"title":2020,"updated_at":2021,"url":2022,"score":2023},"### 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```",[2017,2018],{"name":1985,"color":1986},{"name":1991,"color":1992},2732,"Adding custom animations disable Nuxt UI ones","2024-11-22T15:38:35Z","https://github.com/nuxt/ui/issues/2732",0.7474164,{"description":2025,"labels":2026,"number":2031,"owner":1994,"repository":1995,"state":1996,"title":2032,"updated_at":2033,"url":2034,"score":2035},"### Description\n\nHi there,\n\nI'm really curious about how Nuxt UI is handling trailing slashes. In the Nuxt Content repo I can see they are using `ufo` to remove the trailing slashes, but in the Nuxt UI repo I can't find how you get rid of it. Even tho I know you can do these things on Vercel and Netlify, I'm curious how you handle it in Nuxt UI.\n\nIn my case, route.path is returning a path with a trailing slash and breaks my `queryCollection`...\n\n```vue\nconst { data: page } = await useAsyncData(\n `${route.path}/.navigation`,\n async () => {\n return await queryCollection('content').path(route.path).first();\n }\n);\n```",[2027,2030],{"name":2028,"color":2029},"question","d876e3",{"name":2006,"color":2007},3285,"Trailing slashes","2025-02-10T13:25:12Z","https://github.com/nuxt/ui/issues/3285",0.7506625,{"description":2037,"labels":2038,"number":2044,"owner":1994,"repository":1995,"state":1996,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### Description\n\nHi guys would be nice if there's a config value that sets `progress: false`, cause someone doesn't like it...\nit can be disabled on ui with display none, but a more correct approach would be in app config.\nThanks.\n\n### Additional context\n\n\u003Cimg width=\"382\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fc3885e7-fcfb-4950-a239-f0e4053de69d\" />",[2039,2042,2043],{"name":2040,"color":2041},"enhancement","a2eeef",{"name":2006,"color":2007},{"name":1991,"color":1992},3270,"[Feature request] Toast hide progress in app.config","2025-02-09T17:11:11Z","https://github.com/nuxt/ui/issues/3270",0.7545631,{"description":2050,"labels":2051,"number":2055,"owner":1994,"repository":1995,"state":1996,"title":2056,"updated_at":2057,"url":2058,"score":2059},"### Description\n\nWould be nice to add the possibility to set the position of the loading icon in the `UButton`. Now it replaces the leading icon, but when the trailing icon is used this leads to a behavior that in my opinion is undesidered in the majority of cases. \nThe idea would be a prop like that:\n```ts\nloading-position: 'leading' | 'trailing' | 'auto'\n```\nwhere `auto` should place the loader where the button icon is placed, leading otherwise.\n\n### Additional context\n\n_No response_",[2052,2053,2054],{"name":2040,"color":2041},{"name":2006,"color":2007},{"name":1991,"color":1992},3419,"Add `loading-position` to `UButton`","2025-03-02T12:16:32Z","https://github.com/nuxt/ui/issues/3419",0.75637764,{"description":2061,"labels":2062,"number":2068,"owner":1994,"repository":1995,"state":2069,"title":2070,"updated_at":2071,"url":2072,"score":2073},"### 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```",[2063,2064,2067],{"name":1985,"color":1986},{"name":2065,"color":2066},"duplicate","cfd3d7",{"name":2006,"color":2007},2991,"closed","ERROR [nuxt] [request error] [unhandled] [500] Unexpected token ';'","2024-12-28T17:43:05Z","https://github.com/nuxt/ui/issues/2991",0.7229389,{"description":2075,"labels":2076,"number":2077,"owner":1994,"repository":2078,"state":2069,"title":2079,"updated_at":2080,"url":2081,"score":2082},"### 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.7322357,{"description":2084,"labels":2085,"number":2088,"owner":1994,"repository":1995,"state":2069,"title":2089,"updated_at":2090,"url":2091,"score":2092},"### 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!",[2086,2087],{"name":2028,"color":2029},{"name":2006,"color":2007},3429,"How to get current modal/slideover instance?","2025-03-02T17:44:50Z","https://github.com/nuxt/ui/issues/3429",0.73684704,{"description":2094,"labels":2095,"number":2102,"owner":1994,"repository":1994,"state":2069,"title":2103,"updated_at":2104,"url":2105,"score":2106},"### Describe the feature\r\n\r\nYo. Um...\r\n\r\nDue to https://github.com/fi3ework/vite-plugin-checker/issues/306 and https://github.com/vuejs/language-tools/issues/4484, I suggest to replace vite-plugin-checker with some existing alternative if it exists, or develop something on Nuxt side.\r\n\r\nReasons:\r\n1. `vue-tsc` doesn't really want to update old versions, and even if they would, it won't last forever\r\n2. plugin checker did not receive update for months\r\n3. We are now blocked to upgrade to TS 5.5\r\n\r\nI know this sounds too hard, but decided to drop it here for consideration. Thanks!\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [X] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2096,2099],{"name":2097,"color":2098},"3.x","29bc7f",{"name":2100,"color":2101},"pending triage","E99695",27759,"Replace vite-plugin-checker with something else","2024-06-27T09:59:28Z","https://github.com/nuxt/nuxt/issues/27759",0.7434386,["Reactive",2108],{},["Set"],["ShallowReactive",2111],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"yQLvn5lBbc9WhLxMUKB9rsU-duE8qMuhjbuTKSpeaEg":-1},"/nuxt/ui/3245"]