\n до \u003CUInputNumber v-model=\"bill.to\" :min=\"bill.from\" :max=\"10000\" :step=\"calcStep(bill.to)\" variant=\"soft\" class=\"max-w-32\" />\n \u003C/div>\n\u003C/template>\n```\n\n### Description\n\nhttps://skr.sh/vT5m5gCX1Bk\n\nThe value changes when clicking outside the field, regardless of the `step` and `modelValue` state. The `step` parameter is also calculated incorrectly at the threshold of 1000.",[1995,1998,2001],{"name":1996,"color":1997},"bug","d73a4a",{"name":1999,"color":2000},"v3","49DCB8",{"name":2002,"color":2003},"triage","ffffff",2859,"ui","UInputNumber changes value on blur when not asked for","2024-12-08T12:04:52Z","https://github.com/nuxt/ui/issues/2859",0.73199224,{"description":2011,"labels":2012,"number":2018,"owner":1985,"repository":2005,"state":1987,"title":2019,"updated_at":2020,"url":2021,"score":2022},"### Description\n\nI believe we should be able to collapse elements from left to right and invert them using the UCollapsible component.\n\n### Additional context\n\n_No response_",[2013,2016,2017],{"name":2014,"color":2015},"enhancement","a2eeef",{"name":1999,"color":2000},{"name":2002,"color":2003},3202,"Horizontal collapse support","2025-02-12T21:08:31Z","https://github.com/nuxt/ui/issues/3202",0.7376318,{"description":2024,"labels":2025,"number":2030,"owner":1985,"repository":2005,"state":1987,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Description\n\nIt doesn't seem to apply using\n\ntailwind.config.js\n`export default {\n important: true \n}\n`",[2026,2029],{"name":2027,"color":2028},"question","d876e3",{"name":1999,"color":2000},3528,"Is there a way to apply Tailwind Important Mode through Nuxt UI?","2025-03-14T22:49:40Z","https://github.com/nuxt/ui/issues/3528",0.74081874,{"description":2036,"labels":2037,"number":2040,"owner":1985,"repository":2005,"state":2041,"title":2042,"updated_at":2043,"url":2044,"score":2045},"### Description\n\nSorry if this information is available, but I could not find an answer in the docs or by searching.\n\nI was hoping to be able to let users select a theme that also included changing component defaults. \nUsing Vue/Vite (not Nuxt), is it possible to modify the full global configuration (`ui` object) at runtime (instead of having to pass props to or wrap each component)? \n\nI'm not 100% averse to a bit of monkey patching on my current project, but a supported solution would obviously be much much better.\n\nIf this is not currently possible, please consider this a suggestion, for example via an `ui` prop on the `App` component or a `useNuxtUi` composable.\n",[2038,2039],{"name":2027,"color":2028},{"name":1999,"color":2000},3290,"closed","Runtime configuration change?","2025-04-12T15:53:05Z","https://github.com/nuxt/ui/issues/3290",0.6856918,{"description":2047,"labels":2048,"number":2054,"owner":1985,"repository":2005,"state":2041,"title":2055,"updated_at":2056,"url":2057,"score":2058},"### Environment\n\n System:\n OS: Linux 6.5 Ubuntu 23.10 23.10 (Mantic Minotaur)\n CPU: (8) x64 11th Gen Intel(R) Core(TM) i5-1135G7 @ 2.40GHz\n Memory: 44.48 GB / 62.57 GB\n Container: Yes\n Shell: 5.9 - /usr/bin/zsh\n Browsers:\n Chrome: 126.0.6478.126\n\n### Version\n\nv3.0.0-alpha.6\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/select-menu\n\n### Description\n\n1. open docs\n2. open any select menu\n3. select any option\n4. tab to next field\n5. tab index is reset\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2049,2050,2051],{"name":1996,"color":1997},{"name":1999,"color":2000},{"name":2052,"color":2053},"reka-ui","56d799",2350,"[SelectMenu] Broken focus/tab index after selecting","2024-12-03T15:11:34Z","https://github.com/nuxt/ui/issues/2350",0.71804595,{"description":2060,"labels":2061,"number":2067,"owner":1985,"repository":1986,"state":2041,"title":2068,"updated_at":2069,"url":2070,"score":2071},"When we have a long tree in `content/` for example, the user should not have to scroll to access the search.",[2062,2064],{"name":2014,"color":2063},"1ad6ff",{"name":2065,"color":2066},"responsive","1cd1c6",694,"[Project] Branches and Files search in navbar dialog should be fixed to bottom","2023-02-15T12:32:44Z","https://github.com/nuxt/nuxt.com/issues/694",0.72721004,{"description":2073,"labels":2074,"number":2067,"owner":1985,"repository":2078,"state":2041,"title":2079,"updated_at":2080,"url":2081,"score":2071},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, runtimeConfig\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-cr9qis-awh721?file=composables%2Ftests%2FuseTest.test.ts\n\n### Describe the bug\n\n`Cannot mock \"#app/nuxt\" because it is already loaded` error when using `mockNuxtImport` or `mountSuspended` in tests in Nuxt environment.\r\nTry to run `npm run test`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2075],{"name":2076,"color":2077},"pending triage","5D08F5","test-utils","`Cannot mock \"#app/nuxt\" because it is already loaded` error when running tests","2024-01-08T19:20:49Z","https://github.com/nuxt/test-utils/issues/694",{"description":2083,"labels":2084,"number":2085,"owner":1985,"repository":2078,"state":2041,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### Environment\n\n- Operating System: `Windows_NT`\r\n- Node Version: `v18.15.0`\r\n- Nuxt Version: `3.3.3`\r\n- Nitro Version: `2.3.2`\r\n- Package Manager: `yarn@1.23.0-20200615.1913`\r\n- Builder: `vite`\n\n### Reproduction\n\nFile: `/tests/NoteTree.spec.ts`\r\n```typescript\r\nimport { $fetch } from '@nuxt/test-utils'\r\n\r\ndescribe('test', () => {\r\n it('test index', async () => {\r\n console.log('Begin test index')\r\n expect(await $fetch('/')).toMatch('Hello Nuxt!')\r\n })\r\n})\r\n```\r\nFile: `App.vue`\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n Hello Nuxt!\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\nFile: `package.json`\r\n```json\r\n{\r\n \"name\": \"nuxt-app\",\r\n \"private\": true,\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\",\r\n \"test\": \"nuxt test --coverage\",\r\n \"testOnce\": \"vitest run\",\r\n \"testCoverage\": \"vitest run --coverage\"\r\n },\r\n \"dependencies\": {\r\n \"@css-render/vue3-ssr\": \"^0.15.12\",\r\n \"@vicons/ionicons5\": \"^0.12.0\",\r\n \"cheerio\": \"^1.0.0-rc.12\",\r\n \"fs\": \"0.0.2\",\r\n \"highlight.js\": \"^11.7.0\",\r\n \"marked\": \"^2.0.0\",\r\n \"path\": \"^0.12.7\",\r\n \"prismjs\": \"^1.29.0\"\r\n },\r\n \"devDependencies\": {\r\n \"@nuxt/test-utils\": \"3.3.3\",\r\n \"@types/node\": \"^18.15.11\",\r\n \"@types/prismjs\": \"^1.26.0\",\r\n \"@vitejs/plugin-vue\": \"^4.1.0\",\r\n \"@vitest/coverage-c8\": \"^0.29.8\",\r\n \"@vue/test-utils\": \"^2.3.2\",\r\n \"eslint-plugin-vitest\": \"^0.0.57\",\r\n \"jsdom\": \"^21.1.1\",\r\n \"naive-ui\": \"^2.34.3\",\r\n \"nuxt\": \"3.3.3\",\r\n \"sass\": \"^1.60.0\",\r\n \"vfonts\": \"^0.0.3\",\r\n \"vite-plugin-prismjs\": \"^0.0.8\",\r\n \"vitest\": \"^0.29.8\"\r\n }\r\n}\r\n```\r\n\r\nUsage: Terminal run: `nuxt test`\r\n\n\n### Describe the bug\n\n**Bug preview:**\r\n\r\n1. Execution time too long\r\n2. Excessive duplicate content output from the console\r\n3. Unable to use vitest's coverage command\r\n\r\n\r\n**Bug description:**\r\n**1. Execution time too long**\r\nUsually, a simple project only tests whether a page contains a certain string, so it shouldn't take so long. I hope to optimize the test execution logic, such as in the CI/CD process where Yarn install and Yarn build are usually done in the previous steps. I hope to directly conduct real nuxt tests after this, without the need for repeated compilation\r\n\r\n**2. Excessive duplicate content output from the console**\r\nThe Vue3 project can be tested using the `vitest run` command, and the console is very concise during the testing process. Repeated output will only output one line, but using the `nuxt test` command will output a lot of repetitive content on the console\r\n\r\n**3. Unable to use vitest's coverage command**\r\nThe coverage command of vitest cannot be used. Vue3 projects can use the `vitest run --coverage` command to calculate and output coverage, but using the `nuxt test` command and the `--coverage` command also cannot output coverage\r\n\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[],388,"nuxt3 use vitest Execution time too long and Unable to use vitest's coverage command","2023-12-02T00:13:09Z","https://github.com/nuxt/test-utils/issues/388",0.7315779,{"description":2091,"labels":2092,"number":2097,"owner":1985,"repository":1986,"state":2041,"title":2098,"updated_at":2099,"url":2100,"score":2101},"due to the listing order being a big influence in traffic for the agency page, would it be possible for the agencies to be presented in a random order when accessing the [Agencies page](https://nuxt.com/support/agencies) ?",[2093,2094],{"name":2014,"color":2063},{"name":2095,"color":2096},"marketing","f5c828",1048,"[Agencies] Present agencies in a random order","2023-10-10T14:45:03Z","https://github.com/nuxt/nuxt.com/issues/1048",0.7338703,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"fr6z9XHjyTz50IkRWMLTeZ60noJ8FmfdVCk_mD-IuMs":-1},"/nuxt/ui/3510"]