\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",[3050,3051,3054],{"name":3020,"color":3021},{"name":3052,"color":3053},"closed-by-bot","ededed",{"name":3055,"color":3053},"stale",1710,"closed","Unable to use boolean values with USelectMenu or null with UInput","2025-06-19T02:12:37Z","https://github.com/nuxt/ui/issues/1710",0.61947626,{"description":3063,"labels":3064,"number":3074,"owner":3029,"repository":3029,"state":3057,"title":3075,"updated_at":3076,"url":3077,"score":3078},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.2\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.8.1\r\n- Package Manager: pnpm@8.15.2\r\n- Builder: -\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nCreate a `.config/nuxt.ts` or `.config/nuxt.config.ts` file instead of `nuxt.config.ts`.\n\n### Describe the bug\n\nAutomatic types are missing in the editor.\r\n\r\n\r\n\n\n### Additional context\n\nI honestly didn't know where to report it. This applies to the last [config-dir](https://github.com/pi0/config-dir/tree/main) proposal that was implemented.\r\n\r\nFYI @pi0\r\n\n\n### Logs\n\n_No response_",[3065,3068,3071],{"name":3066,"color":3067},"types","2875C3",{"name":3069,"color":3070},"3.x","29bc7f",{"name":3072,"color":3073},"🔨 p3-minor","FBCA04",25918,"missing types in editor with `.config`","2024-02-22T16:31:31Z","https://github.com/nuxt/nuxt/issues/25918",0.6644825,{"description":3080,"labels":3081,"number":3084,"owner":3029,"repository":3030,"state":3057,"title":3085,"updated_at":3086,"url":3087,"score":3088},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.0\n- Nitro Version: 2.11.8\n- Package Manager: pnpm@10.9.0\n- Builder: -\n- User Config: modules, css, build, supabase, content, pinia, devtools, debug, routeRules, future, compatibilityDate, eslint\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui-pro@3.1.0, @vueuse/nuxt@13.1.0, @nuxt/content@3.5.1, @nuxt/icon@1.12.0, @nuxt/image@1.10.0, @nuxt/scripts@0.11.6, @nuxt/test-utils@3.17.2, @nuxtjs/supabase@1.5.0, @pinia/nuxt@0.11.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\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flex\">\n \u003CUForm :state=\"state\" class=\"w-1/2 p-4\">\n \u003CUFormField v-for=\"(item, index) in items\" :key=\"index\" :label=\"index\" :name=\"index\">\n \u003CUColorPicker v-if=\"index == 'color'\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003CUSlider v-if=\"index == 'range' && typeof item == 'number'\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />\n \u003CUInput v-else :type=\"index\" v-model=\"state[index]\" :default-value=\"item\" />\n \u003C/UFormField>\n \u003C/UForm>\n \u003Cpre class=\"w-1/2 bg-gray-200 p-4 leading-14\"> {{ state }} \u003C/pre>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst state = ref({}) // ISSUE: Default values are not loaded in the v-model\nconst items = {\n number: 50,\n reset: true, // ISSUE: UInput is not supporting boolean values for v-model\n submit: true, // ISSUE: UInput is not supporting boolean values for v-model\n search: \"search\",\n date: \"2025-04-25\",\n text: \"text\",\n color: \"#ccffcc\",\n button: true, // ISSUE: UInput is not supporting boolean values for v-model\n checkbox: false, // ISSUE: UInput is not supporting boolean values for v-model\n \"datetime-local\": \"2025-04-25T10:49:31\",\n email: \"nobody@gmail.com\",\n file: \"\",\n hidden: \"hidden\",\n image: \"image.svg\",\n month: \"2025-04\",\n password: \"topsecret\",\n radio: true, // ISSUE: UInput is not supporting boolean values for v-model\n range: 50, // Default value is displayed but not loaded in the v-model\n tel: \"0612345678\",\n time: \"10:49:31\",\n url: \"www.chatgpt.com\",\n week: \"2025-W16\"\n}\n// const state = reactive(items) // Workaround for default-value\n\u003C/script>\n```\n\n### Description\n\nI made a small comparison between `UInput` and other components like `UColorPicker` and `USlider` and I stumbled on a couple of issues.\n* `default-value` is not displayed except for `range` and `USlider`\n* `default-value` is never initialized in the `v-model`\n* Booleans are not supported in the `v-model` and I was therefore not able to make them reactive.\n\nWorkaround is to load the default value via the `state`, but that requires an additional step and is therefore not ideal for dynamic forms\n`const state = reactive(items)`\n\nWorkaround for working with booleans, but I am not sure how to apply the `v-model` yet🤔\n`\u003CUInput v-if=\"typeof state[index] == 'boolean'\" :type=\"index\" :value=\"index\" :checked=\"item\" />`\n\n\n### Additional context\n\nDefault values via `default-value`\n\nDefault value via `state`\n\n\n### Logs\n\n```shell-script\n\n```",[3082,3083],{"name":3020,"color":3021},{"name":3023,"color":3024},3983,"Default values are not loaded in the v-model","2025-06-30T13:04:54Z","https://github.com/nuxt/ui/issues/3983",0.66752833,{"description":3090,"labels":3091,"number":3101,"owner":3029,"repository":3029,"state":3057,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.12.1`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@8.19.2`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nThe official template shows this problem out of the box:\r\n\r\n```bash\r\nnpx nuxi init -t my-module\r\ncd my-module\r\nnpm i\r\n```\n\n### Describe the bug\n\nIn the `nuxt.config.ts` you should find this typing error:\r\n\r\n```\r\nType 'NuxtModule\u003CModuleOptions>' is not assignable to type 'string | NuxtModule\u003CModuleOptions> | [(string | NuxtModule\u003CModuleOptions> | undefined)?, ({ [x: string]: any; } | undefined)?] | undefined'.\r\n```\r\n\r\nAdditionally, the types seem to be too loose and not autocomplete:\r\n\r\n```ts\r\nimport MyModule from '..'\r\n\r\nexport default defineNuxtConfig({\r\n modules: [\r\n [MyModule, {\r\n // no autocompletion here\r\n }]\r\n ],\r\n myModule: {\r\n // or here\r\n addPlugin: true\r\n }\r\n})\r\n```\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3092,3093,3094,3097,3098],{"name":3066,"color":3067},{"name":3069,"color":3070},{"name":3095,"color":3096},"workaround available","11376d",{"name":3020,"color":3021},{"name":3099,"color":3100},"schema","1d76db",15750,"Invalid types for `ModuleOptions` in `NuxtModule`","2023-01-22T00:09:19Z","https://github.com/nuxt/nuxt/issues/15750",0.6736393,{"description":3107,"labels":3108,"number":3111,"owner":3029,"repository":3029,"state":3057,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Environment\n\n```\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 4.0.1\n- CLI Version: 3.26.4\n- Nitro Version: 2.12.3\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-7amubixz?file=app%2Findex.d.ts\n\n### Describe the bug\n\nIn Nuxt 4, defineAppConfig() accepts any input, which results in the loss of type checking and autocomplete.\nIt seems that in this commit\n[69345c32a5b828c0a5ff141770d6d9d51f30d5b2](https://github.com/nuxt/nuxt/commit/69345c32a5b828c0a5ff141770d6d9d51f30d5b2#diff-2176c7ab69dcd5ffc94e79963693b007471788f25591aeb72e7533240ebad2c2R454)\nthe way .nuxt/types/app.config.d.ts is generated has changed — and now the defineAppConfig function accepts any type.\nWhen I manually removed this generated part, type hints and validation started working correctly again.\n\n### Additional context\n\n### With default generated `.nuxt/types/app.config.d.ts`\n\u003Cimg width=\"832\" height=\"523\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/445f8c71-b550-47a0-a6e0-c279c4b0a705\" />\n\n### Modified `.nuxt/types/app.config.d.ts`\n\u003Cimg width=\"841\" height=\"452\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/9cfe6d9d-9959-47ff-bfc3-31e7f24585b5\" />\n\n### Logs\n\n```shell-script\n\n```",[3109,3110],{"name":3066,"color":3067},{"name":3072,"color":3073},32745,"Custom defineAppConfig() types ignored, no type validation or hints","2025-07-25T13:14:14Z","https://github.com/nuxt/nuxt/issues/32745",0.67482847,{"description":3117,"labels":3118,"number":3124,"owner":3029,"repository":3029,"state":3057,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v22.12.0`\n- Nuxt Version: `3.15.1`\n- CLI Version: `3.20.0`\n- Nitro Version: `2.10.4`\n- Package Manager: `pnpm@9.15.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `modules`\n- Runtime Modules: `@nuxt/ui@2.20.0`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-jxcmyybr?file=app.vue\n\n### Describe the bug\n\nAfter looping though all items in useAppConfig().ui.colors, i get a false positive error after assigning the item to a UBadge's color property, the color is still applied.\n\n### Logs\n\n```shell-script\n[The expected type comes from property 'color' which is declared here on type 'Partial\u003C{ size: BadgeSize; class: any; ui: { base?: string | undefined; rounded?: string | undefined; font?: string | undefined; size?: DeepPartial\u003C{ xs: string; sm: string; md: string; lg: string; }, any> | undefined; ... 4 more ...; default?: DeepPartial\u003C...> | undefined; } & { ...; } & { ...; }; ... 7 more ...; t...'](https://github.com/nuxt/nuxt/issues/30535#issue-2781450805)\n```",[3119,3122],{"name":3120,"color":3121},"pending triage","E99695",{"name":3123,"color":3073},"needs reproduction",30535,"Type 'string' is not assignable to type 'BadgeColor | undefined'.ts-plugin(2322)","2025-01-12T23:05:37Z","https://github.com/nuxt/nuxt/issues/30535",0.6786626,{"description":3130,"labels":3131,"number":3135,"owner":3029,"repository":3030,"state":3057,"title":3136,"updated_at":3137,"url":3138,"score":3139},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.17.1\n- CLI Version: 3.25.0\n- Nitro Version: 2.11.11\n- Package Manager: npm@11.3.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, css, runtimeConfig, ui\n- Runtime Modules: @nuxt/ui@3.1.0, @formkit/auto-animate/nuxt@0.8.2\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\n-\n\n### Description\n\nAfter upgrading from v3.0.2 to v3.1.0 I'm missing types for event binding directives and intellisense/automcomplete for attributes of all Nuxt UI components. Below I added a specific example for the Table component, but this happens to all components. I have removed node_modules, reinstalled, cleared the .nuxt and .output directories, and tried setting up a new project as well (using `npx nuxi init -t ui \u003Cmy-app>`).\n\nMissing types on event binding directives:\n\u003Cimg width=\"712\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/b3bb862c-16aa-4deb-aa12-c07211034f9b\" />\n\nMissing autocomplete:\n\u003Cimg width=\"487\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/8a851f0a-5894-41ae-8cdf-3f2f51d2ab52\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3132,3133,3134],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4029,"Where are all the types? v3.0.2 -> v3.1.0 upgrade","2025-04-30T12:20:42Z","https://github.com/nuxt/ui/issues/4029",0.67995733,{"description":3141,"labels":3142,"number":3145,"owner":3029,"repository":3030,"state":3057,"title":3146,"updated_at":3147,"url":3148,"score":3149},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.14.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@11.3.0\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.1, @pinia/nuxt@0.11.0, @vueuse/nuxt@13.2.0, @nuxtjs/i18n@9.5.4, nuxt-security@2.2.0, @nuxt/ui@3.1.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/sharp-christian-kzdxt9?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nStarting from v3.1.2, using the [built-in v-model-modifiers](https://vuejs.org/guide/essentials/forms.html#modifiers) produces type errors. They are still working tho, so its only a type issue.\n\nReproduction:\n1. Open provided link\n2. Run `pnpx nuxi typecheck`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n➜ workspace git:(master) ✗ pnpx nuxi typecheck\nPackages: +1\n+\nProgress: resolved 1, reused 1, downloaded 0, added 1, done\nℹ Nuxt Icon server bundle mode is set to local 11:09:23 AM\n✔ Nuxt Icon discovered local-installed 2 collections: lucide, simple-icons 11:09:25 AM\nℹ Running with compatibility version 4 nuxt 11:09:25 AM\napp/pages/index.vue:8:22 - error TS2353: Object literal may only specify known properties, and 'modelModifiers' does not exist in type '{ readonly onBlur?: ((event: FocusEvent) => any) | undefined; readonly onChange?: ((event: Event) => any) | undefined; readonly \"onUpdate:modelValue\"?: ((payload: number) => any) | undefined; ... 24 more ...; modelValue?: number | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps'.\n\n8 \u003CUInput v-model.number=\"myNumber\" type=\"number\" />\n ~~~~~~~\n\napp/pages/index.vue:9:22 - error TS2353: Object literal may only specify known properties, and 'modelModifiers' does not exist in type '{ readonly onBlur?: ((event: FocusEvent) => any) | undefined; readonly onChange?: ((event: Event) => any) | undefined; readonly \"onUpdate:modelValue\"?: ((payload: string) => any) | undefined; ... 24 more ...; modelValue?: string | undefined; } & VNodeProps & AllowedComponentProps & ComponentCustomProps'.\n\n9 \u003CUInput v-model.lazy=\"myText\" />\n ~~~~~\n\n\nFound 2 errors in the same file, starting at: app/pages/index.vue:8\n\n\n ERROR Process exited with non-zero status (2) 11:09:41 AM\n\n at R._waitForOutput (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/chunks/main.mjs:508:13)\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\n at async Object.run (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/chunks/typecheck.mjs:91:9)\n at async runCommand$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1767:16)\n at async runCommand$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1758:11)\n at async runMain$1 (/root/.cache/pnpm/v3/tmp/dlx-4483/node_modules/.pnpm/nuxi@3.25.1/node_modules/nuxi/dist/shared/nuxi.BlFGnQYG.mjs:1896:7) \n\n\n\n ERROR Process exited with non-zero status (2)\n```",[3143,3144],{"name":3020,"color":3021},{"name":3023,"color":3024},4166,"Built-in v-model modifiers produce type errors with v3.1.2","2025-05-22T12:51:25Z","https://github.com/nuxt/ui/issues/4166",0.68216366,["Reactive",3151],{},["Set"],["ShallowReactive",3154],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUzqxhmUkovefiyiWhXvm7lscO6IGp0Zm8QfttRWGuto":-1},"/nuxt/ui/2104"]