\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.",[2865,2868,2871],{"name":2866,"color":2867},"bug","d73a4a",{"name":2869,"color":2870},"v3","49DCB8",{"name":2872,"color":2873},"triage","ffffff",2859,"nuxt","ui","open","UInputNumber changes value on blur when not asked for","2024-12-08T12:04:52Z","https://github.com/nuxt/ui/issues/2859",0.7642176,{"description":2883,"labels":2884,"number":2888,"owner":2875,"repository":2875,"state":2877,"title":2889,"updated_at":2890,"url":2891,"score":2892},"### Environment\n\n\n\n\n已经设置了\ndevServer: {\n host: '0.0.0.0',\n port: 3000,\n },\n但是局域网还是无法访问我的项目,请问是还需要配置什么吗 ?\n下面是我的版本信息\n\n\n\n### Reproduction\n\n暂时没有放在仓库上\n\n### Describe the bug\n\n1\n\n### Additional context\n\n本地还有另外一个项目,其他电脑可以正常访问。只有这个项目是无法访问的,并且尝试了更换端口号,依然无法访问,已经关了防火墙node v20.19.2\n\n### Logs\n\n```shell-script\n\n```",[2885],{"name":2886,"color":2887},"pending triage","E99695",32302,"设置devServe后,局域网无法访问项目","2025-06-05T08:09:48Z","https://github.com/nuxt/nuxt/issues/32302",0.7697763,{"description":2894,"labels":2895,"number":2899,"owner":2875,"repository":2900,"state":2877,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### 🆒 Your use case\n\nSo far I have been using Cloudflare Zaraz which collects data on the server side.\r\n\r\nSuch data collection is independent of blockers and cookies and other elements. Thanks to this, statistics are more stable and are usually not affected by the browser quite strongly.\r\n\r\nI have noticed a really huge problem and a huge drop in views and stability of data collection when moving GA4 from Cloudflare Zaraz to Nuxt Scripts.\r\n\r\nIt would be great if in the future there was a possibility of collecting data using server-side as it is described for example here:\r\n\r\nhttps://developers.google.com/tag-platform/learn/sst-fundamentals/5-sst-setup-analytics\r\n\r\nFor now, unfortunately, I am returning to Cloudflare Zaraz with most scripts because then everything is more stable and less blocked.\n\n### 🆕 The solution you'd like\n\nhttps://developers.google.com/tag-platform/learn/sst-fundamentals/5-sst-setup-analytics\n\n### 🔍 Alternatives you've considered\n\n_No response_\n\n### ℹ️ Additional info\n\n_No response_",[2896],{"name":2897,"color":2898},"enhancement","a2eeef",238,"scripts","Server side GA4","2024-09-03T13:45:06Z","https://github.com/nuxt/scripts/issues/238",0.7723297,{"description":2906,"labels":2907,"number":2909,"owner":2875,"repository":2910,"state":2877,"title":2911,"updated_at":2912,"url":2913,"score":2914},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v20.8.1`\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: `yarn@1.22.19`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxt/test-utils/module@3.9.0`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-gee6qy?file=app.vue\r\n\r\n### Describe the bug\r\n\r\nOnce I expose a variable called `error` within the setup, the component fails to render. \r\nSince everything works within the dev server / build, I suspect this is something within `@nuxt/test-utils`\r\n\r\nAfter renaming the `error` variable to something else, the component can be mounted within the tests again.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nVitest caught 1 unhandled error during the test run.\r\nThis might cause false positive tests. Resolve unhandled errors to make sure your tests are not affected.\r\n\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯ Unhandled Rejection ⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\nTypeError: 'set' on proxy: trap returned falsish for property 'error'\r\n ❯ clonedComponent.render node_modules/@nuxt/test-utils/dist/runtime-utils/index.mjs:128:44\r\n 126| renderContext[key] = passedProps[key];\r\n 127| }\r\n 128| return render.call(this, renderContext, ...args);\r\n | ^\r\n 129| } : void 0,\r\n 130| setup: setup ? (props2) => wrappedSetup(props2, setupContext) : void 0\r\n ❯ renderComponentRoot node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:868:16\r\n ❯ ReactiveEffect.componentUpdateFn node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:5922:46\r\n ❯ ReactiveEffect.run node_modules/@vue/reactivity/dist/reactivity.cjs.js:174:19\r\n ❯ instance.update node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6053:16\r\n ❯ setupRenderEffect node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:6063:5\r\n ❯ eval node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:1613:9\r\n\r\nThis error originated in \"test/app.nuxt.test.ts\" test file. It doesn't mean the error was thrown inside the file itself, but while it was running.\r\nThe latest test that might've caused the error is \"Should mount\". It might mean one of the following:\r\n- The error was thrown, while Vitest was running this test.\r\n- This was the last recorded test before the error was thrown, if error originated after test finished its execution.\r\n⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯⎯\r\n\r\n```\r\n```\r\n",[2908],{"name":2866,"color":2867},684,"test-utils","mountSuspended fails: 'set' on proxy: trap returned falsish for property 'error'","2025-03-14T15:14:45Z","https://github.com/nuxt/test-utils/issues/684",0.7732218,{"description":2916,"labels":2917,"number":2918,"owner":2875,"repository":2919,"state":2920,"title":2921,"updated_at":2922,"url":2923,"score":2924},"\r\n",[],244,"icon","closed","build error","2024-08-27T10:33:41Z","https://github.com/nuxt/icon/issues/244",0.45961785,{"description":2926,"labels":2927,"number":1519,"owner":2875,"repository":2875,"state":2920,"title":2937,"updated_at":2938,"url":2939,"score":2940},"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>",[2928,2931,2934],{"name":2929,"color":2930},"documentation","5319e7",{"name":2932,"color":2933},"3.x","29bc7f",{"name":2935,"color":2936},"2.x","d4c5f9","Add login / authentication example","2023-01-19T14:23:45Z","https://github.com/nuxt/nuxt/issues/4",0.71512216,{"description":2942,"labels":2943,"number":2944,"owner":2875,"repository":2919,"state":2920,"title":2945,"updated_at":2946,"url":2947,"score":2948},"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.7495594,{"description":2950,"labels":2951,"number":2955,"owner":2875,"repository":2876,"state":2920,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Environment\n\n(CodeSandbox) \n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, devtools, compatibilityDate, future\n- Runtime Modules: @nuxt/ui@3.0.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/quirky-pare-zxxn6x\n\n### Description\n\nThe RadioGroup component does not accept boolean values, despite the documentation saying it should. I'm not sure if this is a bug or is intended and the documentation is wrong.\n\nIn the provided codesandbox (using v3.0.2) you can see the type errors in the code, as well as buggy behavior in the app.\n\nDocs: https://github.com/nuxt/ui/blob/9ec159e20793a0f7346ad4ec9c0fe142320f0fa2/docs/content/3.components/radio-group.md?plain=1#L20\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2952,2953,2954],{"name":2866,"color":2867},{"name":2869,"color":2870},{"name":2872,"color":2873},3724,"RadioGroup does not accept booleans","2025-04-03T10:21:37Z","https://github.com/nuxt/ui/issues/3724",0.7551715,{"description":2961,"labels":2962,"number":2964,"owner":2875,"repository":2876,"state":2920,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### 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_",[2963],{"name":2866,"color":2867},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.7554417,{"description":2970,"labels":2971,"number":2976,"owner":2875,"repository":2876,"state":2920,"title":2977,"updated_at":2978,"url":2979,"score":2980},"### 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",[2972,2973],{"name":2866,"color":2867},{"name":2974,"color":2975},"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.7607588,["Reactive",2982],{},["Set"],["ShallowReactive",2985],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fH8OrYQh04yrf2D_WDCiDQ3ObtdeCQnORGQsb0OR9lQg":-1},"/nuxt/scripts/244"]