\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```",[2908,2909],{"name":2857,"color":2858},{"name":2860,"color":2861},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.6334311,{"description":2916,"labels":2917,"number":2923,"owner":2866,"repository":2866,"state":2890,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### 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_",[2918,2919,2920],{"name":2880,"color":2881},{"name":2883,"color":2884},{"name":2921,"color":2922},"pending triage","E99695",25929,"Typechecking issue after Nuxt upgrading 3.9 -> 3.10","2024-03-08T11:49:58Z","https://github.com/nuxt/nuxt/issues/25929",0.64152616,{"description":2929,"labels":2930,"number":2934,"owner":2866,"repository":2867,"state":2890,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Environment\n\n```\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.9\n- Package Manager: bun@1.2.9\n- Builder: -\n- User Config: ssr, imports, devtools, experimental, future, compatibilityDate, alias, runtimeConfig, devServer, app, css, modules, build, hooks, dayjs, ui, typescript\n- Runtime Modules: @nuxt/eslint@1.3.0, @vueuse/nuxt@13.1.0, @nuxt/test-utils/module@3.17.2, dayjs-nuxt@2.1.11, nuxt-svgo@4.0.17, @nuxt/ui-pro@3.1.0, @pinia/nuxt@0.11.0, @pinia/colada-nuxt@0.1.1, @nuxt/image@1.10.0\n- Build Modules: -\n```\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.0\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/empty-fast-5xtcmy?workspaceId=ws_SD2P6X4ufyWkm2P3aqoQA6\n\n### Description\n\nbetween version 3.0.2 and 3.1.0 the content container for the menu items is no longer filling the width.\n\n### Additional context\n\n__no response__\n\n### Logs\n\n```shell-script\n\n```",[2931,2932,2933],{"name":2857,"color":2858},{"name":2860,"color":2861},{"name":2863,"color":2864},3987,"[NavigationMenu] Regression - Update","2025-05-02T09:52:45Z","https://github.com/nuxt/ui/issues/3987",0.6443446,{"description":2940,"labels":2941,"number":2947,"owner":2866,"repository":2867,"state":2890,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v23.10.0`\n- Nuxt Version: `3.17.0`\n- CLI Version: `3.25.0`\n- Nitro Version: `2.11.10`\n- Package Manager: `pnpm@10.10.0`\n- Builder: `-`\n- User Config: `-`\n- Runtime Modules: `-`\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\nAny use of tabs slots\n\n### Description\n\nAfter upgrading all dependencies to the latest version and keeping NuxtUI v3.0.2 everything is ok but when in addition to other dependencies I also upgrade NuxtUI to the latest version v3.1.0 then TS errors appear as in the attached screen shot so I guess again a step backwards from the recent fixes with slots ;p\n\n\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2942,2943,2946],{"name":2857,"color":2858},{"name":2944,"color":2945},"duplicate","cfd3d7",{"name":2860,"color":2861},4005,"Tab slots types error","2025-04-28T10:54:47Z","https://github.com/nuxt/ui/issues/4005",0.6484432,{"description":2953,"labels":2954,"number":2957,"owner":2866,"repository":2867,"state":2890,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### 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/weathered-resonance-r7wcmc?file=%2Fapp%2Fpages%2Findex.vue\n\n### Description\n\nThe carousel item generic type does not seem to work anymore. Unfortunately I'm not sure, which is the last version of nuxt ui where it works :(\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n'item' is possibly 'null'. \nProperty 'title' does not exist on type 'string | number | Record\u003Cstring, any>'.\n Property 'title' does not exist on type 'string'.\n```",[2955,2956],{"name":2857,"color":2858},{"name":2860,"color":2861},4020,"Generic Type Issue with Carousel Component","2025-04-29T15:39:36Z","https://github.com/nuxt/ui/issues/4020",0.6484633,{"description":2963,"labels":2964,"number":2971,"owner":2866,"repository":2866,"state":2890,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Environment\r\n\r\n- Operating System: Darwin\r\n- Node Version: v18.14.0\r\n- Nuxt Version: 3.6.1\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@1.22.19\r\n- Builder: vite\r\n- User Config: -\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n\r\n**VsCode 1.79.2**\r\n- vscode.typescript-language-features: disabled\r\n- Vue.volar: 1.8.3, enabled\r\n- Vue.vscode-typescript-vue-plugin: 1.8.3, enabled\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/niklas-may/nuxt-module-issue-reproduction\r\n\r\n### Describe the bug\r\n\r\n**Preface**\r\n_Thank you for your amazing work on Nuxt! I am not sure where this issue is best raised, Nuxt, VsCode or Vue. But due to the special typescript tooling with auto imports, I thought it's best to start here, and would be happy to hear if anybody observed a similar behaviour or has a solution._ \r\n\r\n**Description**\r\nWhen I open `~/.nuxt/components.d.ts` in VsCode and hover over an imported component, VsCode IntelliSense popover displays the correct types for this component.\r\nBut when I use the component in any other components template block, for example `~/app.vue`, the typing is missing the prop types.\r\n\r\n### Component and Type Definitions\r\n\r\n`~/../src/runtime/MyButton.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv style=\"border: 1px solid pink\">\r\n \u003Cslot />\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript setup lang=\"ts\">\r\nwithDefaults(\r\n defineProps\u003C{\r\n variant: \"fill\" | \"ghost\";\r\n }>(),\r\n { variant: \"fill\" }\r\n);\r\n\u003C/script>\r\n```\r\n\r\n`~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\ndeclare module 'vue' {\r\n export interface GlobalComponents {\r\n //...\r\n 'MyButton': typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n //...\r\n }\r\n}\r\n\r\nexport const MyButton: typeof import(\"../../src/runtime/components/MyButton.vue\")['default']\r\n\r\nexport const componentNames: string[]\r\n```\r\n\r\n\r\n### Correct Intellisense\r\n\r\nVsCode popopver hovering `'MyButton'` in `~/.nuxt/components.d.ts`\r\n\r\n```TypeScript\r\n(property) GlobalComponents['MyButton']: __VLS_WithTemplateSlots\u003CDefineComponent\u003C{\r\n variant: {\r\n type: PropType\u003C\"fill\" | \"ghost\">;\r\n required: true;\r\n default: string;\r\n };\r\n}, {}, unknown, {}, {}, ComponentOptionsMixin, ComponentOptionsMixin, ... 5 more ..., {}>, {\r\n ...;\r\n}>\r\n````\r\n\r\n### Wrong Intellisense\r\n\r\nVsCode popopver hovering `\u003CMyButton />` in the template block of `~/app.vue` (or any other template)\r\n\r\n```TypeScript\r\n(property) 'MyButton': DefineComponent\u003C{}, {}, any>\r\n```\r\n\r\n### Additional context\r\n\r\nThe above example is the current state of the reproduction repo. But a different, but similar behavior happened in other reports (for example a yarn workspace repo). Strange enough, sometimes, it works fine...\r\n\r\n### Logs\r\n\r\n_No response_",[2965,2966,2967,2968],{"name":2880,"color":2881},{"name":2883,"color":2884},{"name":2921,"color":2922},{"name":2969,"color":2970},"upstream","E8A36D",21933,"Component appears to be untyped in template block","2023-12-12T14:36:22Z","https://github.com/nuxt/nuxt/issues/21933",0.6544255,{"description":2977,"labels":2978,"number":2984,"owner":2866,"repository":2866,"state":2890,"title":2985,"updated_at":2986,"url":2987,"score":2988},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.18.0`\r\n- Nuxt Version: `3.2.2`\r\n- Nitro Version: `2.2.3`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `sanity`, `app`, `components`, `css`, `imports`, `modules`, `routeRules`, `hooks`, `runtimeConfig`, `meta`, `vite`\r\n- Runtime Modules: `@nuxt/image-edge@1.0.0-27913696.5d122a3`, `@nuxtjs/sanity@1.6.0`, `@pinia/nuxt@0.4.6`, `@pinia-plugin-persistedstate/nuxt@1.0.0`, `@vueuse/nuxt@9.12.0`, `nuxt-icons@3.1.0`, `nuxt-schema-org@2.1.2`, `vite-plugin-vue-type-imports/nuxt`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nWill add later\n\n### Describe the bug\n\nI've tried updating to `v3.2.3` this morning and was faced with `Type instantiation is excessively deep and possibly infinite` in my nuxt config (culprint are the `modules` afaik) - looking at https://github.com/nuxt/nuxt/issues?q=is%3Aissue+Type+instantiation+is+excessively+deep+and+possibly+infinite+is%3Aclosed this was fixed in the past, so potentially creeped back in somehow?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2979,2980,2981],{"name":2883,"color":2884},{"name":2857,"color":2858},{"name":2982,"color":2983},"❗ p4-important","D93F0B",19416,"Possible type regression in `v3.2.3`","2023-03-14T15:38:19Z","https://github.com/nuxt/nuxt/issues/19416",0.65593255,["Reactive",2990],{},["Set"],["ShallowReactive",2993],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fXNeIK2ET3LNKVEBtLgWo6eqTcQl6REaufPh0D2Qd0u8":-1},"/nuxt/ui/4029"]