\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```",[2026,2029,2030],{"name":2027,"color":2028},"bug","d73a4a",{"name":1988,"color":1989},{"name":2031,"color":2032},"triage","ffffff",3174,"`USlider`: Maximum recursive updates exceeded with more than 100 SliderThumbs","2025-01-25T10:51:38Z","https://github.com/nuxt/ui/issues/3174",0.8257468,{"description":2039,"labels":2040,"number":2044,"owner":1991,"repository":2045,"state":1993,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-5sxamx?file=components%2FMyComponent.nuxt.spec.ts\n\n### Describe the bug\n\nOne convenient method for verifying that a component has emitted the expected events is to pass a prop with \"onX\" that contain a mocked function:\r\n\r\n```ts\r\nconst onTest = vi.fn()\r\nrender(MyComponent, {\r\n props: { title: 'Test title', onTest},\r\n});\r\nexpect(onTest).toHaveBeenCalled(); ✅\r\n```\r\n\r\nWhile this works fine with the testing library `render` helper, Nuxt's `renderSuspended` fails to pass the event handler to the component:\r\n\r\n```ts\r\nawait renderSuspended(MyComponent, {\r\n props: { title: 'Test title', onTest },\r\n});\r\nexpect(onTest).toHaveBeenCalled(); ❌\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2041],{"name":2042,"color":2043},"pending triage","5D08F5",731,"test-utils","`renderSuspended` does not handle `onEvent` notation","2024-05-01T20:36:22Z","https://github.com/nuxt/test-utils/issues/731",0.8261644,{"description":2051,"labels":2052,"number":2054,"owner":1991,"repository":1992,"state":2055,"title":2056,"updated_at":2057,"url":2058,"score":2059},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.15.1\n- Nuxt Version: 3.13.2\n- CLI Version: 3.14.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.12.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Version\n\nv2.18.7\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-3rqgxj?file=app.vue\n\n### Description\n\nThe `UTable` component doesn't have a border\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2053],{"name":2027,"color":2028},2438,"closed","No border in `UTable` component","2024-10-23T08:31:25Z","https://github.com/nuxt/ui/issues/2438",0.74905974,{"description":2061,"labels":2062,"number":2064,"owner":1991,"repository":2045,"state":2055,"title":2065,"updated_at":2066,"url":2067,"score":2068},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v21.5.0`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.4`\r\n- Builder: `-`\r\n- User Config: `alias`, `app`, `devtools`, `eslint`, `i18n`, `imports`, `modules`, `nitro`, `runtimeConfig`, `ssr`, `testUtils`, `typescript`, `vite`, `vuetify`\r\n- Runtime Modules: `@pinia-plugin-persistedstate/nuxt@1.2.0`, `@pinia/nuxt@0.5.1`, `@nuxtjs/i18n@8.0.0`, `@nuxtjs/eslint-module@4.1.0`, `nuxt-typed-router@3.5.0`, `@nuxt/test-utils/module@3.9.0`, `vuetify-nuxt-module@0.7.3`, `nuxt-lodash@2.5.3`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-cyqbu8\n\n### Describe the bug\n\nAfter upgrading to 3.9.0, I am getting errors when running tests due to missing identifiers in the nuxt package. Reproduction shows error from my middleware test but I get similar errors when running component tests but this time the error is \"Error: Missing \"#build/paths.mjs\" specifier in \"nuxt\" package\"\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2063],{"name":2042,"color":2043},679,"Error running test after upgrade to 3.9.0","2024-01-28T11:25:59Z","https://github.com/nuxt/test-utils/issues/679",0.7934339,{"description":2070,"labels":2071,"number":2074,"owner":1991,"repository":2075,"state":2055,"title":2076,"updated_at":2077,"url":2078,"score":2079},"Noticed that the animation on the timeline does not work properly on mobile (only first item appears) AND we have an issue for the image when navigating on client-side (at least on Safari):\n\nhttps://user-images.githubusercontent.com/904724/180595606-b112686f-b2ce-4686-8be6-0620ab31dac5.MOV\n\nAlso notice the layout shift on reload, might be due to a lack of height specified on images.",[2072],{"name":2027,"color":2073},"ff281a",831,"nuxt.com","[Community] About page timeline mobile","2023-02-15T12:31:02Z","https://github.com/nuxt/nuxt.com/issues/831",0.8104763,{"description":2081,"labels":2082,"number":2085,"owner":1991,"repository":2075,"state":2055,"title":2086,"updated_at":2087,"url":2088,"score":2089},"- [x] `/modules`\n- [x] `/community/repositories`\n- [x] `/community/nuxters`\n- [x] `/community/partners`\n- [x] `/resources/showcases`",[2083],{"name":2002,"color":2084},"1ad6ff",612,"[Responsive] Aside filters selects on mobile should be full width","2023-02-15T12:32:38Z","https://github.com/nuxt/nuxt.com/issues/612",0.8114725,{"description":2091,"labels":2092,"number":2085,"owner":1991,"repository":2045,"state":2055,"title":2096,"updated_at":2097,"url":2098,"score":2089},"## Description\r\nTrying to follow the official documentation, I am adding a `test` config section in the `defineVitestConfig` and receive the following error:\r\n#### Object literal may only specify known properties, and 'test' does not exist in type 'InlineConfig'.ts(2353)\r\n",[2093],{"name":2094,"color":2095},"vitest-environment","b60205","`test` config not found in nuxt-vitest","2023-12-02T17:18:50Z","https://github.com/nuxt/test-utils/issues/612",["Reactive",2100],{},["Set"],["ShallowReactive",2103],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"fWvbhFd6tpPRntWO-U1w4zOipNyaT8hF3qE-FkiMJrY":-1},"/nuxt/ui/2470"]