\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```",[3113,3114,3115],{"name":3083,"color":3084},{"name":3086,"color":3087},{"name":3089,"color":3090},4530,"[UInputTags, UInputMenu] Theming behaviour issues","2025-07-15T17:50:02Z","https://github.com/nuxt/ui/issues/4530",0.6877973,{"description":3122,"labels":3123,"number":3127,"owner":3092,"repository":3092,"state":3094,"title":3128,"updated_at":3129,"url":3130,"score":3131},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.11.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: pnpm@9.1.4\r\n- Builder: -\r\n- User Config: modules, experimental, ssr, css, colorMode, nitro, app, pwa, devtools, eslintConfig, i18n, vite, runtimeConfig\r\n- Runtime Modules: @vueuse/nuxt@10.10.0, @unocss/nuxt@0.58.9, @pinia/nuxt@0.5.1, @pinia-plugin-persistedstate/nuxt@1.2.0, @nuxtjs/color-mode@3.4.1, @vite-pwa/nuxt@0.4.0, @bg-dev/nuxt-naiveui@1.10.1, @nuxtjs/i18n@8.3.1, unplugin-icons/nuxt, nuxt-module-eslint-config@0.1.1\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nNuxt Config:\r\n```ts\r\nexport default defineNuxtConfig({\r\n // ...\r\n runtimeConfig: {\r\n public: {\r\n test: 'prerendered \"test value\" (default)',\r\n onlyRuntime: 'prerendered \"only runtime value\" (default)'\r\n },\r\n },\r\n nitro: {\r\n esbuild: {\r\n options: {\r\n target: 'esnext',\r\n },\r\n },\r\n prerender: {\r\n crawlLinks: false,\r\n routes: ['/'],\r\n },\r\n },\r\n // ...\r\n})\r\n```\r\n\r\n`pages/index.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>This Page is prerendered\u003C/h1>\r\n {{config.public.test}} \u003Cbr>\r\n \u003CNuxtLink to=\"/test\">SSR page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst config = useRuntimeConfig()\r\n\u003C/script>\r\n```\r\n\r\n`pages/test.vue`\r\n\r\n```vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ch1>This Page is not prerendered\u003C/h1>\r\n {{config.public.test}}\u003Cbr>\r\n {{config.public.onlyRuntime}}\u003Cbr>\r\n \u003CNuxtLink to=\"/\">prerendered Page\u003C/NuxtLink>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst config = useRuntimeConfig()\r\n\u003C/script>\r\n```\r\n\r\nenv for `node .output/server/index.mjs`\r\n\r\n```yaml\r\n environment:\r\n - NUXT_PUBLIC_TEST=runtime \"test value\"\r\n - NUXT_PUBLIC_ONLY_RUNTIME=runtime \"only runtime value\"\r\n```\r\n\r\nlink to deployed version: https://app.runtime-config-example.v2.singular-it-test.de/\n\n### Describe the bug\n\nSteps:\r\n1. open https://app.runtime-config-example.v2.singular-it-test.de/\r\n2. see varaibles\r\n3. navigate to SSR page\r\n4. variables are still from builttime\r\n5. refresh page\r\n6. variables are now from runtime\r\n7. navigate back to prerendered\r\n8. variables are still runtime\n\n### Additional context\n\ni think it will be intended that way, but i find the behavior of the runtimeConfig sometimes a bit inconsistent, especially if you prerender parts of the app and others not. (and thus also with regard to the caching of pwa). Depending on the entry point in the app (i.e. whether generated or dynamic), this can lead to different configs, which then persist between the dynamic and static pages. \r\n\r\ni don't expect prerendered parts of the app to pick up the runtime config, but i would assume that when i switch from a static to a non-static page, the runtime variables also play a role. Otherwise, as soon as prerender is active, everything should be set at build time (so that there can no longer be a runtime config) and everything is/needs to be set in the build step to avoid differences depending on the entry point.\r\n\r\nI know that it is not necessarily common to have a different config for generation than for runtime, but especially in my case it is not necessary to set all variables in the build (prerender). and generally the runtime config is also there to set the variables when running the app.\n\n### Logs\n\n_No response_",[3124],{"name":3125,"color":3126},"pending triage","E99695",28847,"strange runtimeConfig behaviour when prerendering parts of the app","2024-09-06T11:27:57Z","https://github.com/nuxt/nuxt/issues/28847",0.6885559,{"description":3133,"labels":3134,"number":3137,"owner":3092,"repository":3093,"state":3094,"title":3138,"updated_at":3139,"url":3140,"score":3141},"### Environment\n\n- Operating System: `Windows_NT`\n- Node Version: `v24.6.0`\n- Nuxt Version: `3.16.2`\n- CLI Version: `3.26.4`\n- Nitro Version: `2.12.4`\n- Package Manager: `npm@11.5.1`\n- Builder: `-`\n- User Config: `modules`, `devtools`, `app`, `css`, `colorMode`, `ui`, `runtimeConfig`, `alias`, `routeRules`, `sourcemap`, `devServer`, `future`, `compatibilityDate`, `nitro`, `eslint`, `fileStorage`, `fonts`, `googleTranslate`, `gtag`, `i18n`, `icon`, `image`, `security`, `stripe`, `svgo`, `tiptap`\n- Runtime Modules: `nuxt-auth-utils@0.5.17`, `@pinia/nuxt@0.10.1`, `nuxt-svgo@4.0.16`, `@nuxtjs/i18n@9.3.4`, `nuxt-authorization@0.3.4`, `nuxt-file-storage@0.3.0`, `@nuxt/fonts@0.11.0`, `@nuxt/image@1.10.0`, `@nuxt/ui@3.3.0`, `@nuxt/content@3.4.0`, `nuxt-security@2.2.0`, `nuxt-tiptap-editor@2.1.4`, `nuxt-google-translate@1.3.3`, `@unlok-co/nuxt-stripe@5.0.0`, `@nuxt/eslint@1.3.1`, `nuxt-gtag@3.0.3`\n- Build Modules: `-`\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Package\n\nv3.x\n\n### Version\n\n3.16.2\n\n### Reproduction\n\n-\n\n### Description\n\nIf you run nuxt dev you will see in console the message \"nuxt 4 coimpatibility mode enabled\" , in browser you will see the nuxt 4 logo instead of nuxt 3 and it will crash with\n\n500\n[GET] \"http://127.0.0.1:443/__nuxt_vite_node__/manifest\": fetch failed\n\nprobably some dependency related with vite and nuxt has been updated\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3135,3136],{"name":3083,"color":3084},{"name":3089,"color":3090},4844,"from 3.3.0 version 4 of nuxt is \"forced\"","2025-08-29T10:54:57Z","https://github.com/nuxt/ui/issues/4844",0.6908277,{"description":3143,"labels":3144,"number":3149,"owner":3092,"repository":3092,"state":3150,"title":3151,"updated_at":3152,"url":3153,"score":3154},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v16.15.1`\r\n- Nuxt Version: `3.0.0-rc.9`\r\n- Nitro Version: `0.5.1`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `ssr`, `target`, `css`, `modules`, `runtimeConfig`, `sanity`, `meta`, `sitemap`\r\n- Runtime Modules: `@nuxtjs/tailwindcss@5.3.3`, `@nuxtjs/google-gtag@1.0.4`, `@funken-studio/sitemap-nuxt-3@3.2.0`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://alicia-chamaille-portfolio.pages.dev/\n\n### Describe the bug\n\nI have added meta tags to the nuxt.config.ts.\r\n\r\nThese data can be see when viewing the head from the elements, but when trying to validate they are working, I get errors say no description etc.\r\nThese are the sites I'm trying to test on\r\nhttps://cards-dev.twitter.com/validator\r\nhttps://rushax.com/tools/meta-description-checker/\r\nhttps://totheweb.com/learning_center/tool-test-google-title-meta-description-lengths/\r\nhttps://www.heymeta.com/url/www.thaliarabie.com/\r\n\r\n\u003Cimg width=\"1114\" alt=\"Screenshot 2022-10-20 at 16 17 15\" src=\"https://user-images.githubusercontent.com/27204436/197059946-eeb6cb33-7acd-4bb0-b413-83595ac50736.png\">\r\n\r\nNo one of them work, any help would be greatly appreciated.\r\n\r\nI've done the exact same approach on nuxt v2 and it works\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3145,3148],{"name":3146,"color":3147},"3.x","29bc7f",{"name":3125,"color":3126},15216,"closed","Meta tags show in browser but don't work","2023-09-07T22:03:56Z","https://github.com/nuxt/nuxt/issues/15216",0.6738846,{"description":3156,"labels":3157,"number":3160,"owner":3092,"repository":3092,"state":3150,"title":3161,"updated_at":3162,"url":3163,"score":3164},"### Environment\n\n------------------------------\r\n- Operating System: `Linux`\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: `pnpm@7.18.2`\r\n- Builder: `vite`\r\n- User Config: `srcDir`, `imports`, `modules`, `css`, `build`, `pinceau`, `i18n`, `typescript`, `colorMode`, `ignore`, `vite`, `tailwindcss`, `plausible`\r\n- Runtime Modules: `@pinia/nuxt@0.4.6`, `@vueuse/nuxt@9.7.0`, `@nuxtjs/tailwindcss@6.1.3`, `@pinia/nuxt@0.4.6`, `@nuxtjs/i18n@8.0.0-beta.7`, `@nuxtjs/color-mode@3.2.0`, `@huntersofbook/plausible-nuxt@0.5.2`, `@nuxtjs/partytown@1.3.0`, `nuxt-icon@0.1.8`, `pinceau/nuxt`, `@nuxtjs/fontaine@0.2.3`, `nuxt-headlessui@1.0.4`\r\n- Build Modules: `-`\r\n------------------------------\n\n### Reproduction\n\nhttps://github.com/productdevbook/oku-nuxt3-template/tree/bug-nuxt-config\r\n\r\nbrach: bug-nuxt-config\n\n### Describe the bug\n\n\r\nhttps://user-images.githubusercontent.com/38668796/208305787-be4c7c65-820b-4eb5-baaf-9d6295232c31.mp4\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3158,3159],{"name":3146,"color":3147},{"name":3125,"color":3126},15671,"nuxt config TS errors","2023-01-19T18:29:58Z","https://github.com/nuxt/nuxt/issues/15671",0.68141925,{"labels":3166,"number":3169,"owner":3092,"repository":3092,"state":3150,"title":3170,"updated_at":3171,"url":3172,"score":3173},[3167,3168],{"name":3146,"color":3147},{"name":3125,"color":3126},13540,"Problem with @intlify/nuxt3 in most latest Nuxt Version","2023-04-20T12:42:17Z","https://github.com/nuxt/nuxt/issues/13540",0.6860079,{"labels":3175,"number":3181,"owner":3092,"repository":3092,"state":3150,"title":3182,"updated_at":3183,"url":3184,"score":3185},[3176,3177,3178],{"name":3146,"color":3147},{"name":3125,"color":3126},{"name":3179,"color":3180},"needs reproduction","FBCA04",23460,"TS Typing issue.","2023-10-20T22:22:28Z","https://github.com/nuxt/nuxt/issues/23460",0.6901038,{"labels":3187,"number":3195,"owner":3092,"repository":3092,"state":3150,"title":3196,"updated_at":3197,"url":3198,"score":3199},[3188,3189,3192],{"name":3146,"color":3147},{"name":3190,"color":3191},"upstream","E8A36D",{"name":3193,"color":3194},"upstream-bug","B60205",13516,"meta script tags in nuxt.config.ts escape or htmlencode `&`","2023-01-19T16:58:45Z","https://github.com/nuxt/nuxt/issues/13516",0.6903229,["Reactive",3201],{},["Set"],["ShallowReactive",3204],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fE37pvTD61vpOajcVdDExB9MOYZ9apsCZKQymaU-BxiE":-1},"/nuxt/ui/4889"]