\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```",[2852,2855,2858],{"name":2853,"color":2854},"bug","d73a4a",{"name":2856,"color":2857},"v3","49DCB8",{"name":2859,"color":2860},"triage","ffffff",3983,"nuxt","ui","open","Default values are not loaded in the v-model","2025-05-05T16:31:01Z","https://github.com/nuxt/ui/issues/3983",0.65367675,{"description":2870,"labels":2871,"number":2875,"owner":2862,"repository":2863,"state":2864,"title":2876,"updated_at":2877,"url":2878,"score":2879},"### 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```",[2872,2873,2874],{"name":2853,"color":2854},{"name":2856,"color":2857},{"name":2859,"color":2860},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.66520303,{"description":2881,"labels":2882,"number":2886,"owner":2862,"repository":2862,"state":2864,"title":2887,"updated_at":2888,"url":2889,"score":2890},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v20.10.0`\n- Nuxt Version: `3.17.4`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `yarn@1.22.19`\n- Builder: `-`\n- User Config: `future`, `compatibilityDate`, `experimental`, `features`, `unhead`, `modules`, `eslint`, `components`, `primevue`, `shadcn`, `colorMode`, `dayjs`, `veeValidate`, `app`, `nitro`, `runtimeConfig`\n- Runtime Modules: `@nuxt/eslint@1.4.1`, `@vueuse/nuxt@13.2.0`, `@nuxtjs/tailwindcss@6.14.0`, `@headlessui-float/nuxt@0.15.0`, `@primevue/nuxt-module@4.3.4`, `dayjs-nuxt@2.1.11`, `shadcn-nuxt@2.1.0`, `@nuxtjs/color-mode@3.5.2`, `@vee-validate/nuxt@4.15.0`\n- Build Modules: `-`\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-glf1dfbb?file=nuxt.config.ts\n\nOpen `useMyData.ts` and check the `res` type. It should be `AsyncData\u003Cstring | null, ...>`, but it is `AsyncData\u003Cstring | undefined, ...>` desipte the fact that `experimental.defaults.useAsyncData.value` is set to `'null'` in `nuxt.config.ts.`.\n\nAlso please check `.nuxt/types/app.defaults.d.ts` file, that shows that the type is really `undefined` (`type DefaultAsyncDataValue = undefined`).\n\n### Describe the bug\n\nWhen `future.compatibilityVersion` is set to `4` and `experimental.defaults.useAsyncData.value` is set to `'null'` then `useAsyncData` and `useFetch` use `null` as the default. This works in runtime as expected.\n\nBut the type of `DefaultAsyncDataValue` generated in `.nuxt/types/app.defaults.d.ts` is still `undefined`. I thought the whole point of introduction of `DefaultAsyncDataValue` type was to make this change backward compatible.\n\nI even found a template in #27294 that supposedly should be responsible for this: https://github.com/nuxt/nuxt/pull/27294/files#diff-2176c7ab69dcd5ffc94e79963693b007471788f25591aeb72e7533240ebad2c2\n\nBut it looks like it doesn't take into account `experimental.defaults.useAsyncData.value` flag.\n\nAll the above also applies to `experimental.defaults.useAsyncData.errorValue` flag.\n\n### Additional context\n\nI'm not sure if this option was ever intended to modify TypeScript definitions. Maybe I'm expecting too much. :D\n\nBut I would say the option is really useful during migration, IMHO. While the Nuxt migration docs mentions `npx codemod@latest nuxt/4/default-data-error-value`, in my case this command didn't catch any comparisons to `null` in the codebase. But they really exists, so the code starts to work incorrectly when `useFetch` suddenly starts to return `undefined` instead of the expected `null`.\n\nHonestly, I'm surprised that this change is marked as \"Impact Level: Minimal\". It is pretty severe impact to me, if code's expectations have been changed. :)\n\nFor example I found a code like this:\n\n```ts\nconst { data: loadedItems } = await useItemDictionary() // Uses useFetch + cache under the hood\nconst items = computed(() => {\n if (loadedItems.value === null) {\n return []\n }\n return loadedItems.value.map(\n (item) => ...\n )\n})\n```\n\nPreviously it worked, but now it will throw an error because it will try to use `Array.map` on `undefined`.\nThe `codemod` didn't catch this error.\n\nFortunately, this error was catched by TypeScript. But it catches it even when `experimental.defaults.useAsyncData.value` is set to `'null'`, while it shouldn't. :) Quite contrary, if you chage `loadedItems.value === null` to `loadedItems.value === undefined` in the code above, the TypeScript error will disappear, but runtime error will appear, if `experimental.defaults.useAsyncData.value` is set to `'null'`.\n\n### Logs\n\n```shell-script\n\n```",[2883],{"name":2884,"color":2885},"pending triage","E99695",32213,"Setting `experimental.defaults.useAsyncData.value` does not update TS types","2025-05-27T01:19:10Z","https://github.com/nuxt/nuxt/issues/32213",0.66748476,{"description":2892,"labels":2893,"number":2904,"owner":2862,"repository":2862,"state":2864,"title":2905,"updated_at":2906,"url":2907,"score":2908},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.5.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.23.0\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.9.0\n- Builder: -\n- User Config: compatibilityDate, devtools, future, modules\n- Runtime Modules: @nuxt/eslint@1.2.0\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/gaisinskii/nuxt3-parent-node-null?file=app/pages/index.vue\n\nSteps:\n\n1) Follow stackblitz link and wait for it to install\n2) Press \"Open in New Tab\" button, wait for it to fully load and then open the console\n\n\u003Cimg width=\"130\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bce6d0cb-ddd7-447f-b915-b965844deb32\" />\n\n3) Navigate to `pages/index.vue`, modify the `console.log()` and save\n\n### Describe the bug\n\nThe previous [issue](https://github.com/nuxt/nuxt/issues/25214) was closed, but the error remains even in the latest Nuxt version.\n\nThe error will disappear if you add `lazy:true` option\n\n```\nconst { data } = await useFetch('https://jsonplaceholder.typicode.com/todos/1', {\n lazy: true\n})\n```\n\nAs you can see, both `app.vue` `layouts/default.vue` are wrapped with `divs` as it was suggested in the previous issue but we still get the bug.\n\nIs adding `lazy` option is the best workaround as for now?\n\n\u003Cimg width=\"500\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/ca5929e7-f84b-4d0f-a57b-e1cf38c34813\" />\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nvirtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16 [Vue warn]: Unhandled error during execution of component update \n at \u003CRouterView name=undefined route=undefined > \n at \u003CNuxtPage> \n at \u003CDefault ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CAsyncComponentWrapper ref=Ref\u003C Proxy(Object) {…} > > \n at \u003CLayoutLoader key=\"default\" layoutProps= {ref: RefImpl} name=\"default\" > \n at \u003CNuxtLayoutProvider layoutProps= {ref: RefImpl} key=\"default\" name=\"default\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\nwarn$1 @ runtime-core.esm-bundler.js:51\nlogError @ runtime-core.esm-bundler.js:263\nhandleError @ runtime-core.esm-bundler.js:255\ncallWithErrorHandling @ runtime-core.esm-bundler.js:201\nflushJobs @ runtime-core.esm-bundler.js:408\nPromise.then\nqueueFlush @ runtime-core.esm-bundler.js:322\nqueueJob @ runtime-core.esm-bundler.js:317\neffect2.scheduler @ runtime-core.esm-bundler.js:5448\ntrigger @ reactivity.esm-bundler.js:253\nendBatch @ reactivity.esm-bundler.js:311\nnotify @ reactivity.esm-bundler.js:597\ntrigger @ reactivity.esm-bundler.js:571\nset value @ reactivity.esm-bundler.js:1448\nfinalizeNavigation @ vue-router.mjs:3498\n(anonymous) @ vue-router.mjs:3363\nPromise.then\npushWithRedirect @ vue-router.mjs:3330\npush @ vue-router.mjs:3255\nreplace @ vue-router.mjs:3258\naddRoutes @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:16\n(anonymous) @ virtual:nuxt:/home/gaisinskii/nuxt3-parent-node-null/.nuxt/routes.mjs:21\n(anonymous) @ client:34\n(anonymous) @ client:208\n(anonymous) @ client:183\nqueueUpdate @ client:183\nawait in queueUpdate\n(anonymous) @ client:884\nhandleMessage @ client:882\nonMessage @ client:299\n(anonymous) @ client:429\ndispatchEvent @ .localservice@runtime.5a421e5b.js:26\n_handleMessage @ .localservice@runtime.5a421e5b.js:26\n_0x3963e2 @ .localservice@runtime.5a421e5b.js:26Understand this warningAI\nruntime-dom.esm-bundler.js:51 Uncaught (in promise) TypeError: Cannot read properties of null (reading 'parentNode')\n at parentNode (runtime-dom.esm-bundler.js:51:30)\n at ReactiveEffect.componentUpdateFn [as fn] (runtime-core.esm-bundler.js:5410:11)\n at ReactiveEffect.run (reactivity.esm-bundler.js:225:19)\n at ReactiveEffect.runIfDirty (reactivity.esm-bundler.js:263:12)\n at callWithErrorHandling (runtime-core.esm-bundler.js:199:33)\n at flushJobs (runtime-core.esm-bundler.js:408:9)\n```",[2894,2897,2898,2901],{"name":2895,"color":2896},"dx","C39D69",{"name":2853,"color":2854},{"name":2899,"color":2900},"vite","3574D1",{"name":2902,"color":2903},"🔨 p3-minor","FBCA04",31493,"TypeError: Cannot read properties of null (reading 'parentNode') with useFetch","2025-03-21T17:04:23Z","https://github.com/nuxt/nuxt/issues/31493",0.66948575,{"description":2910,"labels":2911,"number":2913,"owner":2862,"repository":2863,"state":2914,"title":2915,"updated_at":2916,"url":2917,"score":2918},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.8.2\r\n- Builder: -\r\n- User Config: runtimeConfig, compatibilityDate, devtools, postcss, css, modules, colorMode, alias\r\n- Runtime Modules: @nuxt/ui@2.18.4, @nuxt/image@1.7.0, @pinia/nuxt@0.5.3\r\n- Build Modules: -\n\n### Version\n\nv2.18.2\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-8zjjv5?file=app.vue\n\n### Description\n\nThe :empty-state prop of the UTable component currently does not accept null as a valid value, despite [documentation](https://ui.nuxt.com/components/table#empty) suggesting that it should. This restriction leads to TypeScript errors when attempting to set the :empty-state prop to null.\r\n\r\nWhen trying to set :empty-state to null, the following TypeScript error occurs:\r\n\r\n`Type 'null' is not assignable to type '{ icon: string; label: string; }'.`\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2912],{"name":2853,"color":2854},2043,"closed",":empty-state Prop Type Should Accept null in TypeScript","2024-11-12T17:12:34Z","https://github.com/nuxt/ui/issues/2043",0.6368626,{"description":2920,"labels":2921,"number":2933,"owner":2862,"repository":2862,"state":2914,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.7.4\r\n- CLI Version: 3.9.0\r\n- Nitro Version: 2.6.3\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: devtools, modules, typescript\r\n- Runtime Modules: @nuxtseo/module@2.0.0-beta.15\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\n\r\n- minimal changes to nuxt config adding `typeCheck: true` and `compilerOptions.noUncheckedIndexedAccess: true`\r\n\r\nhttps://stackblitz.com/edit/github-vdxk2t?file=nuxt.config.ts\r\n\r\n### Describe the bug\r\n\r\nThis highlights an issue when trying to use tsconfig features e.g. `noUncheckedIndexedAccess` or `noUnusedLocals` etc. in a nuxt project to provide stricter code conformance. Any nuxt module you have installed will also be checked for these same rules.\r\n\r\nThis effectively means you cannot use any of the tsconfig rules for the risk of a module developer not adhering to those same standards.\r\n\r\nNuxt should not be type checking any installed modules as part of build with the same tsconfig rules defined at the project level. Providing access to all tsconfig properties is misleading as they effectively don't work with the nuxt ecosystem unless you have a raw project.\r\n\r\nThe repro and logs below show how this fails for the `@nuxtseo/module` module but this error is present in a number of modules I have tried to use e.g. `content`\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n```shell-script\r\nERROR 21:54:09\r\n ERROR(vue-tsc) Type '{ icon: string; label: false; ariaLabel: string | undefined; current?: boolean | undefined; disabled?: boolean | undefined; to?: string | undefined; separator?: string | undefined; hideSeparator?: boolean | undefined; ui?: { ...; } | undefined; }' is not assignable to type 'BreadcrumbItemProps'.\r\n Types of property 'to' are incompatible.\r\n Type 'string | undefined' is not assignable to type 'string'.\r\n Type 'undefined' is not assignable to type 'string'.\r\n FILE /home/projects/github-vdxk2t/node_modules/nuxt-seo-ui/dist/runtime/components/Breadcrumb.vue:46:5\r\n\r\n 44 | }\r\n 45 | if (props.homeIcon) {\r\n > 46 | items[0] = {\r\n | ^^^^^^^^\r\n 47 | ...items[0],\r\n 48 | icon: 'material-symbols:home-outline-rounded',\r\n 49 | label: false,\r\n\r\n[vue-tsc] Found 1 error. Watching for file changes. (x3)\r\n```\r\n```\r\n",[2922,2925,2928,2931,2932],{"name":2923,"color":2924},"discussion","538de2",{"name":2926,"color":2927},"types","2875C3",{"name":2929,"color":2930},"3.x","29bc7f",{"name":2853,"color":2854},{"name":2902,"color":2903},23609,"`typeCheck` reports errors from modules when using `tsconfig` rules","2023-11-30T07:26:56Z","https://github.com/nuxt/nuxt/issues/23609",0.63879466,{"description":2939,"labels":2940,"number":2951,"owner":2862,"repository":2862,"state":2914,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### 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_",[2941,2942,2945,2948],{"name":2929,"color":2930},{"name":2943,"color":2944},"workaround available","11376d",{"name":2946,"color":2947},"upstream","E8A36D",{"name":2949,"color":2950},"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.6539027,{"description":2957,"labels":2958,"number":2961,"owner":2862,"repository":2863,"state":2914,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### 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```",[2959,2960],{"name":2853,"color":2854},{"name":2856,"color":2857},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.6551474,{"description":2967,"labels":2968,"number":2971,"owner":2862,"repository":2863,"state":2914,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### 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```",[2969,2970],{"name":2853,"color":2854},{"name":2856,"color":2857},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.65755063,{"description":2977,"labels":2978,"number":2986,"owner":2862,"repository":2862,"state":2914,"title":2987,"updated_at":2988,"url":2989,"score":2990},"### 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_",[2979,2980,2981,2982,2983],{"name":2926,"color":2927},{"name":2929,"color":2930},{"name":2943,"color":2944},{"name":2853,"color":2854},{"name":2984,"color":2985},"schema","1d76db",15750,"Invalid types for `ModuleOptions` in `NuxtModule`","2023-01-22T00:09:19Z","https://github.com/nuxt/nuxt/issues/15750",0.6603894,["Reactive",2992],{},["Set"],["ShallowReactive",2995],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f8ESXHD7rhw8OuKr9dJYrh-BOiiGnodgOGFI811XFrWY":-1},"/nuxt/ui/1710"]