\n\nWhere I use config then, it shows me typing error.\nWhen I switch to the legacy tsconfig, typing issue are gone.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nTypecheck summary: \n\n\n\napp/layouts/default.vue:35:33 - error TS2339: Property 'title' does not exist on type '{}'.\n\n35 title: appConfig.information?.title,\n ~~~~~\n\napp/layouts/default.vue:36:39 - error TS2339: Property 'description' does not exist on type '{}'.\n\n36 description: appConfig.information?.description,\n ~~~~~~~~~~~\n\napp/layouts/default.vue:39:36 - error TS2339: Property 'socials' does not exist on type '{}'.\n\n39 github: appConfig.information?.socials?.github,\n ~~~~~~~\n\napp/layouts/default.vue:40:38 - error TS2339: Property 'socials' does not exist on type '{}'.\n\n40 linkedin: appConfig.information?.socials?.linkedin,\n ~~~~~~~\n\napp/layouts/default.vue:41:40 - error TS2339: Property 'birthdate' does not exist on type '{}'.\n\n41 isBirthday: appConfig.information?.birthdate ? isBirthday(appConfig.information?.birthdate) : false,\n ~~~~~~~~~\n\napp/layouts/default.vue:41:86 - error TS2339: Property 'birthdate' does not exist on type '{}'.\n\n41 isBirthday: appConfig.information?.birthdate ? isBirthday(appConfig.information?.birthdate) : false,\n ~~~~~~~~~\n\napp/layouts/default.vue:44:27 - error TS2339: Property 'icons' does not exist on type '{}'.\n\n44 normal: appConfig.ui?.icons?.normal as string[] ?? [],\n ~~~~~\n\napp/layouts/default.vue:45:29 - error TS2339: Property 'icons' does not exist on type '{}'.\n\n45 birthday: appConfig.ui?.icons?.birthday as string[] ?? [],\n ~~~~~\n\napp/middleware/title.global.ts:5:28 - error TS2571: Object is of type 'unknown'.\n\n5 const appConfigTitle = useAppConfig().information.title;\n ~~~~~~~~~~~~~~~~~~~~~~~~~~\n\napp/pages/index.vue:14:62 - error TS2339: Property 'messages' does not exist on type '{}'.\n\n14 const messages = useState('randomIndex', () => appConfig.ui?.messages?.sort(() => Math.random() - 0.5))\n ~~~~~~~~\n\nnuxt.schema.ts:3:16 - error TS2304: Cannot find name 'defineNuxtSchema'.\n\n3 export default defineNuxtSchema({\n ~~~~~~~~~~~~~~~~\n\nnuxt.schema.ts:3:16 - error TS2304: Cannot find name 'defineNuxtSchema'.\n\n3 export default defineNuxtSchema({\n ~~~~~~~~~~~~~~~~\n\nnuxt.schema.ts:3:16 - error TS2304: Cannot find name 'defineNuxtSchema'.\n\n3 export default defineNuxtSchema({\n ~~~~~~~~~~~~~~~~\n```",[3156,3159],{"name":3157,"color":3158},"pending triage","E99695",{"name":3160,"color":3161},"possible regression","B90A42",32768,"useAppConfig lose types from nuxt schema with new tsconfig","2025-07-25T22:51:01Z","https://github.com/nuxt/nuxt/issues/32768",0.6228295,{"description":3168,"labels":3169,"number":3180,"owner":3146,"repository":3146,"state":3148,"title":3181,"updated_at":3182,"url":3183,"score":3184},"### Environment\n\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-stl7dc?file=nuxt.config.ts\n\n### Describe the bug\n\nNuxt generates invalid types for an array of objects inside `runtimeConfig`\r\nWhen we set `typeCheck: true` and would like to return the config in some function the vue-tsc throws an error.\r\n\r\nI was also trying to manually type the runtimeConfig according to the instructions but looks like typescript doesn't care about it.\r\nhttps://nuxt.com/docs/guide/going-further/runtime-config#manually-typing-runtime-config\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3170,3173,3176,3177],{"name":3171,"color":3172},"types","2875C3",{"name":3174,"color":3175},"workaround available","11376d",{"name":3140,"color":3141},{"name":3178,"color":3179},"upstream","E8A36D",12400,"Nuxt generates invalid types for an array of objects in runtimeConfig - nuxt.config.ts","2025-01-18T13:52:52Z","https://github.com/nuxt/nuxt/issues/12400",0.640747,{"description":3186,"labels":3187,"number":3193,"owner":3146,"repository":3147,"state":3148,"title":3194,"updated_at":3195,"url":3196,"score":3197},"### 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```",[3188,3189,3192],{"name":3140,"color":3141},{"name":3190,"color":3191},"v3","49DCB8",{"name":3143,"color":3144},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.64426374,{"description":3199,"labels":3200,"number":3207,"owner":3146,"repository":3147,"state":3208,"title":3209,"updated_at":3210,"url":3211,"score":3212},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.8\n- Package Manager: yarn@4.8.1\n- Builder: -\n- User Config: compatibilityDate, imports, components, devtools, modules, css, fonts, ui\n- Runtime Modules: @nuxt/eslint@1.2.0, @nuxt/fonts@0.11.0, @nuxt/image@1.10.0, @nuxt/test-utils@3.17.2, @nuxt/ui@3.0.2\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.2\n\n### Reproduction\n\nhttps://github.com/nuxt/ui/blob/v3/src/theme/button.ts\n\n### Description\n\nI want to customize a button variant by `size`, `trailing` and `square` params. It works, but the types are broken.\n\nThe line in the `compoundVariants`:\n`{ size: 'md', trailing: true, square: false, class: { trailingIcon: '-mr-1' } }`\n\nErrors:\n`Type '{ trailingIcon: string; }' is not assignable to type 'string'`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3201,3202,3203,3204],{"name":3140,"color":3141},{"name":3190,"color":3191},{"name":3143,"color":3144},{"name":3205,"color":3206},"stale","ededed",3738,"closed","Incorrect compound button variants types","2025-08-12T11:07:19Z","https://github.com/nuxt/ui/issues/3738",0.6039705,{"description":3214,"labels":3215,"number":3224,"owner":3146,"repository":3146,"state":3208,"title":3225,"updated_at":3226,"url":3227,"score":3228},"### Environment\r\n\r\n```\r\nnpx nuxi info\r\nNuxi 3.2.0 19:47:48\r\n 19:47:50\r\nRootDir: /home/projects/github-z5ryjg 19:47:50\r\nNuxt project info: 19:47:50\r\n\r\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.2.0`\r\n- Nitro Version: `2.2.1`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/github-z5ryjg?file=nuxt.config.ts\r\n\r\n### Describe the bug\r\n\r\nWhen using arrays in `runtimeConfig` (private and public) of `nuxt.config.ts`, TypeScript throws nonsensical errors for the array's elements: `Type 'string' is not assignable to type 'never'.` or `Type 'string' is not assignable to type 'undefined'`.\r\n\r\nWeirdly, the automatically generated types in `.nuxt/types/schema.d.ts` are correct. Manually defining the types doesn't help.\r\n\r\nSince this error also comes up during `nuxt typecheck`, it caused our CI pipeline to fail and we had to disable typechecks for `nuxt.config.ts`.\r\n\r\n### Additional context\r\n\r\nThis error occurred after upgrading from Nuxt 3.0.0 to 3.2.0.\r\n\r\n### Logs\r\n\r\n_No response_",[3216,3217,3220,3221],{"name":3171,"color":3172},{"name":3218,"color":3219},"3.x","29bc7f",{"name":3140,"color":3141},{"name":3222,"color":3223},"❗ p4-important","D93F0B",18925,"Type errors when using arrays in runtimeConfig","2023-02-10T07:50:30Z","https://github.com/nuxt/nuxt/issues/18925",0.6154996,{"description":3230,"labels":3231,"number":3238,"owner":3146,"repository":3146,"state":3208,"title":3239,"updated_at":3240,"url":3241,"score":3242},"### Environment\r\n\r\nOperating System: Windows_NT\r\nNode Version: v18.0.0\r\nNuxt Version: 3.3.3\r\nNitro Version: 2.3.2\r\nPackage Manager: npm@9.4.2\r\nBuilder: vite\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/iabirkhan/Nuxt-3-Minimal\r\n\r\n### Describe the bug\r\n\r\nwith default nuxt 3.3.3 setup or upgraded version shows type error in nuxt,config.ts. \r\n\r\n- *** This type error shows on minimal setup:\r\n\r\nArgument of type '{ app: { head: { charset: string; viewport: string; }; }; }' is not assignable to parameter of type 'NuxtConfig'.\r\n Object literal may only specify known properties, and 'app' does not exist in type 'NuxtConfig'.ts(2345)\r\n\r\n- *** Extending config also shows type error on plugins, css, build, vite\r\n\r\n```\r\nexport default defineNuxtConfig({\r\n// app, plugins, css, build, vite not working\r\n app: {\r\n head: {\r\n title: \"Nuxt 3 App\",\r\n charset: \"utf-8\",\r\n viewport: \"width=device-width, initial-scale=2\",\r\n },\r\n }, // if app config removed plugins dosen't work\r\n plugins: [], // shows error one after another\r\n css: [],\r\n build: {},\r\n vite: {},\r\n// modules, typescript working\r\n modules: [],\r\n typescript: {\r\n strict: true,\r\n },\r\n});\r\n```\r\n\r\nHopefully explained the problem clearly, please check. \r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[3232,3233,3234,3235],{"name":3171,"color":3172},{"name":3218,"color":3219},{"name":3157,"color":3158},{"name":3236,"color":3237},"needs reproduction","FBCA04",20040,"shows type error on nuxt.config.ts for app meta, plugins, css, build, vite","2023-12-05T07:21:45Z","https://github.com/nuxt/nuxt/issues/20040",0.6281664,{"description":3244,"labels":3245,"number":3250,"owner":3146,"repository":3146,"state":3208,"title":3251,"updated_at":3252,"url":3253,"score":3254},"### 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_",[3246,3247,3248,3249],{"name":3171,"color":3172},{"name":3218,"color":3219},{"name":3157,"color":3158},{"name":3236,"color":3237},21816,"Nuxt `3.6.1` introduces a regression on `AppConfig` types:","2023-09-13T13:03:57Z","https://github.com/nuxt/nuxt/issues/21816",0.6317938,{"labels":3256,"number":3262,"owner":3146,"repository":3146,"state":3208,"title":3263,"updated_at":3264,"url":3265,"score":3266},[3257,3258,3259],{"name":3171,"color":3172},{"name":3157,"color":3158},{"name":3260,"color":3261},"2.x","d4c5f9",7765,"Nuxt Build Error , when I use Typescript and ElementUI","2023-01-22T15:36:04Z","https://github.com/nuxt/nuxt/issues/7765",0.63706404,{"description":3268,"labels":3269,"number":3274,"owner":3146,"repository":3146,"state":3208,"title":3275,"updated_at":3276,"url":3277,"score":3278},"### Environment\n\n- Operating System: Linux\r\n- Node Version: v18.18.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.4.2\r\n- Builder: -\r\n- User Config: extends\r\n- Runtime Modules: -\r\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-bnn6ap?file=nuxt.config.ts\n\n### Describe the bug\n\nUpgrading to Nuxt 3.8 leads to a type issue for me: the `extends` key in `nuxt.config.ts` seems to not accept an array of strings anymore.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3270,3271,3272,3273],{"name":3171,"color":3172},{"name":3218,"color":3219},{"name":3174,"color":3175},{"name":3140,"color":3141},23791,"fix: type error on `extends` in v3.8","2023-10-20T15:23:37Z","https://github.com/nuxt/nuxt/issues/23791",0.6376275,["Reactive",3280],{},["Set"],["ShallowReactive",3283],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLfj3QWhQZ4lUOydvn6d0PU-kFNpa4oBHV5cEzks9J6M":-1},"/nuxt/ui/3579"]