\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```",[3045,3046],{"name":3033,"color":3034},{"name":3047,"color":3048},"v3","49DCB8",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.6630116,{"description":3055,"labels":3056,"number":3063,"owner":3023,"repository":3036,"state":3037,"title":3064,"updated_at":3065,"url":3066,"score":3067},"### 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",[3057,3058,3061],{"name":3033,"color":3034},{"name":3059,"color":3060},"closed-by-bot","ededed",{"name":3062,"color":3060},"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.6649565,{"description":3069,"labels":3070,"number":3075,"owner":3023,"repository":3023,"state":3037,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v18.20.3\r\n- Nuxt Version: 3.13.1\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: compatibilityDate, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-z6juqt?file=components%2FTest.vue\r\n\r\n`npm run typecheck` in terminal\r\n\r\n```\r\ncomponents/Test.vue:8:17 - error TS2339: Property 'optionalStr' does not exist on type 'CreateComponentPublicInstanceWithMixins\u003CToResolvedProps\u003C{}, {}>, {}, {}, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, {}, VNodeProps & AllowedComponentProps & ComponentCustomProps & Readonly\u003C...> & Readonly\u003C...>, ... 16 more ..., {}>'.\r\n\r\n8 \u003Cspan v-if=\"optionalStr\">{{ optionalStr }}\u003C/span>\r\n ~~~~~~~~~~~\r\n```\n\n### Describe the bug\n\nAfter upgrading from Nuxt 3.12.3 to 3.13.2, these TS errors showed up in every component that only uses optional props. The error disappears if we add a single required prop or enable TS strict mode.\n\n### Additional context\n\nThe issue doesn't seem to be present in a pure Vue/Vite project:\r\n\r\nhttps://stackblitz.com/edit/vitejs-vite-ece16d?file=src%2Fcomponents%2FHelloWorld.vue\n\n### Logs\n\n_No response_",[3071,3072],{"name":3020,"color":3021},{"name":3073,"color":3074},"possible regression","B90A42",29041,"Components with only optional props lose props type if strict mode is disabled","2024-09-23T10:12:23Z","https://github.com/nuxt/nuxt/issues/29041",0.6700303,{"description":3081,"labels":3082,"number":3090,"owner":3023,"repository":3023,"state":3037,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v20.11.0\r\n- Nuxt Version: 3.10.2\r\n- CLI Version: 3.10.1\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.4\r\n- Builder: -\r\n- User Config: `devServer`, `nitro`, `routeRules`, `components`, `build`, `modules`, `primevue`, `experimental`, `typescript`, `devtools`\r\n- Runtime Modules: `@vueuse/nuxt@10.8.0`, `nuxt-svgo@4.0.0`, `nuxt-primevue@0.3.0`, `@nuxt/image@1.3.0`, `@pinia/nuxt@0.5.1`\r\n- Build Modules: -\r\n\r\n### Reproduction\r\n\r\n✅ `3.9.3`: https://stackblitz.com/edit/nuxt-3-9-3-typecheck \r\n❌ `3.10.3`: https://stackblitz.com/edit/nuxt-3-10-typecheck \r\n\r\n### Describe the bug\r\n\r\nAfter upgrading Nuxt from `v3.9.3` to `v3.10.2` some typings are not detected anymore. It looks like it's related to third-party packages with `exports` config in the `package.json`. I discovered that `moduleResolution` has been changed in the automatically generated `tsconfig.json` file.\r\n\r\n### Additional context\r\n\r\nSetting `moduleResolution` as `Node` should fix the problem. In the Nuxt `3.10` it was changed to `Bundler`, which looks like a breaking change in some cases.\r\n\r\nIn our case, we have a multifile/multitype package that stopped working during type-checking (the build is okay). I tried to set `moduleResolution` to `Node` back in Nuxt 3.10 and it seems like the type-checking issue has been fixed.\r\n\r\n```json5\r\n{\r\n // https://nuxt.com/docs/guide/concepts/typescript\r\n \"extends\": \"./.nuxt/tsconfig.json\",\r\n\r\n \"compilerOptions\": {\r\n \"moduleResolution\": \"Node\"\r\n }\r\n}\r\n```\r\n\r\n#25230 can be related, but I'm unsure because the Nuxt version there is `3.9`.\r\n\r\n### Logs\r\n\r\n_No response_",[3083,3086,3089],{"name":3084,"color":3085},"types","2875C3",{"name":3087,"color":3088},"3.x","29bc7f",{"name":3020,"color":3021},25929,"Typechecking issue after Nuxt upgrading 3.9 -> 3.10","2024-03-08T11:49:58Z","https://github.com/nuxt/nuxt/issues/25929",0.67555374,{"description":3096,"labels":3097,"number":3104,"owner":3023,"repository":3023,"state":3037,"title":3105,"updated_at":3106,"url":3107,"score":3108},"https://github.com/eslint/eslint/issues/14172 https://github.com/nuxt-community/eslint-module/issues/59 That's why I should do it\r\n\r\nThis is my configuration\r\n \r\n\"dependencies\": {\r\n \"@nuxtjs/auth-next\": \"^5.0.0-1616003482.75c20e6\",\r\n \"@nuxtjs/axios\": \"^5.13.1\",\r\n \"@nuxtjs/component-cache\": \"^1.1.6\",\r\n \"@nuxtjs/proxy\": \"^2.1.0\",\r\n \"@vue/shared\": \"^3.0.7\",\r\n \"axios-extensions\": \"^3.1.3\",\r\n \"core-js\": \"^3.8.3\",\r\n \"element-ui\": \"^2.15.0\",\r\n \"lodash\": \"^4.17.21\",\r\n \"lru-cache\": \"^6.0.0\",\r\n \"qiniu\": \"^7.3.2\",\r\n \"nuxt\": \"^2.15.6\",\r\n \"qrcodejs2\": \"^0.0.2\",\r\n \"resize-observer-polyfill\": \"^1.5.1\",\r\n \"swiper\": \"5.x\",\r\n \"uuid\": \"^8.3.2\",\r\n \"vue-awesome-swiper\": \"^4.1.1\"\r\n },\r\n \"devDependencies\": {\r\n \"@nuxt/types\": \"^2.15.3\",\r\n \"@nuxtjs/eslint-config\": \"^5.0.0\",\r\n \"@nuxtjs/eslint-module\": \"^3.0.2\",\r\n \"@nuxtjs/style-resources\": \"^1.0.0\",\r\n \"@nuxtjs/stylelint-module\": \"^4.0.0\",\r\n \"babel-eslint\": \"^10.1.0\",\r\n \"babel-plugin-component\": \"^1.1.1\",\r\n \"cross-env\": \"^7.0.3\",\r\n \"eslint\": \"^7.18.0\",\r\n \"eslint-plugin-nuxt\": \"^2.0.0\",\r\n \"eslint-plugin-vue\": \"^7.5.0\",\r\n \"postcss-preset-env\": \"^6.7.0\",\r\n \"sass\": \"^1.32.8\",\r\n \"sass-loader\": \"10\",\r\n \"stylelint\": \"^13.9.0\",\r\n \"stylelint-config-standard\": \"^20.0.0\"\r\n }",[3098,3100,3101],{"name":3062,"color":3099},"ffffff",{"name":3020,"color":3021},{"name":3102,"color":3103},"2.x","d4c5f9",9314,"upgrade version TypeError: Cannot read property 'value' of null","2023-01-22T15:44:51Z","https://github.com/nuxt/nuxt/issues/9314",0.68236333,{"description":3110,"labels":3111,"number":3121,"owner":3023,"repository":3023,"state":3037,"title":3122,"updated_at":3123,"url":3124,"score":3125},"### Environment\n\nStackblitz\r\n\r\n````\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.10.3\r\n- CLI Version: 3.10.1\r\n- Nitro Version: -\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: extends\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n````\n\n### Reproduction\n\nhttps://stackblitz.com/github/martinszeltins/found-nuxt-components-issue?file=app.vue\n\n### Describe the bug\n\nWhen I add this module to my modules array in nuxt.config.ts then I lose all typings for my components _(for both local and 3rd party components)._ It shows that components have type of `unknown`. Before I add this module, everything works.\r\n\r\n**nuxt.config.ts** 👇️\r\n```diff\r\nmodules: [\r\n+ '@nuxtjs/i18n', // This breaks all auto-import component typings (components not recognized anymore)\r\n '@vueuse/nuxt',\r\n 'nuxt-primevue'\r\n],\r\n```\r\n\r\nIf I remove it from my modules array then everything works again.\r\n\r\n**Screenshot before adding the module (everything works):** 👍️ 👇️\r\n\r\n\r\n\r\n**Screenshot after adding the module (type unknown):** ❌ 👇️\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3112,3113,3114,3117,3118],{"name":3084,"color":3085},{"name":3087,"color":3088},{"name":3115,"color":3116},"workaround available","11376d",{"name":3033,"color":3034},{"name":3119,"color":3120},"upstream","E8A36D",26214,"Adding `@nuxtjs/i18n` to Nuxt breaks component types (shows unknown)","2024-05-27T10:28:40Z","https://github.com/nuxt/nuxt/issues/26214",0.6835472,{"description":3127,"labels":3128,"number":3131,"owner":3023,"repository":3036,"state":3037,"title":3132,"updated_at":3133,"url":3134,"score":3135},"### 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```",[3129,3130],{"name":3033,"color":3034},{"name":3047,"color":3048},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.6836997,{"description":3137,"labels":3138,"number":3142,"owner":3023,"repository":3023,"state":3037,"title":3143,"updated_at":3144,"url":3145,"score":3146},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.7.0\n- Nuxt Version: 3.13.2\n- CLI Version: 3.15.0\n- Nitro Version: 2.9.7\n- Package Manager: pnpm@9.7.0\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-a4nfq9\n\n1. Run `pnpm nuxt typecheck` - you will see type error reported in `app.vue` which is there deliberately.\n2. Delete `components/no-op.vue`\n3. Run `pnpm nuxt typecheck` - no type errors are reported anymore.\n\n### Describe the bug\n\nType check doesn't happen in SFC templates if the project doesn't have any custom component under `components/` directory.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3139,3140,3141],{"name":3084,"color":3085},{"name":3020,"color":3021},{"name":3119,"color":3120},30173,"No type check in SFC templates if components directory is empty","2025-05-31T15:32:20Z","https://github.com/nuxt/nuxt/issues/30173",0.6847787,["Reactive",3148],{},["Set"],["ShallowReactive",3151],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbXGTT92GrSEBd3yhkrdk_mLLdJ4RyDjp_A8YQh9UBfE":-1},"/nuxt/ui/2868"]