\n```\n\nWould it be relevant to add a global attribute to components like Button, Badge, etc., to force their appearance in dark (or light) mode, regardless of the global setting? This would ensure better visual consistency when these elements are placed on a colored background (e.g., `UPageCTA` with `solid` variant).\n\n### Additional context\n\n_No response_",[2902,2905,2908],{"name":2903,"color":2904},"enhancement","a2eeef",{"name":2906,"color":2907},"v3","49DCB8",{"name":2909,"color":2910},"triage","ffffff",3307,"nuxt","ui","open","Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.66225916,{"description":2920,"labels":2921,"number":2926,"owner":2912,"repository":2913,"state":2914,"title":2927,"updated_at":2928,"url":2929,"score":2930},"",[2922,2925],{"name":2923,"color":2924},"feature","A27AF6",{"name":2906,"color":2907},2322,"[MeterGroup] Implement component","2025-04-07T09:36:44Z","https://github.com/nuxt/ui/issues/2322",0.6735389,{"description":2932,"labels":2933,"number":2934,"owner":2912,"repository":2935,"state":2914,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Describe the feature\n\nI found, how to deploy nuxt 2 app into gcp app engine. But there is no doc about nuxt 3\n\n### Additional information\n\n- [ ] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [x] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [x] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[],1764,"nuxt.com","deploy nuxt 3 on gcp appengine","2025-01-22T09:58:41Z","https://github.com/nuxt/nuxt.com/issues/1764",0.6842618,{"description":2941,"labels":2942,"number":2948,"owner":2912,"repository":2913,"state":2914,"title":2949,"updated_at":2950,"url":2951,"score":2952},"### 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```",[2943,2946,2947],{"name":2944,"color":2945},"bug","d73a4a",{"name":2906,"color":2907},{"name":2909,"color":2910},3738,"Incorrect compound button variants types","2025-03-30T14:32:49Z","https://github.com/nuxt/ui/issues/3738",0.68740493,{"description":2954,"labels":2955,"number":2962,"owner":2912,"repository":2913,"state":2963,"title":2964,"updated_at":2965,"url":2966,"score":2967},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.16.1\n- CLI Version: 3.23.1\n- Nitro Version: 2.11.7\n- Package Manager: npm@10.9.2\n- Builder: -\n- User Config: modules, compatibilityDate, devtools, css, ui, devServer, future, telemetry, hooks, eslint\n- Runtime Modules: @nuxt/eslint@0.6.2, @nuxt/ui-pro@3.0.1, nuxt-jsonld@2.1.0, @pinia/nuxt@0.10.1\n- Build Modules: -\n\n\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nNuxt v3.16.1\nui-pro v3.0.1\n\n### Reproduction\n\nWhen I add the following to my nuxt.config.ts:\n\n```ts\n{\n ui: {\n colorMode: false\n }\n}\n```\n\n...then `npx nuxi typecheck` fails with 8 errors.\n\n```\n[...snip]\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n18 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\nnode_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10:24 - error TS2305: Module '\"#imports\"' has no exported member 'useColorMode'.\n\n10 import { useAppConfig, useColorMode } from '#imports'\n ~~~~~~~~~~~~\n\n\nFound 8 errors in 8 files.\n\nErrors Files\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/color-mode/ColorModeSwitch.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/content/ContentSearch.vue:89\n 1 node_modules/@nuxt/ui-pro/dist/runtime/components/DashboardSearch.vue:57\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeButton.vue:18\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSelect.vue:10\n 1 node_modules/@nuxt/ui-pro/dist/runtime/vue/components/ColorModeSwitch.vue:10\n\n ERROR Process exited with non-zero status (2)\n```\n\n### Description\n\nI think that there probably needs to be a stub export set up in all cases? Or these files should not be gathered by the typechecking script?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2956,2957,2958,2961],{"name":2944,"color":2945},{"name":2906,"color":2907},{"name":2959,"color":2960},"pro","5BD3CB",{"name":2909,"color":2910},3657,"closed","Setting ui.colorMode = false breaks nuxi typecheck","2025-03-27T20:54:57Z","https://github.com/nuxt/ui/issues/3657",0.6149411,{"description":2969,"labels":2970,"number":2973,"owner":2912,"repository":2913,"state":2963,"title":2974,"updated_at":2975,"url":2976,"score":2977},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.10.0\n- Nuxt Version: 3.15.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.15.1\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.9, @nuxt/eslint@0.7.4\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.0.0-alpha.10\n\n### Reproduction\n\nhttps://github.com/Cyanhall/nuxt-ui-v3-demo/tree/main/demo4\n\n### Description\n\nThe button styles in UModal body should not be affected by UButtonGroup. I'm not sure if this is a bug or a feature.\n\n\n```vue\n\u003Ctemplate>\n \u003CUButtonGroup>\n \u003CUModal\n :close=\"true\"\n v-model:open=\"open\"\n title=\"Test\"\n >\n \u003CUButton\n variant=\"outline\"\n color=\"neutral\"\n @click=\"open = true\"\n >\n Modal Button\n \u003C/UButton>\n \u003Ctemplate #body>\n Body\n \u003C/template>\n \u003Ctemplate #footer>\n \u003Cdiv class=\"flex justify-start w-full gap-4\">\n \u003CUButton\n variant=\"outline\"\n class=\"rounded\"\n label=\"Cancel\"\n @click=\"open = false\"\n />\n \u003CUButton\n variant=\"outline\"\n class=\"rounded\"\n label=\"Middle\"\n @click=\"open = false\"\n />\n \u003CUButton\n type=\"submit\"\n class=\"rounded\"\n label=\"Confirm\"\n color=\"primary\"\n @click=\"open = false\"\n />\n \u003C/div>\n \u003C/template>\n \u003C/UModal>\n \u003CUButton\n variant=\"outline\"\n color=\"neutral\"\n @click=\"\"\n >\n Other Button\n \u003C/UButton>\n \u003C/UButtonGroup>\n\u003C/template>\n```\n\n\u003Cimg width=\"362\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/da66f0d8-fc42-45a5-b1e1-d7214468b24a\" />\n\n\u003Cbr>\n\n\u003Cimg width=\"543\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/a50767ec-bea5-4c88-9b45-963f8e81e5df\" />\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2971,2972],{"name":2944,"color":2945},{"name":2906,"color":2907},2978,"The button styles in UModal body should not be affected by UButtonGroup.","2025-02-07T15:32:58Z","https://github.com/nuxt/ui/issues/2978",0.6269268,{"description":2979,"labels":2980,"number":2983,"owner":2912,"repository":2913,"state":2963,"title":2984,"updated_at":2985,"url":2986,"score":2987},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.0\n- Nuxt Version: 3.15.4\n- CLI Version: 3.21.1\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.2.2\n- Builder: -\n- User Config: compatibilityDate, devtools, runtimeConfig, nitro, routeRules, modules, supabase, site, feed, sitemap, robots, schemaOrg, image\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @nuxtjs/supabase@1.4.6, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0, @nuxthub/core@0.8.15, @nuxtjs/sitemap@7.2.4, nuxt-module-feed@1.1.4, @nuxtjs/robots@5.2.2, nuxt-schema-org@4.1.1, nuxt-link-checker@4.1.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.12\n\n### Reproduction\n\n```vue\n\u003CUModal\n :ui=\"{\n title: 'sr-only',\n description: 'sr-only',\n }\"\n :title=\"will not work\"\n :description=\"will not work\">\n \u003Ctemplate #content>\n \u003Cp>anything\u003C/p>\n \u003C/template>\n\u003C/UModal>\n```\n\n### Description\n\nNot having a title or description set for the modal will throw the following RekaUI error:\n```\nPostingCard.vue:76 Warning: `DialogContent` requires a `DialogTitle` for the component to be accessible for screen reader users.\n\nIf you want to hide the `DialogTitle`, you can wrap it with our VisuallyHidden component.\n\nWarning: Missing `Description` or `aria-describedby=\"undefined\"` for DialogContent.\n```\n\nThis is expected.\n\nThe problem is when you use the `content` slot of `UModal`, you can't set the title or description, either through props or by using the `title` or `description` slot.\n\nIt would be nice if setting the title and description slots/props while using the content still applies them but automatically applies `sr-only`.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2981,2982],{"name":2944,"color":2945},{"name":2906,"color":2907},3267,"Modal content slot causes accessibility issues","2025-02-21T10:49:04Z","https://github.com/nuxt/ui/issues/3267",0.6304309,{"description":2989,"labels":2990,"number":2995,"owner":2912,"repository":2913,"state":2963,"title":2996,"updated_at":2997,"url":2998,"score":2999},"### Description\n\nStyles with tailwindcss 4.0.13 seem to be broken after updating from NuxtUI pervious alpha.\n\n```\n\"dependencies\": {\n \"@iconify-json/ri\": \"1.2.5\",\n \"@nuxt/ui\": \"3.0.0\",\n \"@vueuse/core\": \"12.7.0\",\n \"@vueuse/nuxt\": \"12.7.0\",\n }\n```\nmain.css\n```\n@import 'tailwindcss' theme(static);\n@import '@nuxt/ui';\n```\nHas anyone else ran into this issue and if so how did you fix it?",[2991,2994],{"name":2992,"color":2993},"question","d876e3",{"name":2906,"color":2907},3525,"Styles issue have upgrade from 3.0.0-alpha.13 to 3.0.0","2025-03-12T23:28:54Z","https://github.com/nuxt/ui/issues/3525",0.65074605,{"description":3001,"labels":3002,"number":3005,"owner":2912,"repository":2913,"state":2963,"title":3006,"updated_at":3007,"url":3008,"score":3009},"### Description\n\nFor custom validation or for using the Form with Zod, etc. it would be great to have the common form field properties `touched` and `dirty` exposed.\n\n- `Touched` (opposite of `untouched`): A field is considered touched when a user has focused it OR changed it's value\n- `Dirty` (opposite of `pristine`): A field is considered dirty, if the value has changed (AND is different from its initial value). The second part is depending on the definition.\n\nYou can currently work around most of these by using a computed on the exposed `errors` ref and the state reactive, but for custom validation having these values natively exposed from the API would be very helpful.\n\n### Additional context\n\n_No response_",[3003,3004],{"name":2903,"color":2904},{"name":2906,"color":2907},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.6700389,{"description":3011,"labels":3012,"number":3015,"owner":2912,"repository":2913,"state":2963,"title":3016,"updated_at":3017,"url":3018,"score":3019},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v23.1.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: bun@1.1.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.8\n\n### Reproduction\n\nhttps://github.com/brycesteve/nuxtUi500Repro\n\n### Description\n\nWhen using Nuxt UI from a layer, wrapping in `UApp` causes the following error:\n\n```\n500\nnull is not an object (evaluating 'currentRenderingInstance.ce')\n\nat renderComponentRoot (./node_modules/@vue/runtime-core/dist/runtime-core.cjs.js:3708:44)\nat renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:465:65)\nat renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:417:36)\nat ssrRenderComponent (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:57:32)\nat _sfc_ssrRender (:52:49)\nat renderComponentSubTree (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:460:20)\nat renderComponentVNode (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:417:36)\nat ssrRenderComponent (./node_modules/@vue/server-renderer/dist/server-renderer.cjs.js:57:32)\nat _sfc_ssrRender (:46:49)\n```\n\nRemoving `UApp` stops the error from happening. `UApp` also works correctly when not in a layer.\n\nIn the reproduction, Nuxt UI is added to the layer in `~/layers/ui`.\n\nRunning `bun --bun run dev` in the project root causes the error. Switching to `~/layers/ui` and running `bun --bun run dev` doesn't have the same error (`App.vue` in `~/layers/ui/.playground` is the same as the root `App.vue`). So, the issue is something to do with Nuxt UI being extended from a layer. The other components I've tried seem to work ok.\n\nI have read in a few places that this might be something to do with multiple Vue instances being created. But if it is, I can't seem to find a config that allows it to work.\n\nShould Nuxt UI work from a layer, or is it not compatible this way? If it should, is there something I'm doing wrong, or does anyone have a fix to make this work?\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3013,3014],{"name":2944,"color":2945},{"name":2906,"color":2907},2622,"Nuxt UI in layer causes 500 error when wrapping in UApp","2024-12-05T13:48:51Z","https://github.com/nuxt/ui/issues/2622",0.6704001,["Reactive",3021],{},["Set"],["ShallowReactive",3024],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmikeusbp_ydVNzU1xmklyd9WBBXVNbOM4kZ37W-HQg4":-1},"/nuxt/ui/3357"]