\n```\n\n### Will results something like this\n```html\n\u003Cdiv class=\"... root-test base-test\">\n ...\n \u003Cinput class=\"...\" />\n\u003C/div>\n```\n\n### Description\n\nWhen applying themes in `app.config.ts`, both **UInputTags** and **UInputMenu (multiple)** share the same weird behaviour compared with other components, where the class applied to `base` part of the component are applied to `root` part of the component.\n\n### Expected Behaviour\nThe applied class on `base` should be applied to the `\u003Cinput />`, not the `root` part of the component which is the outer `\u003Cdiv />` just like other input components such as **UInput**, **UInputNumber**, or **UTextarea**.\n\nCorrect me if I'm wrong if this are intended, thank you!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3134,3137,3140],{"name":3135,"color":3136},"bug","d73a4a",{"name":3138,"color":3139},"v3","49DCB8",{"name":3141,"color":3142},"triage","ffffff",4530,"nuxt","ui","open","[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.6974062,{"description":3152,"labels":3153,"number":3157,"owner":3144,"repository":3145,"state":3146,"title":3158,"updated_at":3159,"url":3160,"score":3161},"### Environment\n\n- Operating System: Darwin\n- Node Version: v23.11.0\n- Nuxt Version: 3.17.3\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: devtools, typescript, css, compatibilityDate, devServer, vite, runtimeConfig, app, ui, scripts, modules, sentry, sourcemap\n- Runtime Modules: @nuxt/ui@3.1.2, @pinia/nuxt@0.11.0, pinia-plugin-persistedstate/nuxt@4.3.0, @sentry/nuxt/module@9.19.0, @nuxt/scripts@0.11.7, @nuxt/eslint@1.4.0\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/r7ryl3\n\n### Description\n\nI recently upgrade to NuxtUI 3.1.2 (from 3.0.1) and It's impossible (or I don't know) how to deal with custom type for `InputMenu`, I got some types issues on `label-key`, `v-model`, `items`, `slots` as you can see in my reproduction.\n\n### Additional context\n\n\n\n### Logs\n\n```shell-script\n\n```",[3154,3155,3156],{"name":3135,"color":3136},{"name":3138,"color":3139},{"name":3141,"color":3142},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.6983885,{"description":3163,"labels":3164,"number":3168,"owner":3144,"repository":3144,"state":3146,"title":3169,"updated_at":3170,"url":3171,"score":3172},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: pnpm@10.6.5\n- Builder: -\n- User Config: compatibilityDate, components\n- Runtime Modules: -\n- Build Modules: -\n\n## Additional\n\n- Mac Sequoia 15.3.2 (24D81)\n- \"vue-tsc\": \"2.2.8\"\n- VSCode 1.98.2 + Vue - Official\" extension (`vue.volar@2.2.8`)\n\n### Reproduction\n\nThis minimal reproduction [GitHub](https://github.com/mseeley/nuxt-vue-tsc) creates `nuxt.config.ts` and `.npmrc` on-demand, using `fixtures/*`, to satisfy different test conditions. Please see [the `README.md`](https://github.com/mseeley/nuxt-vue-tsc/blob/main/README.md).\n\nThis repo is not a mono-repo. While isolating the bug I first reproduced it in a version of this repository with PNPM workspaces. I have since been able to reduce the repro to a shallow single-app repo.\n\n## Tests\n\nIn both cases below you will see implicit-any TS errors [like this one from my local machine](https://github.com/mseeley/nuxt-vue-tsc/blob/main/screenshots/SCR-20250321-oluy.png).\n\n### Stackblitz\n\n- [Stackblitz](https://stackblitz.com/~/github.com/mseeley/nuxt-vue-tsc?file=README.md)\n- Run `./repro.sh`\n\n### Local\n\n- Checkout [the repo](https://github.com/mseeley/nuxt-vue-tsc)\n- Examine `Makefile`, it's used to run bash commands\n- Run `make pnpm-shamefully-hoist-false-components-empty-dirs`\n\n### Describe the bug\n\nThis bug reproduces when:\n\n- Node.js modules are installed using PNPM _without_ `shamefully-hoist=true`\n- Nuxt auto-import of files in `components/` is disabled.\n\nWhen this happens, Vue component generics of files in `components/`, are handled with an implicit any type. This reproduces on the CLI using `nuxi typecheck` and `vue-tsc --noEmit`. It also reproduces in VSCode.\n\n| Module Manager | `shamefully-hoist` | `components` | Pass | Repro |\n| -------------- | ------------------ | -------------- | ---- | -------------------------------------------------------- |\n| `npm@10.2.4` | n/a | `{ dirs: [] }` | ✅ | `make npm-components-empty-dirs` |\n| `pnpm@10.6.5` | `true` | `{ dirs: [] }` | ✅ | `make pnpm-shamefully-hoist-true-components-empty-dirs` |\n| `pnpm@10.6.5` | `false` | `{ dirs: [] }` | ❌ | `make pnpm-shamefully-hoist-false-components-empty-dirs` |\n| `npm@10.2.4` | n/a | `undefined` | ✅ | `make npm-components-undefined` |\n| `pnpm@10.6.5` | `true` | `undefined` | ✅ | `make pnpm-shamefully-hoist-true-components-undefined` |\n| `pnpm@10.6.5` | `false` | `undefined` | ✅ | `make pnpm-shamefully-hoist-false-components-undefined` |\n\n⭐️ `pnpm` tests show identical behavior on `v8.15.1`.\n\n\n### Additional context\n\nInitial workarounds are clear:\n\n- Enable `shamefully-hoist=true`\n- Or, enable auto-imports of `components/**/*.vue`\n\nBut, perhaps there's a surgical hoist? Or, a vue-tsc/Nuxt update?\n\n### Logs\n\n```shell-script\nFrom Stackblitz:\n\n\n❯ ./repro.sh\nLockfile is up to date, resolution step is skipped\nPackages: +579\n++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++\nProgress: resolved 579, reused 579, downloaded 0, added 579, done\n\ndependencies:\n+ typed-assert 1.0.9\n\ndevDependencies:\n+ nuxt 3.16.1\n+ vue-tsc 2.2.8\n\n> nuxt-app@ postinstall /home/mseeley/nuxt-vue-tsc\n> nuxt prepare\n\n✔ Types generated in .nuxt nuxi 4:46:35 PM\n\nDone in 4.3s\n\n> _tc\n> nuxi typecheck\n\napp.vue:13:40 - error TS7006: Parameter 'item' implicitly has an 'any' type.\n\n13 \u003CAll :items=\"scientists\" :key-of=\"(item) => item.id\">\n ~~~~\n\n\nFound 1 error in app.vue:13\n\n\n ERROR Process exited with non-zero status (2) 4:46:40 PM\n\n at new x (node_modules/.pnpm/tinyexec@0.3.2/node_modules/tinyexec/dist/main.js:440:5)\n at R._waitForOutput (node_modules/.pnpm/tinyexec@0.3.2/node_modules/tinyexec/dist/main.js:548:13)\n at async Object.run (node_modules/.pnpm/@nuxt+cli@3.23.1/node_modules/@nuxt/cli/dist/chunks/typecheck.mjs:84:9)\n at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:337:16)\n at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:328:11)\n at async Module.runMain (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:466:7) \n\n\n\n ERROR Process exited with non-zero status (2) 4:46:40 PM\n\n\n> nuxt-app@ _tc /home/mseeley/nuxt-vue-tsc\n> nuxi typecheck\n\napp.vue:13:40 - error TS7006: Parameter 'item' implicitly has an 'any' type.\n\n13 \u003CAll :items=\"scientists\" :key-of=\"(item) => item.id\">\n ~~~~\n\n\nFound 1 error in app.vue:13\n\n\n ERROR Process exited with non-zero status (2) 4:46:45 PM\n\n at new x (node_modules/.pnpm/tinyexec@0.3.2/node_modules/tinyexec/dist/main.js:440:5)\n at R._waitForOutput (node_modules/.pnpm/tinyexec@0.3.2/node_modules/tinyexec/dist/main.js:548:13)\n at async Object.run (node_modules/.pnpm/@nuxt+cli@3.23.1/node_modules/@nuxt/cli/dist/chunks/typecheck.mjs:59:7)\n at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:337:16)\n at async runCommand (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:328:11)\n at async Module.runMain (node_modules/.pnpm/citty@0.1.6/node_modules/citty/dist/index.mjs:466:7) \n\n\n\n ERROR Process exited with non-zero status (2) 4:46:45 PM\n\n ELIFECYCLE Command failed with exit code 1.\n```",[3165],{"name":3166,"color":3167},"pending triage","E99695",31499,"Disabling `components` auto-import breaks Vue component generics in PNPM without `shamefully-hoisted`","2025-03-22T09:33:52Z","https://github.com/nuxt/nuxt/issues/31499",0.7002646,{"description":3174,"labels":3175,"number":3178,"owner":3144,"repository":3145,"state":3179,"title":3180,"updated_at":3181,"url":3182,"score":3183},"### 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```",[3176,3177],{"name":3135,"color":3136},{"name":3138,"color":3139},4355,"closed","The UInput component is not a controlled component","2025-06-16T10:45:31Z","https://github.com/nuxt/ui/issues/4355",0.6318768,{"description":3185,"labels":3186,"number":3200,"owner":3144,"repository":3144,"state":3179,"title":3201,"updated_at":3202,"url":3203,"score":3204},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.16.0`\r\n- Nuxt Version: `3.8.0`\r\n- CLI Version: `3.9.1`\r\n- Nitro Version: `2.7.0`\r\n- Package Manager: `npm@9.5.1`\r\n- Builder: `-`\r\n- User Config: `devtools`, `modules`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@6.8.0`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://github.com/TheFlyer1983/nuxt-issue\n\n### Describe the bug\n\nI am getting an issue with a component, that previously worked. But after upgrading my Nuxt to v3.8.0, I keep getting this error whenever I refresh:\r\n\r\n\r\n\r\nI am unable to get past this or debug this because there is no real information in which to use to identify the issue.\n\n### Additional context\n\nThis is causing a major block on upgrading from Nuxt 2 to Nuxt 3, for a business application that is currently live.\n\n### Logs\n\n```shell-script\nI get these logs from my terminal.\r\n\r\n\r\n[[vite-node] [plugin:vite:vue] [VITE_ERROR] /components/inputs/StyledSelect.vue \u003Cbr>\u003Cpre><script lang=\"ts\" setup>\r\nconst props = withDefaults(\r\n defineProps<{\r\n disabled?: boolean;\r\n modelValue: object | string | number | null;\r\n small?: boolean;\r\n xSmall?: boolean;\r\n }>(),\r\n {\r\n disabled: false,\r\n small: false,\r\n xSmall: false\r\n }\r\n);\r\n\r\nconst emit = defineEmits<{\r\n (e: 'update:modelValue', value: object | string | number | null): void;\r\n}>();\r\n\r\nconst v = computed({\r\n get: () => props.modelValue,\r\n set: (value) => {\r\n emit('update:modelValue', value);\r\n }\r\n});\r\n</script>\r\n\r\n<template>\r\n <select\r\n v-model=\"v\"\r\n :disabled=\"disabled\"\r\n :class=\"[\r\n 'styled-select text-p-gray-4 transition-all duration-200 ease-in-out focus:outline-none focus:ring-1 focus:ring-p-pink',\r\n {\r\n 'form-select': !small,\r\n 'form-select-small': small,\r\n 'form-select-x-small': xSmall,\r\n 'opacity-50': disabled\r\n }\r\n ]\" data-v-inspector=\"components/inputs/StyledSelect.vue:29:3\"\r\n >\r\n <slot />\r\n </select>\r\n</template>\r\n\u003C/pre>\u003Cbr>\r\nat /components/inputs/StyledSelect.vue] {\r\n cause: {\r\n statusMessage: 'Vite Error',\r\n message: '[vite-node] [plugin:vite:vue] [VITE_ERROR] /components/inputs/StyledSelect.vue \u003Cbr>\u003Cpre><script lang=\"ts\" setup>\\n' +\r\n 'const props = withDefaults(\\n' +\r\n ' defineProps<{\\n' +\r\n ' disabled?: boolean;\\n' +\r\n ' modelValue: object | string | number | null;\\n' +\r\n ' small?: boolean;\\n' +\r\n ' xSmall?: boolean;\\n' +\r\n ' }>(),\\n' +\r\n ' {\\n' +\r\n ' disabled: false,\\n' +\r\n ' small: false,\\n' +\r\n ' xSmall: false\\n' +\r\n ' }\\n' +\r\n ');\\n' +\r\n '\\n' +\r\n 'const emit = defineEmits<{\\n' +\r\n \" (e: 'update:modelValue', value: object | string | number | null): void;\\n\" +\r\n '}>();\\n' +\r\n '\\n' +\r\n 'const v = computed({\\n' +\r\n ' get: () => props.modelValue,\\n' +\r\n ' set: (value) => {\\n' +\r\n \" emit('update:modelValue', value);\\n\" +\r\n ' }\\n' +\r\n '});\\n' +\r\n '</script>\\n' +\r\n '\\n' +\r\n '<template>\\n' +\r\n ' <select\\n' +\r\n ' v-model=\"v\"\\n' +\r\n ' :disabled=\"disabled\"\\n' +\r\n ' :class=\"[\\n' +\r\n \" 'styled-select text-p-gray-4 transition-all duration-200 ease-in-out focus:outline-none focus:ring-1 focus:ring-p-pink',\\n\" +\r\n ' {\\n' +\r\n \" 'form-select': !small,\\n\" +\r\n \" 'form-select-small': small,\\n\" +\r\n \" 'form-select-x-small': xSmall,\\n\" +\r\n \" 'opacity-50': disabled\\n\" +\r\n ' }\\n' +\r\n ' ]\" data-v-inspector=\"components/inputs/StyledSelect.vue:29:3\"\\n' +\r\n ' >\\n' +\r\n ' <slot />\\n' +\r\n ' </select>\\n' +\r\n '</template>\\n' +\r\n '\u003C/pre>\u003Cbr>',\r\n stack: '[vite-node] [plugin:vite:vue] [VITE_ERROR] /components/inputs/StyledSelect.vue \u003Cbr>\u003Cpre><script lang=\"ts\" setup>\\n' +\r\n 'const props = withDefaults(\\n' +\r\n ' defineProps<{\\n' +\r\n ' disabled?: boolean;\\n' +\r\n ' modelValue: object | string | number | null;\\n' +\r\n ' small?: boolean;\\n' +\r\n ' xSmall?: boolean;\\n' +\r\n ' }>(),\\n' +\r\n ' {\\n' +\r\n ' disabled: false,\\n' +\r\n ' small: false,\\n' +\r\n ' xSmall: false\\n' +\r\n ' }\\n' +\r\n ');\\n' +\r\n '\\n' +\r\n 'const emit = defineEmits<{\\n' +\r\n \" (e: 'update:modelValue', value: object | string | number | null): void;\\n\" +\r\n '}>();\\n' +\r\n '\\n' +\r\n 'const v = computed({\\n' +\r\n ' get: () => props.modelValue,\\n' +\r\n ' set: (value) => {\\n' +\r\n \" emit('update:modelValue', value);\\n\" +\r\n ' }\\n' +\r\n '});\\n' +\r\n '</script>\\n' +\r\n '\\n' +\r\n '<template>\\n' +\r\n ' <select\\n' +\r\n ' v-model=\"v\"\\n' +\r\n ' :disabled=\"disabled\"\\n' +\r\n ' :class=\"[\\n' +\r\n \" 'styled-select text-p-gray-4 transition-all duration-200 ease-in-out focus:outline-none focus:ring-1 focus:ring-p-pink',\\n\" +\r\n ' {\\n' +\r\n \" 'form-select': !small,\\n\" +\r\n \" 'form-select-small': small,\\n\" +\r\n \" 'form-select-x-small': xSmall,\\n\" +\r\n \" 'opacity-50': disabled\\n\" +\r\n ' }\\n' +\r\n ' ]\" data-v-inspector=\"components/inputs/StyledSelect.vue:29:3\"\\n' +\r\n ' >\\n' +\r\n ' <slot />\\n' +\r\n ' </select>\\n' +\r\n '</template>\\n' +\r\n '\u003C/pre>\u003Cbr>\\n' +\r\n 'at /components/inputs/StyledSelect.vue'\r\n },\r\n statusCode: 500,\r\n fatal: false,\r\n unhandled: false,\r\n statusMessage: 'Vite Error',\r\n data: undefined,\r\n __nuxt_error: true\r\n```\n```\n",[3187,3190,3193,3194,3197],{"name":3188,"color":3189},"good first issue","fbca04",{"name":3191,"color":3192},"3.x","29bc7f",{"name":3135,"color":3136},{"name":3195,"color":3196},"vite","3574D1",{"name":3198,"color":3199},"🔨 p3-minor","FBCA04",23822,"Issue with component since upgrading","2023-10-22T04:39:40Z","https://github.com/nuxt/nuxt/issues/23822",0.6872748,{"description":3206,"labels":3207,"number":3215,"owner":3144,"repository":3145,"state":3179,"title":3216,"updated_at":3217,"url":3218,"score":3219},"### Environment\n\nOperating System: Linux\r\nNode Version: v20.15.1\r\nNuxt Version: 3.13.0\r\nCLI Version: 3.13.1\r\nNitro Version: 2.9.7\r\nPackage Manager: bun@1.1.27\r\nBuilder: -\r\nUser Config: devtools, extends, modules, ui\r\nRuntime Modules: @nuxt/ui@2.18.4\r\nBuild Modules: -\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\n-\n\n### Description\n\n```\r\nType '{ \"v-model\": string | undefined; icon: string; type: string; size: \"md\"; placeholder: string; autocomplete: string; }' is not assignable to type 'IntrinsicAttributes & Partial\u003C{ name: string; size: InputSize; type: string; required: boolean; class: any; leading: boolean; color: InputColor; ... 16 more ...; modelModifiers: {}; }> & Omit\u003C...>'.\r\n Property 'autocomplete' does not exist on type 'IntrinsicAttributes & Partial\u003C{ name: string; size: InputSize; type: string; required: boolean; class: any; leading: boolean; color: InputColor; ... 16 more ...; modelModifiers: {}; }> & Omit\u003C...>'.\r\n```\n\n### Additional context\n\n`UInput` component doesn't have the default input types (`HTMLInputElement`)\n\n### Logs\n\n_No response_",[3208,3209,3210,3213],{"name":3135,"color":3136},{"name":3141,"color":3142},{"name":3211,"color":3212},"closed-by-bot","ededed",{"name":3214,"color":3212},"stale",2104,"`UInput` default types","2025-06-18T09:06:12Z","https://github.com/nuxt/ui/issues/2104",0.68961334,{"description":3221,"labels":3222,"number":3225,"owner":3144,"repository":3145,"state":3179,"title":3226,"updated_at":3227,"url":3228,"score":3229},"### 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```",[3223,3224],{"name":3135,"color":3136},{"name":3138,"color":3139},3983,"Default values are not loaded in the v-model","2025-06-30T13:04:54Z","https://github.com/nuxt/ui/issues/3983",0.69074625,{"description":3231,"labels":3232,"number":3243,"owner":3144,"repository":3144,"state":3179,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v18.16.0\n- Nuxt Version: 3.4.3\n- Nitro Version: 2.4.0\n- Package Manager: pnpm@8.5.0\n- Builder: vite\n- User Config: experimental, modules, colorMode\n- Runtime Modules: @unocss/nuxt@0.51.12, @vueuse/nuxt@10.1.2, nuxt-icon@0.4.0, nuxt-swiper@1.1.0, @nuxt/devtools@0.4.6, @nuxt/image-edge@1.0.0-28020728.5df24eb, @nuxtjs/color-mode@3.2.0\n- Build Modules: -\n\n### Reproduction\n\n\n\nThis error doesn't seem to be reproducible on Stackblitz so I have included a [github repo](https://github.com/tobychidi/nuxt-utils-import-error)\n\n### Describe the bug\n\nWhen functions are auto-imported from utils/ composables and used in Vue SFC Template, VsCode throws and error. Yes, I use the latest volar. This error appeared after `pnpm up` That bumped my Vue version to 3.3.1.\n\nI have not tried reverting Vue versions though. \n\n### Additional context\n\nExample: \n```\nProperty 'useShowSnack' does not exist on type '{ $: ComponentInternalInstance; $data: {}; $props: { key?: string | number | symbol | undefined; ref?: VNodeRef | undefined; ref_for?: boolean | undefined; ... 8 more ...; style?: unknown; }; ... 10 more ...; $watch\u003CT extends string | ((...args: any) => any)>(source: T, cb: T extends (...args: any) => infer R ? (arg...'.ts(2339)\n```\n\n_No response_\n\n### Logs\n\n_No response_",[3233,3234,3237,3240],{"name":3191,"color":3192},{"name":3235,"color":3236},"workaround available","11376d",{"name":3238,"color":3239},"upstream","E8A36D",{"name":3241,"color":3242},"upstream-bug","B60205",20827,"TS Error with auto-imports from composables and utils in Vue Template after 3.3","2024-11-07T20:13:37Z","https://github.com/nuxt/nuxt/issues/20827",0.694046,{"description":3249,"labels":3250,"number":3253,"owner":3144,"repository":3144,"state":3179,"title":3254,"updated_at":3255,"url":3256,"score":3257},"### Environment\n\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v18.17.0\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: npm@9.6.7\r\n- Builder: vite\r\n- User Config: app, vite, build, modules, css, runtimeConfig, plugins, googleFonts, devtools\r\n- Runtime Modules: @pinia/nuxt@0.4.11, @pinia-plugin-persistedstate/nuxt@1.1.1, @nuxtjs/google-fonts@3.0.2, nuxt-icon@0.5.0\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\n[Reproduction](https://stackblitz.com/edit/github-egvwuo-q53rtw?file=README.md)\n\n### Describe the bug\n\nUsing a component in the template while also importing its type in the Composition API leads to an error.\n\n### Additional context\n\nIn reproduction you can delete comment tags in **bug.vue** page to see error. I don't encounter this error when i don't call the component within the template. You can see it on the **weird.vue** page or in the **bug.vue** page with a comment.\r\n\r\nI don't encounter this issue in a project where I'm using version ^3.6.2.\n\n### Logs\n\n```shell-script\nInternal server error: Failed to resolve import \".nuxt/components\" from \"pages\\course\\index.vue\". Does the file exist? 05:38:47 \r\n Plugin: vite:import-analysis\r\n File: *path*/pages/course/index.vue:8:32\r\n 2 | import { ref } from 'vue';\r\n 3 | import { defineComponent as _defineComponent } from \"vue\";\r\n 4 | import { ModalsClassroom } from \".nuxt/components\";\r\n | ^\r\n 5 | const _sfc_main = /* @__PURE__ */ _defineComponent({\r\n 6 | __name: \"index\",\n```\n",[3251,3252],{"name":3191,"color":3192},{"name":3166,"color":3167},22979,"Nuxt3.6.5 - Failed to resolve import \".nuxt/components\" | Using a component in the template while also importing its type in the Composition API leads to an error.","2023-09-04T10:36:49Z","https://github.com/nuxt/nuxt/issues/22979",0.69502467,{"description":3259,"labels":3260,"number":3264,"owner":3144,"repository":3145,"state":3179,"title":3265,"updated_at":3266,"url":3267,"score":3268},"### 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",[3261,3262,3263],{"name":3135,"color":3136},{"name":3211,"color":3212},{"name":3214,"color":3212},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.697431,["Reactive",3270],{},["Set"],["ShallowReactive",3273],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPBpEY9vWFUVVKjv7j8icvZyg_kObuz8D9_GCERWEsOk":-1},"/nuxt/ui/2713"]