\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_",[3030,3033,3036],{"name":3031,"color":3032},"enhancement","a2eeef",{"name":3034,"color":3035},"v3","49DCB8",{"name":3037,"color":3038},"triage","ffffff",3307,"ui","Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.693433,{"description":3046,"labels":3047,"number":3051,"owner":3020,"repository":3040,"state":3022,"title":3052,"updated_at":3053,"url":3054,"score":3055},"### Description\n\nAdd a color prop similar to the one used in NavigationMenu, to allow changing the color of the active item\n\n### Additional context\n\n_No response_",[3048,3049,3050],{"name":3031,"color":3032},{"name":3034,"color":3035},{"name":3037,"color":3038},3052,"Add a color prop to UBreadcrumb","2025-02-23T19:20:02Z","https://github.com/nuxt/ui/issues/3052",0.69388723,{"labels":3057,"number":3067,"owner":3020,"repository":3020,"state":3068,"title":3069,"updated_at":3070,"url":3071,"score":3072},[3058,3061,3064],{"name":3059,"color":3060},"3.x","29bc7f",{"name":3062,"color":3063},"bug","d73a4a",{"name":3065,"color":3066},"upstream","E8A36D",12182,"closed","ReferenceError: window is not defined","2023-01-19T15:59:20Z","https://github.com/nuxt/nuxt/issues/12182",0.6644861,{"labels":3074,"number":3079,"owner":3020,"repository":3020,"state":3068,"title":3080,"updated_at":3081,"url":3082,"score":3083},[3075,3076],{"name":3059,"color":3060},{"name":3077,"color":3078},"pending triage","E99695",14489,"VueUse `useMounted` results in \"onMounted is called when there is no active component instance\" during SSR in production mode","2023-08-30T19:48:13Z","https://github.com/nuxt/nuxt/issues/14489",0.6678856,{"description":3085,"labels":3086,"number":3091,"owner":3020,"repository":3040,"state":3068,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Description\n\ni noticed that NUXT UI / NUXT UI PRO were refactored to use tailwind's new version 3 stuff + radix...\n\ni just went to the tailwind docs today and it looks like they just skipped right past their new version 3 and went to version 4...\n\nany ideas how this effects NUXT UI/PRO? \n\nMy undersanding is that version 3->4 means it was a semver breaking change?",[3087,3090],{"name":3088,"color":3089},"question","d876e3",{"name":3034,"color":3035},3167,"tailwind version 4..?","2025-01-24T10:17:32Z","https://github.com/nuxt/ui/issues/3167",0.6701042,{"description":3097,"labels":3098,"number":3101,"owner":3020,"repository":3040,"state":3068,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Environment\n\n- Operating System: Linux\n- Node Version: v22.4.0\n- Nuxt Version: 3.14.159\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.13.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.8\n- Build Modules: -\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\n-\n\n### Description\n\nDefault classes of container in [docs](https://ui3.nuxt.dev/components/container#theme) is:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\n**But no one of classes except `mx-auto` is not was created.**\nI change `--ui-container` variable like in [docs](https://ui3.nuxt.dev/getting-started/theme#container):\n```css\n/** app.css */\n\n@import 'tailwindcss';\n@import '@nuxt/ui';\n\n@theme {\n --container-xl: 1280px;\n}\n\n:root {\n --ui-container: var(--container-xl);\n}\n```\nAs result, container classes is `max-w-7xl mx-auto px-4 sm:px-6 lg:px-8` and still not was created, except `mx-auto`.\n\nBut if i create `app.config.ts`:\n```ts\nexport default defineAppConfig({\n ui: {\n container: {\n base: 'max-w-[var(--ui-container)] mx-auto px-4 sm:px-6 lg:px-8'\n }\n }\n})\n```\nAll is ok, width and other classes are created and applying.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3099,3100],{"name":3062,"color":3063},{"name":3034,"color":3035},2655,"Classes of container component are not working properly","2024-11-16T13:13:33Z","https://github.com/nuxt/ui/issues/2655",0.67085546,{"description":3107,"labels":3108,"number":3109,"owner":3020,"repository":3110,"state":3068,"title":3111,"updated_at":3112,"url":3113,"score":3114},"After using `pnpm update` to upgrade vue to 3.4.3, the console throws a lot of `Hydration mismatch`. If I am using vue 3.3.13, no `Hydration mismatch` warnings will be thrown.\r\n\r\n\u003Cimg width=\"1402\" alt=\"SCR-20240103-qagg\" src=\"https://github.com/nuxt/nuxt.com/assets/133459587/188ac1c4-e19a-4570-a5d0-4863c92a7bda\">\r\n",[],1467,"nuxt.com","About vue@3.4.3 causing hydration mismatch","2024-05-03T00:34:36Z","https://github.com/nuxt/nuxt.com/issues/1467",0.6723869,{"description":3116,"labels":3117,"number":3119,"owner":3020,"repository":3040,"state":3068,"title":3120,"updated_at":3121,"url":3122,"score":3123},"### Environment\n\n- Node version: 22.9.0 (Docker image 22.9.0-alpine)\n- Nuxt version: 3.14.1592\n- Package manager: pnpm@9.14.2\n- nuxt/ui module version: 2.19.2\n- package.json\n ```\n {\n \"name\": \"nuxt-app\",\n \"private\": true,\n \"type\": \"module\",\n \"scripts\": {\n \"build\": \"nuxt build\",\n \"dev\": \"nuxt dev\",\n \"generate\": \"nuxt generate\",\n \"preview\": \"nuxt preview\",\n \"postinstall\": \"nuxt prepare\"\n },\n \"dependencies\": {\n \"@nuxt/ui\": \"^2.19.2\",\n \"nuxt\": \"^3.14.1592\",\n \"vue\": \"latest\",\n \"vue-router\": \"latest\"\n },\n \"packageManager\": \"pnpm@9.14.2+sha512.6e2baf77d06b9362294152c851c4f278ede37ab1eba3a55fda317a4a17b209f4dbb973fb250a77abc463a341fcb1f17f17cfa24091c4eb319cda0d9b84278387\"\n }\n ```\n- Dockerfile\n ```\n ARG NODE_DOCKER_IMAGE=22.9.0-alpine\n FROM node:$NODE_DOCKER_IMAGE AS base\n \n ARG PORT=3000\n \n ENV NODE_ENV=production\n \n WORKDIR /app\n # Build\n FROM base AS builder\n \n RUN npm install -g pnpm\n \n COPY --link package.json .\n COPY --link pnpm-lock.yaml .\n \n RUN pnpm install --production=true\n \n COPY --link . .\n \n RUN pnpm build\n \n # Run\n FROM base\n \n ENV PORT=$PORT\n \n COPY --from=builder /app/.output /app/.output\n \n COPY --from=builder /app/docker-entrypoint.sh /usr/local/bin/docker-entrypoint\n \n RUN chmod +x /usr/local/bin/docker-entrypoint\n \n ENTRYPOINT [\"docker-entrypoint\"]\n ```\n\n\n### Version\n\nv2.19.2\n\n### Reproduction\n\n1. Create the \"frontend\" Nuxt app `pnpx nuxi@latest init frontend`\n2. `cd frontend`\n3. Add the \"nux/ui\" module `pnpx nuxi@latest module add ui`\n4. Put the Dockerfile described inside the frontend folder\n5. `docker build .`\n\n### Description\n\nThe build fails:\n```\n=> ERROR [builder 6/6] RUN pnpm build 3.4s\n------ \n > [builder 6/6] RUN pnpm build: \n0.512 \n0.512 > nuxt-app@ build /app \n0.512 > nuxt build \n0.512 \n0.658 Nuxt 3.14.1592\n1.374 [nuxt:tailwindcss] ℹ Using default Tailwind CSS file\n1.589 ℹ Nuxt Icon server bundle mode is set to local\n3.009 ℹ Building client...\n3.018 ℹ vite v5.4.11 building for production...\n3.040 ℹ transforming...\n3.350 ℹ ✓ 57 modules transformed.\n3.351 \n3.351 ERROR x Build failed in 331ms\n3.351 \n3.351 \n3.351 ERROR Nuxt Build Error: [vite:css] [postcss] Cannot find module 'tailwindcss/lib/lib/defaultExtractor.js'\n3.351 Require stack:\n3.351 - /app/.nuxt/nuxtui-tailwind.config.cjs\n3.351 file: /app/node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/tailwind.css:undefined:NaN\n3.351 \n3.351 Require stack:\n3.351 - .nuxt/nuxtui-tailwind.config.cjs\n3.351 file: node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/tailwind.css:undefined:NaN\n3.351 at Module._resolveFilename (node:internal/modules/cjs/loader:1248:15)\n3.351 at Function.resolve (node:internal/modules/helpers:145:19)\n3.351 at _resolve (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:241814)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:244531)\n3.351 at .nuxt/nuxtui-tailwind.config.cjs:2:60\n3.351 at evalModule (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)\n3.351 at .nuxt/tailwind.config.cjs:7:1\n3.351 at evalModule (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:247313)\n3.351 at jiti (node_modules/.pnpm/jiti@1.21.6/node_modules/jiti/dist/jiti.js:1:245241)\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/load-config.js:56:30\n3.351 at loadConfig (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/load-config.js:58:6)\n3.351 at getTailwindConfig (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:71:116)\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/lib/setupTrackingContext.js:100:92\n3.351 at node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/processTailwindFeatures.js:46:11\n3.351 at plugins (node_modules/.pnpm/tailwindcss@3.4.15/node_modules/tailwindcss/lib/plugin.js:38:69)\n3.351 at LazyResult.runOnRoot (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:329:16)\n3.351 at LazyResult.runAsync (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:258:26)\n3.351 at LazyResult.async (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:160:30)\n3.351 at LazyResult.then (node_modules/.pnpm/postcss@8.4.49/node_modules/postcss/lib/lazy-result.js:404:17)\n3.351 \n3.370 ELIFECYCLE Command failed with exit code 1.\n```\n\n### Additional context\n\nMaybe I'm facing the same problem stated in https://github.com/nuxt/ui/issues/1689\n\n### Logs\n\n```shell-script\n\n```",[3118],{"name":3062,"color":3063},2785,"Nuxt Build Error at build time with Docker","2024-11-27T10:23:20Z","https://github.com/nuxt/ui/issues/2785",0.6753294,{"description":3125,"labels":3126,"number":3132,"owner":3020,"repository":3040,"state":3068,"title":3133,"updated_at":3134,"url":3135,"score":3136},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.18.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: pnpm@9.12.3\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/image@1.8.1, @nuxt/content@2.13.4, @nuxthq/studio@1.1.2, @nuxt/ui-pro@3.0.0-alpha.10, @nuxtjs/plausible@1.2.0, @nuxtjs/seo@2.0.2, @vueuse/nuxt@12.0.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0.alpha10\n\n### Reproduction\n\nhttps://ui3.nuxt.dev/components/button#loading (example with `loading-auto`)\n\n### Description\n\nWhen using a `UIButton` component with an `@click` event, the cursor does not change to `cursor-pointer`, which may confuse users about the button's clickability.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3127,3128,3131],{"name":3062,"color":3063},{"name":3129,"color":3130},"duplicate","cfd3d7",{"name":3034,"color":3035},2940,"`cursor-pointer` is missing on `UButton` with an `@click` event","2025-04-02T09:37:12Z","https://github.com/nuxt/ui/issues/2940",0.6754801,["Reactive",3138],{},["Set"],["ShallowReactive",3141],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$foneSjpNUQ5d50u6iBiRL5j0zPc4jc5EfxPl4g7p474U":-1},"/nuxt/ui/3283"]