\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.",[2013,2016,2017],{"name":2014,"color":2015},"bug","d73a4a",{"name":1988,"color":1989},{"name":1991,"color":1992},2859,"UInputNumber changes value on blur when not asked for","2024-12-08T12:04:52Z","https://github.com/nuxt/ui/issues/2859",0.75875485,{"description":2024,"labels":2025,"number":2030,"owner":1994,"repository":1995,"state":1996,"title":2031,"updated_at":2032,"url":2033,"score":2034},"### Description\n\n## Environment\n\nnuxt: `3.16.2`\n@nuxt/ui: `3.0.2`\n\n## Description\n\nI am trying to setup auto-imports for the `useToast` composable following the [nuxt doc](https://nuxt.com/docs/guide/concepts/auto-imports#auto-import-from-third-party-packages):\n\nThis is settings I have in `nuxt.config.ts`:\n\n```typescript\n{\n imports: {\n scan: false,\n presets: [\n { from: '@nuxt/ui/composables/useToast.js', imports: ['useToast'] },\n ],\n }\n}\n```\n\nAnd I got following error:\n\n```\nX [ERROR] Could not resolve \"#imports\"\n\n node_modules/@nuxt/ui/dist/runtime/composables/useToast.js:2:25:\n 2 │ import { useState } from \"#imports\";\n ╵ ~~~~~~~~~~\n\n The package import \"#imports\" is not defined in this \"imports\" map:\n\n node_modules/@nuxt/ui/package.json:45:13:\n 45 │ \"imports\": {\n ╵ ^\n\n You can mark the path \"#imports\" as external to exclude it from the bundle, which will remove this\n error and leave the unresolved path in the bundle.\n\n\n ERROR error while updating dependencies: 8:37:30 AM \nError: Build failed with 1 error:\nnode_modules/@nuxt/ui/dist/runtime/composables/useToast.js:2:25: ERROR: Could not resolve \"#imports\"\n```\n\n> Thanks in advance for any help.",[2026,2029],{"name":2027,"color":2028},"question","d876e3",{"name":1988,"color":1989},3928,"Setting up auto-imports for composables throws \"Cannot resolve #imports\" error","2025-04-18T01:01:47Z","https://github.com/nuxt/ui/issues/3928",0.7820147,{"description":2036,"labels":2037,"number":2043,"owner":1994,"repository":1995,"state":2044,"title":2045,"updated_at":2046,"url":2047,"score":2048},"### 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_",[2038,2039,2040],{"name":2014,"color":2015},{"name":1988,"color":1989},{"name":2041,"color":2042},"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.7576507,{"description":2050,"labels":2051,"number":2056,"owner":1994,"repository":2057,"state":2044,"title":2058,"updated_at":2059,"url":2060,"score":2061},"Hello.\r\n\r\ni was just wondering is it possible to make better error logs?\r\nBecause at one moment tests just stop and all I see is:\r\n\r\n",[2052,2053],{"name":1985,"color":1986},{"name":2054,"color":2055},"vitest-environment","b60205",605,"test-utils","Is it possible to create better error logs?","2023-12-05T16:15:41Z","https://github.com/nuxt/test-utils/issues/605",0.7584055,{"description":2063,"labels":2064,"number":2065,"owner":1994,"repository":2066,"state":2044,"title":2067,"updated_at":2068,"url":2069,"score":2070},"I installed nuxt-icon with `yarn add nuxt-icon`\r\n\r\nThen, I got the following warning:\r\n\r\n`warning \"nuxt-icon > @iconify/vue@4.1.0\" has unmet peer dependency \"vue@>=3\".`\r\n\r\nI use node v16.19.1 and in my dependencies, I have \r\n`\"nuxt\": \"^3.2.3\",`\r\n`\"nuxt-icon\": \"^0.3.2\"`\r\n\r\nI checked vue's version with `yarn list --pattern vue` and got:\r\nyarn list v1.22.19\r\n├─ @iconify/vue@4.1.0\r\n├─ @unhead/vue@1.1.16\r\n├─ @vitejs/plugin-vue-jsx@3.0.0\r\n├─ @vitejs/plugin-vue@4.0.0\r\n├─ @vue/babel-helper-vue-transform-on@1.0.2\r\n├─ @vue/babel-plugin-jsx@1.1.1\r\n├─ @vue/compiler-core@3.2.47\r\n├─ @vue/compiler-dom@3.2.47\r\n├─ @vue/compiler-sfc@3.2.47\r\n├─ @vue/compiler-ssr@3.2.47\r\n├─ @vue/devtools-api@6.5.0\r\n├─ @vue/reactivity-transform@3.2.47\r\n├─ @vue/reactivity@3.2.47\r\n├─ @vue/runtime-core@3.2.47\r\n├─ @vue/runtime-dom@3.2.47\r\n├─ @vue/server-renderer@3.2.47\r\n├─ @vue/shared@3.2.47\r\n├─ @vueuse/head@1.1.15\r\n├─ vue-bundle-renderer@1.0.2\r\n├─ vue-devtools-stub@0.1.0\r\n├─ vue-router@4.1.6\r\n└─ vue@3.2.47\r\n\r\nSo vue@>=3 exists but I still get that warning.\r\n\r\nI tried `yarn upgrade` and `npx nuxi@latest upgrade` but none helped.\r\n\r\nEverything seems to be working, so should I fix it and how, or ignore it?",[],59,"icon","Unmet Peer Dependency vue@>=3","2023-03-14T16:30:09Z","https://github.com/nuxt/icon/issues/59",0.7639066,{"description":2072,"labels":2073,"number":2076,"owner":1994,"repository":1995,"state":2044,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### 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",[2074,2075],{"name":2027,"color":2028},{"name":1988,"color":1989},3290,"Runtime configuration change?","2025-04-12T15:53:05Z","https://github.com/nuxt/ui/issues/3290",0.76517826,{"description":2082,"labels":2083,"number":2086,"owner":1994,"repository":1995,"state":2044,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v20.11.0\n- Nuxt Version: 3.15.1\n- CLI Version: 3.19.1\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.2\n- Builder: -\n- User Config: compatibilityDate, app, devtools, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.0.0-alpha.10, @nuxt/ui@3.0.0-alpha.10, @nuxt/eslint@0.7.4\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/great-orla-2l7wyw\n\n### Description\n\nThe checkbox-type items are no longer working as expected. When we copy and paste the code from the documentation [here](https://ui3.nuxt.dev/components/dropdown-menu#with-checkbox-items), the behavior is different from what is described.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2084,2085],{"name":2014,"color":2015},{"name":1988,"color":1989},3071,"[DropdownMenu] checkbox-type items are no longer working","2025-01-25T12:55:17Z","https://github.com/nuxt/ui/issues/3071",0.7684224,{"labels":2092,"number":2097,"owner":1994,"repository":1994,"state":2044,"title":2098,"updated_at":2099,"url":2100,"score":2101},[2093,2096],{"name":2094,"color":2095},"3.x","29bc7f",{"name":2014,"color":2015},11846,"global imports transform is wrongly stripping code after `https://`","2023-01-19T15:48:19Z","https://github.com/nuxt/nuxt/issues/11846",0.7689625,["Reactive",2103],{},["Set"],["ShallowReactive",2106],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"RqijOuAldhCDQLLFvRqLX6KbUscTzU3vtPE2NvYhZW4":-1},"/nuxt/test-utils/388"]