\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.",[2003,2006,2009],{"name":2004,"color":2005},"bug","d73a4a",{"name":2007,"color":2008},"v3","49DCB8",{"name":2010,"color":2011},"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.77498746,{"description":2019,"labels":2020,"number":2021,"owner":1994,"repository":2022,"state":2023,"title":2024,"updated_at":2025,"url":2026,"score":2027},"\r\n",[],244,"icon","closed","build error","2024-08-27T10:33:41Z","https://github.com/nuxt/icon/issues/244",0.44980168,{"description":2029,"labels":2030,"number":770,"owner":1994,"repository":1994,"state":2023,"title":2040,"updated_at":2041,"url":2042,"score":2043},"Hi, I think a lot of issues faced by Next.js apply to Nuxt.js also, and I believe that ultimately, such a feature will require a way to allow for custom server workflows, with session support etc.\r\nInterested to discuss this.\r\n\r\nhttps://github.com/zeit/next.js/issues/153\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This question is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c12\">#c12\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2031,2034,2037],{"name":2032,"color":2033},"documentation","5319e7",{"name":2035,"color":2036},"3.x","29bc7f",{"name":2038,"color":2039},"2.x","d4c5f9","Add login / authentication example","2023-01-19T14:23:45Z","https://github.com/nuxt/nuxt/issues/4",0.72509366,{"description":2045,"labels":2046,"number":2051,"owner":1994,"repository":2013,"state":2023,"title":2052,"updated_at":2053,"url":2054,"score":2055},"### Environment\n\n### Description\n\nThe `ID` column is not displayed when it is the first element in the columns array and item selection is enabled in the NuxtUI table.\n\n``` js\nconst columns = [\n {\n key: 'id',\n label: 'ID',\n },\n {\n key: 'displayName',\n label: 'Display Name',\n },\n {\n key: 'email',\n label: 'Email',\n }\n]\n```\n\n\n\n### Expected Behavior\n\nThe `ID` column should be displayed correctly regardless of its position in the columns array.\n\n### Workaround\n\nAdding a placeholder column before the `ID` column resolves the issue temporarily.\n\n```js\nconst columns = [\n {\n key: 'placeholder',\n },\n```\n\n\n\n\n### Environment\n\n- NuxtUI Version: 2.20.0\n- Browser: Chrome\n- Operating System: Windows 11\n\n### Version\n\n2.20.0\n\n### Reproduction\n\n### Steps to Reproduce\n\n1. Create a table with item selection enabled.\n2. Set a `ID` column as the first element in the columns array.\n3. Observe that the `ID` column is not displayed.\n",[2047,2048],{"name":2004,"color":2005},{"name":2049,"color":2050},"duplicate","cfd3d7",3040,"Columns [0] Element Does not Display if the Table is Selectable","2025-01-08T10:01:01Z","https://github.com/nuxt/ui/issues/3040",0.7416338,{"description":2057,"labels":2058,"number":2059,"owner":1994,"repository":2022,"state":2023,"title":2060,"updated_at":2061,"url":2062,"score":2063},"This css blocks the render of page... Why not this resource with async and defer?\r\n\r\n\r\n",[],155,"Render blocking CSS WPO Core Vitals","2024-07-18T22:45:44Z","https://github.com/nuxt/icon/issues/155",0.74861836,{"description":2065,"labels":2066,"number":2069,"owner":1994,"repository":2013,"state":2023,"title":2070,"updated_at":2071,"url":2072,"score":2073},"### Environment\n\n Operating System: Linux\n- Node Version: v20.15.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.7.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxtjs/i18n@9.1.1, @nuxt/ui@3.0.0-alpha.10, @pinia/nuxt@0.9.0, nuxt-viewport@2.2.0, @nuxthub/core@0.8.7, nuxt-auth-utils@0.5.6, @nuxt/fonts@0.10.3\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.10\n\n### Reproduction\n\n```vue\n//dont work\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\" multiple\n @update:model-value=\"testFunctionArray\" @change=\"testFunctionArray\"\n v-model=\"row.original.permissionsModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n```vue\n//work fine\n\u003CUSelect variant=\"none\" class=\"w-full\" label-key=\"name\" value-key=\"id\"\n @update:model-value=\"testFunction\" @change=\"testFunction\"\n v-model=\"row.original.permissionModel\" :items=\"permissions\">\n\u003C/USelect>\n```\n\n### Description\n\n`testFunctionArray` is never called if multiple prop is set to true\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2067,2068],{"name":2004,"color":2005},{"name":2007,"color":2008},2953,"USelect with multiple prop does not trigger event when model-value change","2025-01-25T13:12:19Z","https://github.com/nuxt/ui/issues/2953",0.75591326,{"description":2075,"labels":2076,"number":2085,"owner":1994,"repository":1994,"state":2023,"title":2086,"updated_at":2087,"url":2088,"score":2089},"### Environment\r\n\r\n- Operating System: Linux\r\n- Node Version: v18.16.1\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.1\r\n- Package Manager: yarn@3.6.0\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/daniluk4000/nuxt-3.4.2-docker-error\r\n\r\n1. Run `docker-compose up`\r\n2. Open app.vue with IDE and look at the imports\r\n3. Run `sudo yarn dev` (as Docker probably broke file system perms if you are not Mac user)\r\n4. Look at the fixed imports (using VS Code or non-WSL Webstorm)\r\n\r\n### Describe the bug\r\n\r\nBefore Nuxt 3.5.3 update tsconfig paths were generated relatively to current directory\r\n\r\n\r\n\r\nBut after Nuxt 3.6.0 update it now has absolute paths\r\n\r\n\r\n\r\nAnd breaks IDE as Docker has different folder names inside of it:\r\n\r\n\r\n\r\n### Additional context\r\n\r\nThis also breaks Webstorm when using with WSL, it can't resolve imports as well even without using docker for me.\r\n\r\nIt would be so good, if this was made for some reason, to optionally opt-out and use relative paths.\r\n\r\n### Logs\r\n\r\n_No response_",[2077,2080,2081,2082],{"name":2078,"color":2079},"types","2875C3",{"name":2035,"color":2036},{"name":2004,"color":2005},{"name":2083,"color":2084},"🔨 p3-minor","FBCA04",21827,"IDE types are broken after upgrade to 3.6.0 when using Docker (and WSL Webstorm)","2023-08-26T13:46:46Z","https://github.com/nuxt/nuxt/issues/21827",0.7590589,{"description":2091,"labels":2092,"number":2093,"owner":1994,"repository":2022,"state":2023,"title":2094,"updated_at":2095,"url":2096,"score":2097},"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,"Unmet Peer Dependency vue@>=3","2023-03-14T16:30:09Z","https://github.com/nuxt/icon/issues/59",0.75927943,{"description":2099,"labels":2100,"number":2102,"owner":1994,"repository":2013,"state":2023,"title":2103,"updated_at":2104,"url":2105,"score":2106},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v22.3.0`\r\n- Nuxt Version: `3.13.1`\r\n- CLI Version: `3.13.1`\r\n- Nitro Version: `2.9.7`\r\n- Package Manager: `yarn@1.22.22`\r\n- Builder: `-`\r\n- User Config: `compatibilityDate`, `devtools`, `modules`, `plugins`, `runtimeConfig`, `i18n`\r\n- Runtime Modules: `@nuxt/ui@2.18.4`, `@nuxtjs/i18n@8.5.1`\r\n- Build Modules: `-`\r\n\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-jfdc58?file=app.vue,app.config.ts\n\n### Description\n\n## Description\r\nThe Nuxt UI notification component is currently being created and added to the DOM even when no toast has been triggered. This behavior leads to unintended consequences due to the component's z-index:\r\n\r\nThe notification component occupies part of the screen unnecessarily.\r\nIt overlaps other elements on the page due to its z-index, potentially disrupting the user interface.\r\n\r\n## Expected Behavior\r\nThe notification component should only be created and added to the DOM when a toast is actually triggered.\r\n\r\n## Current Behavior\r\nThe notification component is always present in the DOM, regardless of whether a toast has been triggered or not.\r\n\r\n## Steps to Reproduce\r\n\r\n- Implement the Nuxt UI notification component in a project.\r\n- Inspect the DOM without triggering any toasts.\r\n- Observe that the notification component is present and has a z-index applied.\r\n\r\n## Additional Context\r\nThis issue affects the usability and performance of applications using the Nuxt UI notification component. Resolving it would improve both the user experience and the overall efficiency of the component.\r\n\r\n## Possible Solution\r\nConsider implementing a conditional rendering approach where the notification component is only added to the DOM when it's actually needed (i.e., when a toast is triggered).\r\n\u003Cimg width=\"1427\" alt=\"Screenshot 2024-09-04 at 6 29 00 PM\" src=\"https://github.com/user-attachments/assets/da90352f-71e6-4aaf-9bda-7a9e4a3fd056\">\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2101],{"name":2004,"color":2005},2113,"Notification component created even when toast is not triggered, causing z-index issues","2024-11-09T10:24:37Z","https://github.com/nuxt/ui/issues/2113",0.7596727,["Reactive",2108],{},["Set"],["ShallowReactive",2111],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"H8OrYQh04yrf2D_WDCiDQ3ObtdeCQnORGQsb0OR9lQg":-1},"/nuxt/scripts/244"]