\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```",[3165,3168],{"name":3166,"color":3167},"pending triage","E99695",{"name":3169,"color":3170},"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.6928664,{"description":3177,"labels":3178,"number":3181,"owner":3144,"repository":3145,"state":3182,"title":3183,"updated_at":3184,"url":3185,"score":3186},"### 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```",[3179,3180],{"name":3135,"color":3136},{"name":3138,"color":3139},4019,"closed","Type Issue with Select Component","2025-04-29T15:39:56Z","https://github.com/nuxt/ui/issues/4019",0.64755934,{"description":3188,"labels":3189,"number":3196,"owner":3144,"repository":3145,"state":3182,"title":3197,"updated_at":3198,"url":3199,"score":3200},"### 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",[3190,3191,3194],{"name":3135,"color":3136},{"name":3192,"color":3193},"closed-by-bot","ededed",{"name":3195,"color":3193},"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.6646371,{"description":3202,"labels":3203,"number":3209,"owner":3144,"repository":3144,"state":3182,"title":3210,"updated_at":3211,"url":3212,"score":3213},"### Environment\n\n```\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\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-mg1abp6d?file=app.vue\n\n### Describe the bug\n\nIn the Nuxt `v3.15` `compatibilityVersion: 4` doesn't change `data` type to `undefined` returned by `useFetch` as described in the [documentation](https://nuxt.com/docs/getting-started/upgrade#respect-defaults-when-clearing-data-in-useasyncdata-and-usefetch). It's `null`.\n\nIt works in `v3.14` as expected.\n\n```\n ERROR(vue-tsc) 'data.value' is possibly 'null'.\n FILE app.vue:10:12\n\n 8 | const dataValue = computed(() => {\n 9 | if (data.value !== undefined) {\n > 10 | return data.value.woof;\n | ^^^^^^^^^^\n 11 | }\n 12 | });\n 13 | \u003C/script>\n```",[3204,3207,3208],{"name":3205,"color":3206},"types","2875C3",{"name":3166,"color":3167},{"name":3169,"color":3170},30369,"`compatibilityVersion 4` doesn't change `useFetch` return data types","2024-12-27T21:33:08Z","https://github.com/nuxt/nuxt/issues/30369",0.668587,{"labels":3215,"number":3227,"owner":3144,"repository":3144,"state":3182,"title":3228,"updated_at":3229,"url":3230,"score":3231},[3216,3219,3220,3223,3224],{"name":3217,"color":3218},"good first issue","fbca04",{"name":3205,"color":3206},{"name":3221,"color":3222},"3.x","29bc7f",{"name":3135,"color":3136},{"name":3225,"color":3226},"🔨 p3-minor","FBCA04",14437,"Type wrong: `default` option of `useFetch` ","2023-03-11T22:36:12Z","https://github.com/nuxt/nuxt/issues/14437",0.66973126,{"description":3233,"labels":3234,"number":3244,"owner":3144,"repository":3144,"state":3182,"title":3245,"updated_at":3246,"url":3247,"score":3248},"### 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_",[3235,3236,3237,3240,3241],{"name":3205,"color":3206},{"name":3221,"color":3222},{"name":3238,"color":3239},"workaround available","11376d",{"name":3135,"color":3136},{"name":3242,"color":3243},"schema","1d76db",15750,"Invalid types for `ModuleOptions` in `NuxtModule`","2023-01-22T00:09:19Z","https://github.com/nuxt/nuxt/issues/15750",0.6744379,{"description":3250,"labels":3251,"number":3257,"owner":3144,"repository":3144,"state":3182,"title":3258,"updated_at":3259,"url":3260,"score":3261},"### Environment\n\n------------------------------\r\n- Operating System: Darwin\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.11.2\r\n- CLI Version: 3.11.1\r\n- Nitro Version: 2.9.6\r\n- Package Manager: yarn@1.22.21\r\n- Builder: -\r\n- User Config: ssr, app, nitro, runtimeConfig, devtools, css, modules, typescript, postcss, colorMode\r\n- Runtime Modules: nuxt-svgo@4.0.0, @vueuse/nuxt@10.7.2, @samk-dev/nuxt-vcalendar@1.0.2, dayjs-nuxt@2.1.9, @pinia/nuxt@0.5.1, @nuxt/image@1.3.0, @nuxtjs/device@3.1.1, @nuxtjs/color-mode@3.3.2, nuxt-swiper@1.2.2\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nTo reproduce you will need this configuration:\r\n{\r\n \"name\": \"nuxt-app\",\r\n \"private\": true,\r\n \"type\": \"module\",\r\n \"scripts\": {\r\n \"build\": \"nuxt build\",\r\n \"dev\": \"nuxt dev\",\r\n \"generate\": \"nuxt generate\",\r\n \"preview\": \"nuxt preview\",\r\n \"postinstall\": \"nuxt prepare\",\r\n \"lint\": \"eslint .\",\r\n \"lint:fix\": \"eslint . --fix\"\r\n },\r\n \"devDependencies\": {\r\n \"@nuxt/eslint-config\": \"^0.2.0\",\r\n \"@nuxtjs/color-mode\": \"^3.3.2\",\r\n \"@nuxtjs/device\": \"^3.1.1\",\r\n \"@samk-dev/nuxt-vcalendar\": \"^1.0.2\",\r\n \"@vueuse/core\": \"^10.7.2\",\r\n \"@vueuse/nuxt\": \"^10.7.2\",\r\n \"add\": \"^2.0.6\",\r\n \"autoprefixer\": \"^10.4.17\",\r\n \"dayjs-nuxt\": \"^2.1.9\",\r\n \"eslint\": \"^8.56.0\",\r\n \"nuxt\": \"^3.11.2\",\r\n \"nuxt-svgo\": \"^4.0.0\",\r\n \"postcss\": \"^8.4.33\",\r\n \"sass\": \"^1.70.0\",\r\n \"tailwindcss\": \"^3.4.1\",\r\n \"typescript\": \"^5.4.4\",\r\n \"vue\": \"^3.4.21\",\r\n \"vue-router\": \"^4.2.5\",\r\n \"vue-tsc\": \"^1.8.27\",\r\n \"yarn\": \"^1.22.21\"\r\n },\r\n \"dependencies\": {\r\n \"@nuxt/image\": \"^1.3.0\",\r\n \"@pinia/nuxt\": \"^0.5.1\",\r\n \"@types/crypto-js\": \"^4.2.2\",\r\n \"@types/memory-cache\": \"^0.2.5\",\r\n \"@vueuse/integrations\": \"^10.7.2\",\r\n \"animate.css\": \"^4.1.1\",\r\n \"crypto-js\": \"^4.2.0\",\r\n \"defu\": \"^6.1.4\",\r\n \"memory-cache\": \"^0.2.0\",\r\n \"nuxt-swiper\": \"^1.2.2\",\r\n \"pinia\": \"^2.1.7\",\r\n \"ufo\": \"^1.5.3\",\r\n \"universal-cookie\": \"^7.0.1\"\r\n }\r\n}\r\n\r\nI am using Webstorm\n\n### Describe the bug\n\nI have this code to make POST request to server:\r\nconst publications = await $fetch\u003CPublicationsResponse>('/v1/publication/search?limit=10&page=1', {\r\n method: 'POST',\r\n body: {\r\n \"categories\": [\r\n {\r\n \"id\": props.categoryId\r\n }\r\n ]\r\n }\r\n})\r\n\r\nI am getting this error:\r\n\r\n\r\nIts only disappears, when I am removing method: 'POST', but I need to make Post request.\r\nWhat can be wrong?\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3252,3253,3254,3256],{"name":3221,"color":3222},{"name":3166,"color":3167},{"name":3255,"color":3226},"needs reproduction",{"name":3192,"color":3193},26650,"Types issue in $fetch","2024-04-13T01:42:05Z","https://github.com/nuxt/nuxt/issues/26650",0.6868294,{"description":3263,"labels":3264,"number":3266,"owner":3144,"repository":3144,"state":3182,"title":3267,"updated_at":3268,"url":3269,"score":3270},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.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: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\n\n### Describe the bug\n\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\n\n### Additional context\n\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThe button itself still shows `0 selected`.\n\n### Logs\n\n_No response_",[3265],{"name":3166,"color":3167},28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.6892183,["Reactive",3272],{},["Set"],["ShallowReactive",3275],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f18-LNa_Tbr9S_2mS72tNlGKLz3LXBNc9yUZlTvJ-1zw":-1},"/nuxt/ui/1897"]