\n \u003C/u-form>\n\u003C/template>\n```\n\nTriggers type error:\n\n```\nType '{ file: { readonly lastModified: number; readonly name: string; readonly webkitRelativePath: string; readonly size: number; readonly type: string; arrayBuffer: () => Promise\u003CArrayBuffer>; slice: (start?: number | undefined, end?: number | undefined, contentType?: string | undefined) => Blob; stream: () => ReadableSt...' is not assignable to type 'Partial\u003C{ file: File; }>'\n```\n\nExpected: it's allowed to have a form with a schema that requires a file to be selected.\n\n### Additional context\n\nIn fact, I believe this is a much broader problem. Why is the `state` typed as `Partial\u003CInferInput\u003CS>> ` in the first place? The type of the fields does not always match the schema. Basically, that's the point of schema in the first place, to perform validation — and not only value, but also the type. Consider number input value:\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport * as z from \"zod\"\n\nconst fields = reactive({\n // Type used by \u003Cinput v-model=\"...\" type=\"number\">\n // It saves empty string for non-numbers.\n foo: \"\" as number | \"\",\n})\n\nconst schema = z.object({\n // But we need the actual number for the input data.\n foo: z.number(),\n})\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cu-form :state=\"fields\" :schema=\"schema\">\n \u003Cinput v-model=\"fields.foo\" type=\"number\" />\n \u003C/u-form>\n\u003C/template>\n```\n\nThis leads to similar type error:\n\n```\nType '{ foo: number | \"\"; }' is not assignable to type 'Partial\u003C{ foo: number; }>'.\n Types of property 'foo' are incompatible.\n Type 'number | \"\"' is not assignable to type 'number | undefined'.\n Type 'string' is not assignable to type 'number'.\n```\n\nAs I see it, `state` should be untyped/unknown.\n\n### Logs\n\n```shell-script\n\n```",[3207,3208],{"name":3188,"color":3189},{"name":3194,"color":3195},5204,"UFile (and others!) type error when used with schema validation","2025-10-10T06:07:16Z","https://github.com/nuxt/ui/issues/5204",0.6982679,{"description":3215,"labels":3216,"number":3220,"owner":3197,"repository":3198,"state":3221,"title":3222,"updated_at":3223,"url":3224,"score":3225},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `4.0.3`\n- CLI Version: `3.28.0`\n- Nitro Version: `2.12.4`\n- Package Manager: `pnpm@10.9.0`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `extends`, `components`, `alias`, `dir`, `ssr`, `modules`, `ui`, `css`, `imports`, `app`, `runtimeConfig`\n- Runtime Modules: `@nuxt/ui@3.3.2`, `@pinia/nuxt@0.11.2`, `@vueuse/nuxt@13.6.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/fancy-leaf-5z2y85\n\n### Description\n\nThe InputMenu component crashes when provided with numeric values in its items prop, the same usage works correctly with SelectMenu.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3217,3218,3219],{"name":3188,"color":3189},{"name":3191,"color":3192},{"name":3194,"color":3195},4767,"closed","InputMenu crashes when using numeric items","2025-08-16T02:41:48Z","https://github.com/nuxt/ui/issues/4767",0.66268957,{"description":3227,"labels":3228,"number":3232,"owner":3197,"repository":3198,"state":3221,"title":3233,"updated_at":3234,"url":3235,"score":3236},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: npm@11.2.0\n- Builder: -\n- User Config: compatibilityDate, devtools, nitro, css, modules, vite\n- Runtime Modules: @nuxt/fonts@0.11.0, @nuxt/content@3.4.0, @nuxt/icon@1.11.0, @nuxt/image@1.10.0, @nuxt/scripts@0.11.5, @nuxt/eslint@1.3.0, @nuxt/ui@3.0.2\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.2\n\n### Reproduction\n\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flex flex-col items-center justify-center gap-4 h-screen\">\n\n {{ state }}\n\n \u003Cdiv class=\"flex items-center gap-2\">\n \u003CUTree\n :items=\"gates\"\n label-key=\"label\"\n value-key=\"id\"\n v-model=\"state.gate\" \n >\n \u003C/UTree>\n \u003C/div>\n \u003C/div>\n\u003C/template>\n\n\n\n\u003Cscript\n lang=\"ts\"\n setup\n>\n\nimport type { FormSubmitEvent } from '@nuxt/ui'\n\ninterface Gate {\n id: number,\n label: string,\n uname: string\n}\n\ntype Schema = {\n gate: Gate\n}\n\nconst state = reactive\u003CPartial\u003CSchema>>({\n gate: undefined,\n})\n\nconst gates = [{id:0, uname: null, label: \"unknown\"}, {id:1, uname: \"first-gate\", label: \"First\"}]\n\n\u003C/script>\n```\n\n### Description\n\nvalue-key points to id or missed.\n\nv-model type check points to id:number but there is full object.\n\n\n\n### Additional context\n\nHow to get full object here when bug fixed?\n\n### Logs\n\n```shell-script\n\n```",[3229,3230,3231],{"name":3188,"color":3189},{"name":3191,"color":3192},{"name":3194,"color":3195},3762,"UTree value-key not working","2025-09-18T11:00:16Z","https://github.com/nuxt/ui/issues/3762",0.6661384,{"description":3238,"labels":3239,"number":3246,"owner":3197,"repository":3198,"state":3221,"title":3247,"updated_at":3248,"url":3249,"score":3250},"### Environment\r\n\r\n- Operating System: Windows_NT\r\n- Node Version: v20.12.2\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.9.1\r\n- Package Manager: pnpm@8.3.1\r\n- Builder: -\r\n- User Config: app, colorMode, ui, css, modules, runtimeConfig, authJs, pinia, nitro, alias, devtools, imports, typescript\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.2.0, @vueuse/nuxt@9.13.0, @hebilicious/authjs-nuxt@0.3.0-beta.2, @nuxtjs/eslint-module@4.1.0, nuxt-monaco-editor@1.2.7, nuxt-lodash@2.5.3, @nuxt/ui@2.14.2\r\n- Build Modules: -\r\n\r\n### Version\r\n\r\nv2.14.2\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/nuxt-ui-eqhn2j?file=app.vue\r\n\r\n### Description\r\n\r\nI'm getting multiple new type errors that I wasn't getting before with types that used to be valid. I think this is being caused by an update to `vue-tsc`, however I'm not sure.\r\n\r\nIn the reproduction link you can see the two examples that don't compile. Simply run `npm run typecheck` in the console to get the errors\r\nHere are the minimal examples\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nconst value = ref\u003Cstring | null | undefined>(undefined);\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CUInput v-model.trim=\"value\" />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n```shell-script\r\nTS2322: Type 'string | null | undefined' is not assignable to type 'string | number | undefined'.\r\n```\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nconst value = ref\u003Cboolean|undefined>();\r\nconst options = [\r\n {\r\n label: 'Yes',\r\n value: true\r\n },\r\n {\r\n label: 'No',\r\n value: false\r\n },\r\n {\r\n label: 'None selected',\r\n value: undefined\r\n }\r\n];\r\n\u003C/script>\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CUSelectMenu\r\n :options=\"options\"\r\n v-model=\"value\"\r\n value-attribute=\"value\" option-attribute=\"label\"\r\n />\r\n \u003C/div>\r\n\u003C/template>\r\n```\r\n```shell-script\r\nTS2322: Type 'boolean | undefined' is not assignable to type 'string | number | Record\u003Cstring, any> | unknown[] | undefined'.\r\n```\r\n\r\n### Additional context\r\n\r\n\r\n### Logs\r\n\r\n```shell-script\r\napp.vue:14:15 - error TS2322: Type 'string | null | undefined' is not assignable to type 'string | number | undefined'.\r\n\r\n14 \u003CUInput v-model.trim=\"inputValue\" />\r\n ~~~~~~~~~~\r\n\r\n node_modules/@nuxt/ui/dist/runtime/components/forms/Input.vue.d.ts:244:5\r\n 244 modelValue: string | number;\r\n ~~~~~~~~~~\r\n The expected type comes from property 'modelValue' which is declared here on type 'Partial\u003C{ size: InputSize; ui: any; id: string; icon: string; color: any; type: string; class: any; name: string; modelValue: string | number; leading: boolean; variant: InputVariant; ... 12 more ...; modelModifiers: { ...; }; }> & Omit\u003C...> & Record\u003C...>'\r\n\r\n\r\nFound 1 error in app.vue:14\r\n```\r\n",[3240,3241,3244],{"name":3188,"color":3189},{"name":3242,"color":3243},"closed-by-bot","ededed",{"name":3245,"color":3243},"stale",1710,"Unable to use boolean values with USelectMenu or null with UInput","2025-06-19T02:12:37Z","https://github.com/nuxt/ui/issues/1710",0.6716977,{"description":3252,"labels":3253,"number":3258,"owner":3197,"repository":3198,"state":3221,"title":3259,"updated_at":3260,"url":3261,"score":3262},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v20.19.2`\n- Nuxt Version: `4.1.2`\n- CLI Version: `3.28.0`\n- Nitro Version: `2.12.6`\n- Package Manager: `npm@9.2.0`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `modules`, `css`\n- Runtime Modules: `@nuxt/ui@4.0.0-alpha.2`, `nuxt-auth-utils@0.5.25`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv4.0.0-alpha.x\n\n### Version\n\nv4.0.0-alpha.2\n\n### Reproduction\n\n-\n\n### Description\n\nAs the title says, you can't use \"number\" as a input type without TypeScript yelling at you.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3254,3255,3256],{"name":3188,"color":3189},{"name":3194,"color":3195},{"name":3257,"color":3192},"v4",5005,"AuthFormField does not support \"number\" as a valid type","2025-09-25T16:56:32Z","https://github.com/nuxt/ui/issues/5005",0.681694,{"description":3264,"labels":3265,"number":3271,"owner":3197,"repository":3198,"state":3221,"title":3272,"updated_at":3273,"url":3274,"score":3275},"### 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```",[3266,3267,3270],{"name":3188,"color":3189},{"name":3268,"color":3269},"needs reproduction","CB47CF",{"name":3191,"color":3192},4452,"UTable context menu error during selection of items","2025-07-13T16:34:46Z","https://github.com/nuxt/ui/issues/4452",0.6823382,{"description":3277,"labels":3278,"number":3281,"owner":3197,"repository":3198,"state":3221,"title":3282,"updated_at":3283,"url":3284,"score":3285},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.18.0`\n- CLI Version: `3.27.0`\n- Nitro Version: `2.12.4`\n- Package Manager: `pnpm@10.12.3`\n- Builder: `-`\n- User Config: `modules`, `ssr`, `components`, `devtools`, `app`, `css`, `colorMode`, `runtimeConfig`, `future`, `experimental`, `compatibilityDate`, `eslint`, `fonts`, `icon`, `supabase`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `reka-ui/nuxt@2.4.0`, `@nuxt/ui@3.3.0`, `@nuxtjs/supabase@1.5.2`, `@vueuse/nuxt@13.6.0`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.3.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/suspicious-lumiere-6jxxjc\n\n### Description\n\nWhen displaying the `UInputMenu`, with no items in the array (fetched later) but with a default value, the placeholder is shown instead of showing the string.\n\n### Additional context\n\nFaulty commit: 488707e\n\n#4528 \n\n### Logs\n\n```shell-script\n\n```",[3279,3280],{"name":3188,"color":3189},{"name":3191,"color":3192},4635,"`UInputMenu` does not display default model value (placeholder shown instead)","2025-08-14T09:04:53Z","https://github.com/nuxt/ui/issues/4635",0.6826992,{"description":3287,"labels":3288,"number":3291,"owner":3197,"repository":3198,"state":3221,"title":3292,"updated_at":3293,"url":3294,"score":3295},"### 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```",[3289,3290],{"name":3188,"color":3189},{"name":3191,"color":3192},4355,"The UInput component is not a controlled component","2025-06-16T10:45:31Z","https://github.com/nuxt/ui/issues/4355",0.6841147,{"description":3297,"labels":3298,"number":3301,"owner":3197,"repository":3198,"state":3221,"title":3302,"updated_at":3303,"url":3304,"score":3305},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: app, build, colorMode, compatibilityDate, debug, devtools, fonts, future, hooks, i18n, icon, imports, modules, nitro, routeRules, runtimeConfig, security, ssr, sourcemap, css, telemetry, vite\n- Runtime Modules: @nuxt/eslint@1.3.0, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.1.0, @nuxtjs/i18n@9.5.3, nuxt-security@2.2.0, @nuxt/ui@3.1.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/epic-smoke-95wysw?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nUsing the `@update:model-value` event handler produces type errors with the Select component, starting from nuxt-ui v3.1.0 (v3.0.2 works fine).\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nType 'boolean | AcceptableValue | undefined' is not assignable to type '\"yes\" | \"no\"'.\n Type 'undefined' is not assignable to type '\"yes\" | \"no\"'.ts-plugin(2322)\n```",[3299,3300],{"name":3188,"color":3189},{"name":3191,"color":3192},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.68548787,["Reactive",3307],{},["Set"],["ShallowReactive",3310],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$frfp5BX248yOme_Q5Ou1ZJIybswNhni_RKPAnD-aImQQ":-1},"/nuxt/ui/5018"]