\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup>\nconst tabIndex = ref(0)\nconst tabItems = [\n {\n accessorKey: 'firstTab',\n label: 'First Tab',\n value: 0\n },\n {\n accessorKey: 'secondTab',\n label: 'Second Tab',\n value: 1\n },\n {\n accessorKey: 'thirdTab',\n label: 'Third Tab',\n value: 2\n }\n]\n\u003C/script>\n```\n\n### Description\n\nIn Nuxt UI's UTabs component, when an item's value is set to 0 (a number), the internal TabsTrigger evaluates `:value=\"item.value || String(index)\"`. Since 0 is falsy in JavaScript, it falls back to String(index) (e.g., '0'), causing the v-model to update as a string instead of a number, leading to unexpected type coercion after tab selection.\n\nPotential solution:\n\n`:value=\"item.value ?? String(index)\" `\n\nThis uses the nullish coalescing operator (??), which only falls back if item.value is null or undefined (not falsy values like 0), preserving the numeric type for 0 while maintaining the intended fallback behavior for missing values.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3168,3169,3170],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4804,"UTabs: Numeric value 0 coerced to string due to falsy check in TabsTrigger","2025-08-21T22:30:48Z","https://github.com/nuxt/ui/issues/4804",0.7196871,{"description":3177,"labels":3178,"number":3182,"owner":3147,"repository":3148,"state":3149,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### Environment\n\n- Operating System: Windows (win32)\n- Node Version: v22.16.0\n- Nuxt Version: 3.17.5\n- CLI Version: 3.28.0\n- Nitro Version: 2.x (bundled with Nuxt 3.17.5)\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: nuxt.config.ts (with custom modules and configurations)\n- Runtime Modules: @clerk/nuxt, @nuxt/eslint, @nuxt/fonts, @nuxt/icon, @nuxt/image, @nuxt/scripts, @nuxt/test-utils, @nuxt/ui, nuxt-zod-i18n, @nuxtjs/i18n\n- Build Modules: (same as runtime)\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0 of Nuxt UI\n\n### Reproduction\n\nhttps://ui.nuxt.com/components/input-menu#control-search-term\n\n### Description\n\nThe UInputMenu component does not display the controlled search term when using v-model:search-term. In the documentation example at https://ui.nuxt.com/components/input-menu#control-search-term, searchTerm is set to 'D' but the input displays 'Backlog' (the selected value) instead of the search term.\n\n Expected Behavior:\n When v-model:search-term=\"searchTerm\" is used with searchTerm.value = 'D', the input field should display \"D\".\n\n Actual Behavior:\n The input field displays the selected value (\"Backlog\") instead of the controlled search term (\"D\").\n\n Impact:\n This prevents programmatic control of the search term display, which is needed for features like pre-filling search queries or maintaining search state across component updates.\n\n Reproduction:\n Use the exact code from the documentation example - the search term \"D\" is not reflected in the input display despite being properly bound via v-model:search-term.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3179,3180,3181],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4772,"v-model:search-term not updating search term when being set","2025-08-17T14:13:38Z","https://github.com/nuxt/ui/issues/4772",0.7236974,{"description":3188,"labels":3189,"number":3193,"owner":3147,"repository":3148,"state":3194,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Environment\n\nhttps://ui.nuxt.com/components/input-number#step\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\n1. If `step = 2` and I manually set the `value = 3`, the input automatically adjusts the value to `4` (nearest multiple of 2).\n2. If I change the `step = 3` and manually set the `value = 5`, the input automatically adjusts it to `6` (nearest multiple of 3).\n\n### Description\n\nhttps://ui.nuxt.com/components/input-number#step\n\n1. The step should only control the step size when increasing or decreasing the value.\n2. If I set the `value = 3` with `step = 2`, the increments should go as `3, 5, 7, 9, ...` and decrements should go as `3, 1, -1, -3, ...`\n3. The component should not force the value to the nearest multiple of the step.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3190,3191,3192],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4323,"closed","UInputNumber Step - Step should define increment/decrement value, not force multiples","2025-06-25T07:43:40Z","https://github.com/nuxt/ui/issues/4323",0.6512019,{"description":3200,"labels":3201,"number":3204,"owner":3147,"repository":3148,"state":3194,"title":3205,"updated_at":3206,"url":3207,"score":3208},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.5\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: modules, css, future, compatibilityDate, vite\n- Runtime Modules: @nuxt/ui@3.1.3\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-bsi7gjhw?file=app%2Fapp.vue\n\n### Description\n\nThe UInput component behaves the same way whether using `v-model` or just `:modelValue`—it retains input values when typed into. However, this is incorrect because I did not set up the `@update:modelValue` event\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3202,3203],{"name":3138,"color":3139},{"name":3141,"color":3142},4355,"The UInput component is not a controlled component","2025-06-16T10:45:31Z","https://github.com/nuxt/ui/issues/4355",0.6717214,{"description":3210,"labels":3211,"number":3215,"owner":3147,"repository":3148,"state":3194,"title":3216,"updated_at":3217,"url":3218,"score":3219},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v24.0.2\n- Nuxt Version: 3.17.4\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: bun@1.2.14\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules, css, runtimeConfig\n- Runtime Modules: @nuxt/ui-pro@3.1.3, @nuxtjs/supabase@1.5.1, @nuxt/image@1.10.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.3\n\n### Reproduction\n\nNo need for reproduction.\n\n### Description\n\nHi, and thanks for this amazing UI library.\nI was wondering why to use a v-model for UProgress since it does not update the script from the dom?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3212,3213,3214],{"name":3138,"color":3139},{"name":3141,"color":3142},{"name":3144,"color":3145},4232,"[UProgress]: replace v-model with :value?","2025-05-27T12:32:29Z","https://github.com/nuxt/ui/issues/4232",0.6981027,{"description":3221,"labels":3222,"number":3228,"owner":3147,"repository":3148,"state":3194,"title":3229,"updated_at":3230,"url":3231,"score":3232},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.9.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `srcDir`, `routeRules`, `app`, `svgSprite`, `alias`, `css`, `imports`, `modules`, `ssr`, `runtimeConfig`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `@nuxt/fonts@0.11.4`, `@nuxt/icon@1.14.0`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.8`, `@nuxt/test-utils@3.19.1`, `@nuxt/ui@3.1.3`, `@nuxtjs/svg-sprite@1.0.2`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/dreamy-euler-9595k7\n\n\n### Description\n\n\n\nHi when i select copy payment id i got that error when i console log the row it gives me undefined upon clicking kindly check this link: https://ui.nuxt.com/components/table#with-context-menu\n\n#4259 \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3223,3224,3227],{"name":3138,"color":3139},{"name":3225,"color":3226},"needs reproduction","CB47CF",{"name":3141,"color":3142},4452,"UTable context menu error during selection of items","2025-07-13T16:34:46Z","https://github.com/nuxt/ui/issues/4452",0.70603055,{"description":3234,"labels":3235,"number":3238,"owner":3147,"repository":3148,"state":3194,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### Environment\n\n- Operating System: Linux\n- Node Version: v24.4.0\n- Nuxt Version: -\n- CLI Version: 3.26.4\n- Nitro Version: -\n- Package Manager: bun@1.2.4\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/w6mpnq\n\n### Description\n\nThe props `defaultValue` doesn't seem to work on UInput (found this props on the documentation). The field stays empty.\n`modelValue` works \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3236,3237],{"name":3138,"color":3139},{"name":3141,"color":3142},4569,"defaultValue has no effect","2025-07-22T08:38:57Z","https://github.com/nuxt/ui/issues/4569",0.7085076,{"labels":3244,"number":3251,"owner":3147,"repository":3147,"state":3194,"title":3252,"updated_at":3253,"url":3254,"score":3255},[3245,3247,3248],{"name":3246,"color":3145},"stale",{"name":3158,"color":3159},{"name":3249,"color":3250},"2.x","d4c5f9",8023,"Dollar sign ($) in .env value converted to 'undefined' in $config","2023-01-22T15:36:07Z","https://github.com/nuxt/nuxt/issues/8023",0.7115035,["Reactive",3257],{},["Set"],["ShallowReactive",3260],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fKQAiRAyfwSfDKKBuO-vyT5KDMbIyWXeom5ypvQOBJio":-1},"/nuxt/ui/2859"]