\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```",[3039,3042],{"name":3040,"color":3041},"pending triage","E99695",{"name":3043,"color":3044},"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.6546905,{"description":3051,"labels":3052,"number":3054,"owner":3029,"repository":3029,"state":3031,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### Environment\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.0\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: npm@10.8.2\n- Builder: -\n- User Config: compatibilityDate\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-r78zhzgw?file=app.vue\n`npm run generate && npm run preview`\n\n### Describe the bug\n\nWhen using CSS `v-bind()` for part of CSS properties that can have multiple values like `border`, they disappear only in production builds. This is specific to Nuxt and did not occur with Vue alone. ( https://stackblitz.com/edit/vitejs-vite-h7sncoub?file=src%2FApp.vue and `npm run build && npm run preview` )\n\nAs a workaround, I was able to avoid this issue by using `v-bind()` with individual properties like `border-width`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3053],{"name":3040,"color":3041},31779,"Sometimes CSS `v-bind()` disappears only in production build.","2025-04-12T12:48:15Z","https://github.com/nuxt/nuxt/issues/31779",0.6715264,{"description":3060,"labels":3061,"number":3065,"owner":3029,"repository":3030,"state":3031,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### 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```",[3062,3063,3064],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4182,"Custom type with InputMenu","2025-05-19T12:22:28Z","https://github.com/nuxt/ui/issues/4182",0.6804375,{"description":3071,"labels":3072,"number":3076,"owner":3029,"repository":3030,"state":3031,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.15.0\n- Nuxt Version: 3.17.7\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: pnpm@10.10.0\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, fonts, icon, components, css, ui\n- Runtime Modules: @nuxt/fonts@0.11.4, @nuxt/eslint@1.5.2, @nuxt/icon@1.15.0, @nuxt/image@1.10.0, @nuxt/ui@3.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.2.0\n\n### Reproduction\n\nTheming with either of this method such as:\n\n### Theming in `app.config.ts`\nSame issue for both UInputTags and UInputMenu (multiple)\n```typescript\ninputTags: {\n ...\n compoundVariants: [\n {\n variant: 'outline',\n class : {\n root: 'root-test',\n base: 'base-test',\n },\n },\n ],\n},\ninputMenu: {\n ...\n compoundVariants: [\n // Works properly\n {\n variant: 'outline',\n class : {\n root: 'root-test',\n base: 'base-test',\n },\n },\n // Wrong behaviour\n {\n variant: 'outline',\n multiple: true,\n class : {\n root: 'root-test',\n base: 'base-test',\n },\n },\n ],\n},\n\n```\n### Theming directly using `ui`\n```tsx\n\u003CUInputTags\n ...\n :ui=\"{\n root: 'root-test',\n base: 'base-test',\n }\"\n/>\n```\n\n### Will results something like this\n```html\n\u003Cdiv class=\"... root-test base-test\">\n ...\n \u003Cinput class=\"...\" />\n\u003C/div>\n```\n\n### Description\n\nWhen applying themes in `app.config.ts`, both **UInputTags** and **UInputMenu (multiple)** share the same weird behaviour compared with other components, where the class applied to `base` part of the component are applied to `root` part of the component.\n\n### Expected Behaviour\nThe applied class on `base` should be applied to the `\u003Cinput />`, not the `root` part of the component which is the outer `\u003Cdiv />` just like other input components such as **UInput**, **UInputNumber**, or **UTextarea**.\n\nCorrect me if I'm wrong if this are intended, thank you!\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3073,3074,3075],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4530,"[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.6877758,{"description":3082,"labels":3083,"number":3088,"owner":3029,"repository":3029,"state":3089,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Environment\n\n------------------------------ From the stackblitz repo\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.10`\r\n- Nitro Version: `0.5.3`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\r\n------------------------------On my local laptop\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.16.0`\r\n- Nuxt Version: `3.0.0-rc.10`\r\n- Nitro Version: `0.5.3`\r\n- Package Manager: `npm@8.11.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-2svdvu?file=app.vue\n\n### Describe the bug\n\nStyles from default layout gets ignored in app.vue. Only way the styles show up is by adding NuxtWelcome to app.vue. \r\n\r\nOnce the app is up and running in the repo, in app.vue, uncomment NuxtWelcome and you can see the styles restored. \r\n\r\nPlease advise if I'm missing any nuxt rules/conventions w.r.t layouts. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3084,3087],{"name":3085,"color":3086},"3.x","29bc7f",{"name":3040,"color":3041},14910,"closed","Default layout styles are getting ignored in app.vue","2023-01-19T17:42:24Z","https://github.com/nuxt/nuxt/issues/14910",0.64456487,{"description":3095,"labels":3096,"number":3102,"owner":3029,"repository":3029,"state":3089,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\r\n- Node Version: `v16.14.2`\r\n- Nuxt Version: `3.0.0-rc.9`\r\n- Nitro Version: `0.5.1`\r\n- Package Manager: `npm@7.17.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-starter-ytp3rx?file=app.vue\n\n### Describe the bug\n\nWhen you create a minimal application without a `nuxt.config.ts` (so just `app.vue` for example), the \"default `app.vue`\" will be shown forever.\r\n\r\nThis can only be resolved by adding back a `nuxt.config.ts` (or js)\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3097,3098,3099],{"name":3085,"color":3086},{"name":3020,"color":3021},{"name":3100,"color":3101},"❗ p4-important","D93F0B",14848,"Welcome component will stay when no `nuxt.config.ts` exists","2023-01-19T17:41:13Z","https://github.com/nuxt/nuxt/issues/14848",0.6526857,{"description":3108,"labels":3109,"number":3115,"owner":3029,"repository":3029,"state":3089,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v18.8.0`\r\n- Nuxt Version: `3.1.1`\r\n- Nitro Version: `2.1.0`\r\n- Package Manager: `npm@8.18.0`\r\n- Builder: `vite`\r\n- User Config: `-`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\n*\r\n\r\n### Describe the bug\r\n\r\nAfter updating from 3.0.0 to 3.1.1\r\nI'm getting errors from vue-tsc like Property 'x' does not exist on type 'AppConfig' \r\n\r\nI was trying to declare interface AppConfigInput in index.d.ts like here\r\nhttps://nuxt.com/docs/guide/directory-structure/app-config#manually-typing-app-config\r\nI also added to nuxt.config.ts\r\nexperimental: { configSchema: true, },\r\n\r\ninsideapp.config.ts I have an empty object.\r\nexport default defineAppConfig({})\r\nI'm setting appConfig dynamically based on process.env (in nuxt.config.ts), ofc it has valid types there\r\nBut it should be merged anyway.\r\n\r\n### Additional context\r\n\r\nhttps://github.com/nuxt/nuxt/pull/18410\r\n\r\n### Logs\r\n\r\n_No response_",[3110,3111,3112],{"name":3085,"color":3086},{"name":3040,"color":3041},{"name":3113,"color":3114},"needs reproduction","FBCA04",18555,"3.1.1 - Typing AppConfig stopped work after upgrade","2023-03-20T15:38:42Z","https://github.com/nuxt/nuxt/issues/18555",0.6639452,{"description":3121,"labels":3122,"number":3126,"owner":3029,"repository":3029,"state":3089,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### Environment\n\n(Stackblitz Sandbox)\n\nWorking directory: /home/projects/llqiwvwkzb.github\nNuxt project info:\n------------------------------\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: compatibilityDate, devtools\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-appconfig-update?file=app.config.ts\n\n### Describe the bug\n\nWhen removing unused entries in appConfig, Nuxt only updates existing entries and ignores the entries to be deleted.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3123,3124],{"name":3020,"color":3021},{"name":3125,"color":3114},"🔨 p3-minor",30916,"appConfig doesn't remove unused entries","2025-02-10T17:10:12Z","https://github.com/nuxt/nuxt/issues/30916",0.6664072,{"description":3132,"labels":3133,"number":3136,"owner":3029,"repository":3029,"state":3089,"title":3137,"updated_at":3138,"url":3139,"score":3140},"### Environment\r\n\r\n```\r\nNuxt project info: \r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v18.18.0\r\n- Nuxt Version: 3.9.3\r\n- CLI Version: 3.10.0\r\n- Nitro Version: 2.8.1\r\n- Package Manager: npm@10.2.3\r\n- Builder: -\r\n- User Config: css, devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\r\n```\r\n\r\n### Reproduction\r\n\r\n[Nuxt 3 repo](https://stackblitz.com/edit/github-qbfhyv) vs [Nuxt 2 repo](https://stackblitz.com/edit/github-4yydwm)\r\n\r\nBoth projects implement an identical structure (layout with header and index page)\r\n\r\nIn each of the reproductions, run the necessary commands to run the project in production mode\r\n- nuxt 3 - `npm run build && npm run preview`\r\n- nuxt 2 - `npm run build && npm run start`\r\n\r\nInspect the HTML code returned by accessing the index page. Notice the `\u003Cstyle>` tag in the `\u003Chead>`\r\n\r\n### Describe the bug\r\n\r\nThe way Nuxt 3 builds and extracts the CSS from the app is inconsistent with Nuxt 2. This can cause complications when migrating an existing Nuxt 2 app.\r\n\r\nIn Nuxt 3, the global styles specified from the nuxt config are injected at the end of the style tag. With Nuxt 2, these were injected at the beginning.\r\n\r\nIn both reproduction repositories, the `@/assets/styles/global.css` file is provided globally. If you inspect the result of the HTML pages (build for production), the contents of that CSS file are placed differently.\r\n\r\n**Follow-up observation** - this might be unrelated, but you will also notice that in the case of Nuxt 3, it is including the styles for both `components/dynamic/One.vue` and `components/dynamic/Two.vue` even though only at render time only `\u003Cdynamic-one />` is rendered. Nuxt 2 correctly only includes the styles from `One.vue`.\r\n\r\nIf unrelated (and is considered to be an issue) i am happy to open a separate report.\r\n\r\n### Additional context\r\n\r\nWe are in the process of migrating our Nuxt 2 app to Nuxt 3 and are running into multiple complications - this is one of them.\r\n\r\nIn the case of developing an app from scratch this would not be an issue because it would inform the development style.\r\n\r\nHowever, in our case some of the global styles get overridden by rules at the component level. The new order in Nuxt 3 causes this to break.\r\n\r\n### Logs\r\n\r\n_No response_",[3134,3135],{"name":3085,"color":3086},{"name":3040,"color":3041},25393,"Discrepancies in production build styles order (compared to nuxt 2)","2024-01-26T20:16:35Z","https://github.com/nuxt/nuxt/issues/25393",0.6762877,["Reactive",3142],{},["Set"],["ShallowReactive",3145],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$feHbkrA48Jx5bG0oZ-ls6drWlSvVd6nzLKG1A0r4VMbQ":-1},"/nuxt/ui/4461"]