\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_",[1984,1987,1990],{"name":1985,"color":1986},"enhancement","a2eeef",{"name":1988,"color":1989},"v3","49DCB8",{"name":1991,"color":1992},"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.73162663,{"description":2002,"labels":2003,"number":2007,"owner":1994,"repository":2008,"state":1996,"title":2009,"updated_at":2010,"url":2011,"score":2012},"### Environment\n\n```\n------------------------------\n- Operating System: Darwin\n- Node Version: v20.13.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.16.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.5.2\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/eslint@0.7.2, nuxt-open-fetch@0.9.5, @nuxtjs/i18n@9.1.0, nuxt-jsonld@2.1.0, @nuxtjs/device@3.2.4, @nuxtjs/robots@5.0.0, @vueuse/nuxt@12.0.0, @sidebase/nuxt-auth@0.9.4, @vesp/nuxt-fontawesome@1.1.0\n- Build Modules: -\n------------------------------\n```\n\n### Reproduction\n\nWhen using a vitest workspace, vitest complains that it can't resolve the config files, this is due to `defineVitestConfig`.\n```\n> vitest\n\nfailed to load config from /Users/reinierkaper/rvezy/rvezy-web-client/src/tests/unit/vitest.config.ts\n```\n\n### Describe the bug\n\nI think the `defineVitestConfig` wrapper conflicts with what vitest expects back in a workspace configuration file.\nEverything works fine when the tests are ran directly with a config file reference, just not in a workspace.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2004],{"name":2005,"color":2006},"bug","d73a4a",1043,"test-utils","Vitest workspaces not properly supported by `defineVitestConfig`","2025-02-21T09:20:04Z","https://github.com/nuxt/test-utils/issues/1043",0.75561905,{"description":2014,"labels":2015,"number":2018,"owner":1994,"repository":2019,"state":2020,"title":2021,"updated_at":2022,"url":2023,"score":2024},"\n\nI believe we should add a check here to make sure the data is correct, otherwise throw (will fallback to the toast error): https://github.com/nuxtlabs/nuxt.com/blob/dev/composables/useProjectComponents.ts#L29\n",[2016],{"name":2005,"color":2017},"ff281a",489,"nuxt.com","closed","Editor cannot load if preview has not `/api/component-meta`","2022-05-11T14:14:55Z","https://github.com/nuxt/nuxt.com/issues/489",0.7014666,{"description":2026,"labels":2027,"number":2033,"owner":1994,"repository":1995,"state":2020,"title":2034,"updated_at":2035,"url":2036,"score":2037},"### For what version of Nuxt UI are you suggesting this?\n\nv3.0.0-alpha.x\n\n### Description\n\nChart is one of many things found when developing a statistics such as in dashboard admin. It would be good if nuxt ui have this component.\n\n### Additional context\n\n_No response_",[2028,2031,2032],{"name":2029,"color":2030},"duplicate","cfd3d7",{"name":1985,"color":1986},{"name":1988,"color":1989},2673,"Chart component","2024-11-18T08:33:07Z","https://github.com/nuxt/ui/issues/2673",0.7221172,{"description":2039,"labels":2040,"number":2045,"owner":1994,"repository":1995,"state":2020,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### For what version of Nuxt UI are you suggesting this?\n\nv2.x\n\n### Description\n\nWhen validating an object, a FormGroup does not display validations of specific properties (at least not with details).\n\nWould it make sense for the name `myobj` to display errors from anything that looks like `myobj\\..*` ? it could show all of them, each on a newline.\n\n### Additional context\n\nhttps://github.com/nuxt/ui/issues/1898",[2041,2042,2044],{"name":1985,"color":1986},{"name":2043,"color":1992},"wontfix-v2",{"name":1988,"color":1989},2569,"Display zod validation errors based on prefix","2024-11-11T18:28:09Z","https://github.com/nuxt/ui/issues/2569",0.7290693,{"description":2051,"labels":2052,"number":2057,"owner":1994,"repository":1995,"state":2020,"title":2058,"updated_at":2059,"url":2060,"score":2061},"### Description\n\nI want to configure my Nuxt UI v3 project only to use black and white colors with the neutral palette from Tailwind, similar to the one found in shadcn. I understand Nuxt UI supports Tailwind CSS theming, but I’m unsure of the best/recommended way to override all component colors globally",[2053,2056],{"name":2054,"color":2055},"question","d876e3",{"name":1988,"color":1989},3200,"How to create a black & white only theme in Nuxt UI v3","2025-02-09T12:59:38Z","https://github.com/nuxt/ui/issues/3200",0.7337714,{"description":2063,"labels":2064,"number":2067,"owner":1994,"repository":1995,"state":2020,"title":2068,"updated_at":2069,"url":2070,"score":2071},"### 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_",[2065,2066],{"name":1985,"color":1986},{"name":1988,"color":1989},2302,"Form validation properties","2025-01-24T18:10:45Z","https://github.com/nuxt/ui/issues/2302",0.7364758,{"description":2073,"labels":2074,"number":2076,"owner":1994,"repository":1995,"state":2020,"title":2077,"updated_at":2078,"url":2079,"score":2080},"### Environment\n\nNuxt project info: 12:26:48 PM\r\n\r\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.16.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.13.1\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.9.0\r\n- Builder: -\r\n- User Config: devtools, ssr, typescript, imports, modules, svgo, mongoose, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/test-utils/module@3.14.1, nuxt-mongoose@1.0.6, @pinia/nuxt@0.5.4, @nuxt/ui@2.18.4, @nuxtjs/i18n@8.5.2, nuxt-svgo@4.0.5\r\n- Build Modules: -\r\n------------------------------\n\n### Version\n\nv2.18.4\n\n### Reproduction\n\nthe online address: https://nano-portfolio-ruby.vercel.app/\r\nthe repo: https://github.com/gaomingzhao666/nano-portfolio\n\n### Description\n\nHey, I don't install `nuxt-icon` module and I can use icons directly in `nuxt-ui`, because I think the `nuxt-ui` already integrated `nuxt-icon` module.\r\n\r\nThe problem is: that the icon is empty when users first enter the page that shows icons, and when I turn off the computer and open it in next day, the bug is reproduced.\r\n\r\nI think the server cache is not working properly, should I install `nuxt-icon` module manually or it's just a bug to `nuxt-ui`\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2075],{"name":2005,"color":2006},2195,"the `icon` component that integrated in `nuxt-ui` by default is not shown at first loading","2024-09-27T04:02:26Z","https://github.com/nuxt/ui/issues/2195",0.74082905,{"description":2082,"labels":2083,"number":2086,"owner":1994,"repository":1995,"state":2020,"title":2087,"updated_at":2088,"url":2089,"score":2090},"### Description\n\nThe concepts of Chips and Badges are reversed. \n\nChip is the component with text, to represent status or options selected, that can also have counters, icons aside labels and in some cases a remove button.\nBadge is the component that have a notification or a counter\n\nIn my opinion:\n\nThis is a chip ⤵️\n\n\nAnd this is a Badge ⤵️\n\n\nAn example\nhttps://medium.com/design-bootcamp/ux-blueprint-03-badges-vs-chips-tags-a-friendly-guide-e38ab2217be3#:~:text=Key%20Differences,users%20navigate%20and%20manage%20content.",[2084,2085],{"name":2054,"color":2055},{"name":1988,"color":1989},3282,"The concepts of Chips and Badges are reversed","2025-02-10T09:38:39Z","https://github.com/nuxt/ui/issues/3282",0.7464313,{"labels":2092,"number":2101,"owner":1994,"repository":1994,"state":2020,"title":2102,"updated_at":2103,"url":2104,"score":2105},[2093,2095,2098],{"name":2094,"color":1992},"stale",{"name":2096,"color":2097},"pending triage","E99695",{"name":2099,"color":2100},"2.x","d4c5f9",6198,"Key Events blocked / not working reliably","2023-01-22T15:34:44Z","https://github.com/nuxt/nuxt/issues/6198",0.7495583,["Reactive",2107],{},["Set"],["ShallowReactive",2110],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"nqwykaajSc3y8_u9Yd0t5TyJd7oA3-c1XireKj2LKiw":-1},"/nuxt/ui/3685"]