\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.",[2025,2028,2029],{"name":2026,"color":2027},"bug","d73a4a",{"name":2011,"color":2012},{"name":2014,"color":2015},2859,"UInputNumber changes value on blur when not asked for","2024-12-08T12:04:52Z","https://github.com/nuxt/ui/issues/2859",0.7552624,{"description":2036,"labels":2037,"number":2039,"owner":1985,"repository":1999,"state":1987,"title":2040,"updated_at":2041,"url":2042,"score":2043},"### Environment\n\nWorking directory: /home/projects/github-shtgaydv nuxi 17:57:03\nNuxt project info: nuxi 17:57:03\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.3\n- CLI Version: 3.20.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: devtools, compatibilityDate\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-shtgaydv\n\n### Describe the bug\n\nHello,\n\nfirst of all I am not sure if this is a bug or if I did something wrong in configuring my tests or if this just normal behaviour. \n\nI run into the problem that global variables (`$\u003Csomething>`) [provided via plugins](https://nuxt.com/docs/guide/directory-structure/plugins#providing-helpers) are not available in the nuxt test context. I have a simple component, that uses the example function from the docs `$hello('world')` in the template section and the test fails with the error `TypeError: _ctx.$hello is not a function`. \n\nI can fix this by providing `$hello` via a global mock to the options of `mountSuspended`, but I was under the impression that @nuxt/test-utils should provide the same context to vitest as when I run the nuxt app normally via the dev server.\n\nThis also affects modules like [dayjs-nuxt](https://nuxt.com/modules/dayjs) for which I need to mock the `$dayjs()` function. A mock does not need to be provided for all modules though, e.g. the `$t()` function of @nuxt/i18n works without mocking it. Why is this the case?\n\n\n#### MyComponent.spec.ts\n```ts\n// @vitest-environment nuxt\nimport { describe, it } from 'vitest';\nimport { mountSuspended } from '@nuxt/test-utils/runtime';\nimport MyComponent from '../components/MyComponent.vue';\n\ndescribe('my test', () => {\n it('Should render the component', async () => {\n /* ❌ Fails with '_ctx.$hello is not a function' */\n const wrapper = await mountSuspended(MyComponent);\n\n /* ✅ Does only work with mocked $hello. */\n // const wrapper = await mountSuspended(MyComponent, {\n // global: { mocks: { $hello: (msg: string) => `Hello ${msg}!` } },\n // });\n });\n});\n```\n\n#### plugins/hello\n```ts\nexport default defineNuxtPlugin(() => {\n return {\n provide: {\n hello: (msg: string) => `Hello ${msg}!`,\n },\n };\n});\n```\n\nMyComponent.vue\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n {{ $hello('world') }}\n \u003C/div>\n\u003C/template>\n```\n\n### Additional context\n\nThere are similar issues reported here for when the function is provided via a Symbol but I did not find anything regarding this exact problem and error message.\n\n### Logs\n\n```shell-script\n\n```",[2038],{"name":1996,"color":1997},1102,"Global helpers from plugins not available in test context","2025-02-25T12:10:29Z","https://github.com/nuxt/test-utils/issues/1102",0.76288694,{"description":2045,"labels":2046,"number":2048,"owner":1985,"repository":1999,"state":1987,"title":2049,"updated_at":2050,"url":2051,"score":2052},"### Environment\n\n```\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.13.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.5.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.7.2, nuxt-open-fetch@0.9.5, @nuxtjs/i18n@9.1.0, nuxt-jsonld@2.1.0, @nuxtjs/device@3.2.4, @nuxtjs/robots@5.0.0, @vueuse/nuxt@12.0.0, @sidebase/nuxt-auth@0.9.4, @vesp/nuxt-fontawesome@1.1.0\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\nWhen using a vitest workspace, vitest complains that it can't resolve the config files, this is due to `defineVitestConfig`.\n```\n> vitest\n\nfailed to load config from /Users/reinierkaper/rvezy/rvezy-web-client/src/tests/unit/vitest.config.ts\n```\n\n### Describe the bug\n\nI think the `defineVitestConfig` wrapper conflicts with what vitest expects back in a workspace configuration file.\nEverything works fine when the tests are ran directly with a config file reference, just not in a workspace.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2047],{"name":2026,"color":2027},1043,"Vitest workspaces not properly supported by `defineVitestConfig`","2025-02-21T09:20:04Z","https://github.com/nuxt/test-utils/issues/1043",0.7635784,{"description":2054,"labels":2055,"number":2061,"owner":1985,"repository":2017,"state":2062,"title":2063,"updated_at":2064,"url":2065,"score":2066},"### 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_",[2056,2057,2058],{"name":2026,"color":2027},{"name":2011,"color":2012},{"name":2059,"color":2060},"reka-ui","56d799",2350,"closed","[SelectMenu] Broken focus/tab index after selecting","2024-12-03T15:11:34Z","https://github.com/nuxt/ui/issues/2350",0.7082831,{"description":2068,"labels":2069,"number":2074,"owner":1985,"repository":2017,"state":2062,"title":2075,"updated_at":2076,"url":2077,"score":2078},"### 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",[2070,2073],{"name":2071,"color":2072},"question","d876e3",{"name":2011,"color":2012},3290,"Runtime configuration change?","2025-04-12T15:53:05Z","https://github.com/nuxt/ui/issues/3290",0.72570026,{"description":2080,"labels":2081,"number":2083,"owner":1985,"repository":2017,"state":2062,"title":2084,"updated_at":2085,"url":2086,"score":2087},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.13.0\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.4\r\n- Builder: -\r\n- User Config: compatibilityDate, runtimeConfig, experimental, router, i18n, devServer, devtools, app, components, modules, vue, tailwindcss, image, ui, nitro, storyblok, algolia, colorMode, hooks\r\n- Runtime Modules: @nuxt/devtools@1.4.1, @nuxt/image@1.8.0, @nuxt/ui@2.18.4, @nuxtjs/i18n@8.5.1, @pinia/nuxt@0.5.4, @storyblok/nuxt@6.0.10, @vueuse/nuxt@11.0.3, nuxt-og-image@3.0.0-rc.66, @stefanobartoletti/nuxt-social-share@1.0.1\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-y5b7nb?file=app.vue\n\n### Description\n\nWhen using the button component with color 'white' and variant 'link', 'outline' or 'soft' invalid Tailwind color classes are generated, e.g. 'text-white-500'. It should be 'text-white'.\r\n\r\ntext-white-500 hover:text-white-600 disabled:text-white-500 dark:text-white-400 dark:hover:text-white-500 dark:disabled:text-white-400 focus-visible:ring-inset focus-visible:ring-white-500 dark:focus-visible:ring-white-400\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2082],{"name":2071,"color":2072},2109,"White link, outline and soft buttons generate wrong Tailwind classes, e.g. 'text-white-500'","2024-09-06T13:10:25Z","https://github.com/nuxt/ui/issues/2109",0.74405545,{"description":2089,"labels":2090,"number":2093,"owner":1985,"repository":2017,"state":2062,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.14.0`\n- Nuxt Version: `3.13.2`\n- CLI Version: `3.15.0`\n- Nitro Version: `2.9.7`\n- Package Manager: `pnpm@9.9.0`\n- Builder: `-`\n- User Config: `default`\n- Runtime Modules: `@nuxt/ui@3.0.0-alpha.7`\n- Build Modules: `-`\n\n### Version\n\n3.0.0-alpha.7\n\n### Reproduction\n\nhttps://github.com/madebyfabian/nuxt-ui3-drawer-chip-button-reprod\n\n### Description\n\nProbably super edge-case, sorry in advance 😄. Reproduction repo is linked, could not create a stackblitz because it seems tailwind v4 does not work with stackblitz.\n\n---\n\nThe issue is that if you use a `\u003CUChip>` to wrap your `\u003CUButton>` that acts as a trigger for `\u003CUModal>` or `\u003CUDrawer>` (probably also for other components?), the aria-* values are not applied properly. \n\nSo usually, the trigger button HTML should look like this:\n```html\n\u003Cbutton type=\"button\" aria-haspopup=\"dialog\" aria-expanded=\"false\" data-state=\"closed\" class=\"...\">...\u003C/button>\n```\n\nBut when wrapped with a Chip (see the `app.vue` in the reproduction repo), it looks like this:\n\n```html\n\u003Cdiv class=\"relative inline-flex items-center justify-center shrink-0\" type=\"button\" aria-haspopup=\"dialog\" aria-expanded=\"false\" data-state=\"closed\">\n \u003Cbutton type=\"button\" class=\"...\">\n \u003Cspan class=\"truncate\">...\u003C/span>\n \u003C/button>\n \u003Cspan class=\"rounded-full ring ring-[var(--ui-bg)] flex items-center justify-center text-[var(--ui-bg)] font-medium whitespace-nowrap bg-[var(--ui-primary)] h-[8px] min-w-[8px] text-[8px] top-0 right-0 absolute -translate-y-1/2 translate-x-1/2 transform\" >\u003C/span>\n\u003C/div>\n```\n\nso the aria-* attributes are applied to the parent `\u003Cdiv>` node and not the `\u003Cbutton>`, which causes Lighthouse to complain (thats why I noticed).\n\n---\n\nNot sure if that's a Nuxt UI specific issue or it's more in the underlying Vue Radix. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2091,2092],{"name":2026,"color":2027},{"name":2011,"color":2012},2484,"[v3] `UButton` wrapped with `UChip` as a `Modal`/`Drawer` trigger: aria-* attributes wrong","2024-10-31T11:18:06Z","https://github.com/nuxt/ui/issues/2484",0.74440265,["Reactive",2099],{},["Set"],["ShallowReactive",2102],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"0r3nhN-cfg3tejmAd3dbEtptXnZ2IvYp21klYBlbZ6M":-1},"/nuxt/ui/3071"]