\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```",[3134,3137],{"name":3135,"color":3136},"bug","d73a4a",{"name":3138,"color":3139},"v3","49DCB8",4166,"nuxt","ui","closed","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.65919375,{"description":3149,"labels":3150,"number":3153,"owner":3141,"repository":3142,"state":3143,"title":3154,"updated_at":3155,"url":3156,"score":3157},"### 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```",[3151,3152],{"name":3135,"color":3136},{"name":3138,"color":3139},4019,"Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.6624266,{"description":3159,"labels":3160,"number":3173,"owner":3141,"repository":3141,"state":3143,"title":3174,"updated_at":3175,"url":3176,"score":3177},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v20.9.0\r\n- Nuxt Version: 3.10.1\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: yarn@1.22.19\r\n- Builder: -\r\n- User Config: devtools, experimental, runtimeConfig, app, modules, fontLoader, css, vite, typescript, i18n, nuxt-jsonld, primevue, image\r\n- Runtime Modules: @nuxt/image@1.3.0, @nuxtjs/eslint-module@4.1.0, @nuxtjs/i18n@8.0.2, @nuxtjs/robots@3.0.0, @nuxtjs/strapi@1.11.0, @nuxtjs/tailwindcss@6.11.3, @pinia/nuxt@0.5.1, @vueuse/nuxt@10.7.2, nuxt-icons@3.2.1, nuxt-jsonld@2.0.8, nuxt-primevue@0.2.2, @vee-validate/nuxt@4.12.5, nuxt-font-loader@2.3.5\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-1psnfn?file=types%2Ftest.types.ts\n\n### Describe the bug\n\nAfter updating Nuxt to the latest version (3.10.1), it no longer recognises types imported from external libraries (in my case, strapi and i18n).\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3161,3164,3167,3170],{"name":3162,"color":3163},"types","2875C3",{"name":3165,"color":3166},"3.x","29bc7f",{"name":3168,"color":3169},"pending triage","E99695",{"name":3171,"color":3172},"upstream","E8A36D",25674,"Types Error for types exported from external libraries.","2024-02-07T14:59:59Z","https://github.com/nuxt/nuxt/issues/25674",0.6692364,{"description":3179,"labels":3180,"number":3185,"owner":3141,"repository":3141,"state":3143,"title":3186,"updated_at":3187,"url":3188,"score":3189},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-qagkk8\n\n### Describe the bug\n\nHello, \n\nI'm running into an issue where typechecking is no longer working in `nuxt@3.14.1592`. \n\nTo reproduce the issue: \n\n1. In the minimal reproduction stackblitz, open the the terminal \n2. Execute `npm install` (to trigger `nuxt prepare`) \n3. Run the command `npm run check-types` (which is just a wrapper for `nuxt typecheck`) \n\n**Result**: The built-in Nuxt 3 typechecking functionality is broken. When the command from (3) is run, an error is thrown that the search string `\"/supportedTSExtensions = .*(?=;)/\"` is not found. \n\n**Desired behaviour**: I'd like to fix the issue so that typechecking works again. We use this in CI, and it's an important alarm bell for us. \n\n### Additional context\n\n\n\n\n\n### Logs\n\n```shell-script\n'Search string not found: \"/supportedTSExtensions = .*(?=;)/\"'\n\n ERROR Command failed with exit code 1: npx -p vue-tsc -p typescript vue-tsc --noEmit 11:35:21 AM\n\n at new ExecaError (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:1188:1)\n at getFinalError (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:1158:9)\n at makeError (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:3638:16)\n at getAsyncResult (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:7867:4)\n at handlePromise (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/index3.mjs:7850:17)\n at async Object.run (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/chunks/typecheck.mjs:112:9)\n at async runCommand$1 (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.f8a4d1b7.mjs:1679:16)\n at async runCommand$1 (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.f8a4d1b7.mjs:1670:11)\n at async runMain$1 (/home/.npm/_npx/b95349761371180e/node_modules/nuxi/dist/shared/nuxi.f8a4d1b7.mjs:1808:7)\n```",[3181,3182],{"name":3168,"color":3169},{"name":3183,"color":3184},"possible regression","B90A42",30154,"Built-in typechecking fails on `nuxt@3.14.1592`","2024-12-05T17:50:54Z","https://github.com/nuxt/nuxt/issues/30154",0.6755445,{"description":3191,"labels":3192,"number":3196,"owner":3141,"repository":3141,"state":3143,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### 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_",[3193,3194,3195],{"name":3162,"color":3163},{"name":3165,"color":3166},{"name":3168,"color":3169},25929,"Typechecking issue after Nuxt upgrading 3.9 -> 3.10","2024-03-08T11:49:58Z","https://github.com/nuxt/nuxt/issues/25929",0.67937577,{"description":3202,"labels":3203,"number":3211,"owner":3141,"repository":3141,"state":3143,"title":3212,"updated_at":3213,"url":3214,"score":3215},"### 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_",[3204,3205,3206,3209,3210],{"name":3162,"color":3163},{"name":3165,"color":3166},{"name":3207,"color":3208},"workaround available","11376d",{"name":3135,"color":3136},{"name":3171,"color":3172},26214,"Adding `@nuxtjs/i18n` to Nuxt breaks component types (shows unknown)","2024-05-27T10:28:40Z","https://github.com/nuxt/nuxt/issues/26214",0.68003935,{"description":3217,"labels":3218,"number":3225,"owner":3141,"repository":3141,"state":3143,"title":3226,"updated_at":3227,"url":3228,"score":3229},"### Environment\n\nStackblitz + WSL\r\n\r\nWSL Info: \r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.17.1\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: npm@9.8.1\r\n- Builder: vite\r\n- User Config: devtools, typescript, modules, components, graphqlMiddleware, css, postcss, runtimeConfig, app, routeRules\r\n- Runtime Modules: @nuxt/image@1.0.0-rc.1, nuxt-graphql-middleware@4.0.0-beta.3\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-gscpb2?file=server%2Fapi%2Fhello.ts\n\n### Describe the bug\n\nPassing the event to useRuntimeConfig in server API routes causes typechecking to fail, despite being [encouraged in the docs](https://nuxt.com/docs/guide/going-further/runtime-config#server-routes)\r\n\r\n\r\n1. Create an API route that uses `useRuntimeConfig(event)`\r\n2. Run `npx nuxi typecheck` (or similar) \r\n3. Will fail with `Expected 0 arguments, but got 1.`\r\n\r\nNote that stackblitz flags this as an error right in the editor too. \r\n\r\n\n\n### Additional context\n\n1. ESLint + VS Code's internal typescript seem to be able to narrow the right type. (Clicking \"Jump to Type Definition\" navigates to the right type which accepts events). I'm not sure why typechecking is failing there. \n\n### Logs\n\n```shell-script\nerror TS2554: Expected 0 arguments, but got 1.\r\n\r\nconst { apiUrl } = useRuntimeConfig(event);\r\n \r\n```\n```\n",[3219,3220,3221,3222],{"name":3162,"color":3163},{"name":3165,"color":3166},{"name":3135,"color":3136},{"name":3223,"color":3224},"🔨 p3-minor","FBCA04",24095,"API endpoints useRuntimeConfig(event) throws type errors with nuxt typecheck","2024-02-09T12:16:29Z","https://github.com/nuxt/nuxt/issues/24095",0.6803356,{"description":3231,"labels":3232,"number":3235,"owner":3141,"repository":3141,"state":3143,"title":3236,"updated_at":3237,"url":3238,"score":3239},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 4.0.2\n- CLI Version: 3.27.0\n- Nitro Version: 2.12.4\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: compatibilityDate, devtools, typescript\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\n[reproduction](https://stackblitz.com/edit/github-qvzrtdvv)\n\n### Describe the bug\n\nNuxt will not typecheck the codebase when setting the `typescript.typeCheck` to `build` on nuxt config.\n\nI have placed both typescript errors in `app.vue` and `server/routes/health.ts` files and no errors are thrown on build. Running nuxt typecheck directly will only throw the app.vue error and not the one on the server directory.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3233,3234],{"name":3162,"color":3163},{"name":3168,"color":3169},32823,"[v4]: typecheck on build does not work","2025-08-02T12:14:14Z","https://github.com/nuxt/nuxt/issues/32823",0.68231726,{"description":3241,"labels":3242,"number":3248,"owner":3141,"repository":3141,"state":3143,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.16.1\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.1\r\n- Package Manager: yarn@3.5.1\r\n- Builder: vite\r\n- User Config: extends, debug, ssr, routeRules, experimental, runtimeConfig, typescript, css, i18n, modules, alias, vite\r\n- Runtime Modules: nuxt-icon@^0.4.1, @nuxtjs/i18n@8.0.0-beta.12, @vueuse/nuxt@10.2.0, @nuxt/devtools@0.6.3, @nuxtjs/eslint-module@^4.1.0, nuxt-vitest@^0.8.5\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nAdd the nuxt-icon module with typecheck enabled.\n\n### Describe the bug\n\nEssentially a regression on: https://github.com/nuxt/nuxt/pull/20526.\r\n\r\nAs noted here: https://github.com/nuxt-modules/icon/issues/86.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3243,3244,3245,3246],{"name":3162,"color":3163},{"name":3165,"color":3166},{"name":3168,"color":3169},{"name":3247,"color":3224},"needs reproduction",21816,"Nuxt `3.6.1` introduces a regression on `AppConfig` types:","2023-09-13T13:03:57Z","https://github.com/nuxt/nuxt/issues/21816",0.68277603,{"labels":3254,"number":3258,"owner":3141,"repository":3141,"state":3143,"title":3259,"updated_at":3260,"url":3261,"score":3262},[3255,3256,3257],{"name":3165,"color":3166},{"name":3135,"color":3136},{"name":3223,"color":3224},13752,"Nuxt3 generated Sites do not pass W3C validator","2023-01-19T17:04:41Z","https://github.com/nuxt/nuxt/issues/13752",0.68456256,["Reactive",3264],{},["Set"],["ShallowReactive",3267],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fUi-xUGAY6lrdJ6_g6okaTR0Cmqgs4NBwH_jHBVh5IEA":-1},"/nuxt/ui/4928"]