`\n\nit doesn't work that way\n\nI really ask for help!",[1984,1987],{"name":1985,"color":1986},"question","d876e3",{"name":1988,"color":1989},"v3","49DCB8",3098,"nuxt","ui","open","Table filtered, sorting fetch","2025-01-14T11:05:37Z","https://github.com/nuxt/ui/issues/3098",0.68387973,{"description":1999,"labels":2000,"number":2005,"owner":1991,"repository":1992,"state":1993,"title":2006,"updated_at":2007,"url":2008,"score":2009},"### Description\n\nI have defined some css variables in css file that is located in `app/styles/main.css location`. I can use these in tw like so `bg-[--primary]`\r\n\r\nbut how do i use this with `UI` lib ? for example using with Card component? \r\n\r\n```\r\n:root {\r\n\t--bg: #f5f6ce;\r\n\t--primary: #2ab4f6;\r\n\t--r-sm: 5px;\r\n}\r\n```",[2001,2002],{"name":1985,"color":1986},{"name":2003,"color":2004},"stale","ededed",2270,"How to use css variables defined in css file in UI","2024-11-27T02:06:52Z","https://github.com/nuxt/ui/issues/2270",0.6903862,{"description":2011,"labels":2012,"number":2020,"owner":1991,"repository":1992,"state":1993,"title":2021,"updated_at":2022,"url":2023,"score":2024},"### Environment\n\nnode22, nuxtui300-b3 and nuxt3\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv.3.0.0-beta3\n\n### Reproduction\n\nYou can reproduce from the components page for modal and drawer. Open the drawer, the bottom drawer appears, and rest of page shifts from removal of scrollbar. Same does not occur on the modal component.\n\n### Description\n\nThe modal component properly handles overflow and prevents shifting of the main page layout when open. The drawer component does not. Would like to see the drawer prevent layout shift from the scroll bar removal, like is done on the modals. \n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2013,2016,2017],{"name":2014,"color":2015},"bug","d73a4a",{"name":1988,"color":1989},{"name":2018,"color":2019},"triage","ffffff",3523,"Drawer shifts layout unlike modal","2025-03-23T17:40:06Z","https://github.com/nuxt/ui/issues/3523",0.6957081,{"description":2026,"labels":2027,"number":2032,"owner":1991,"repository":1992,"state":1993,"title":2033,"updated_at":2034,"url":2035,"score":2036},"",[2028,2031],{"name":2029,"color":2030},"feature","A27AF6",{"name":1988,"color":1989},2322,"[MeterGroup] Implement component","2025-04-07T09:36:44Z","https://github.com/nuxt/ui/issues/2322",0.6961596,{"description":2038,"labels":2039,"number":2045,"owner":1991,"repository":1992,"state":1993,"title":2046,"updated_at":2047,"url":2048,"score":2049},"### Description\n\nWhen adding `UButton` component with `ghost` or `link` variant inside a `UBanner` with `links` attribute, they remain displayed in black text, even if the banner has a dark background (e.g., primary color). Unlike the Banner close button, which has specific Tailwind classes that adapt it to dark mode (white text), these elements do not automatically adjust their colors.\n\n\n\n```html\n \u003CUBanner to=\"/guide-gouvernance-associative-crise\" icon=\"i-ph-books-duotone\" title=\"Guide Gouvernance Associative\" :actions=\"[{label: 'Lire le guide', to: '/guide-gouvernance-associative-crise', variant: 'ghost', size: 'md', trailingIcon: 'i-ph-arrow-right'}, {label: 'Lire le guide', to: '/guide-gouvernance-associative-crise', variant: 'link', size: 'md'}]\" close />\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_",[2040,2043,2044],{"name":2041,"color":2042},"enhancement","a2eeef",{"name":1988,"color":1989},{"name":2018,"color":2019},3307,"Better handling of `UButton`, `UBadge`, … colors on colored backgrounds","2025-02-13T19:05:27Z","https://github.com/nuxt/ui/issues/3307",0.69897896,{"description":2051,"labels":2052,"number":2055,"owner":1991,"repository":1992,"state":2056,"title":2057,"updated_at":2058,"url":2059,"score":2060},"### 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```",[2053,2054],{"name":2014,"color":2015},{"name":1988,"color":1989},3267,"closed","Modal content slot causes accessibility issues","2025-02-21T10:49:04Z","https://github.com/nuxt/ui/issues/3267",0.63597196,{"description":2062,"labels":2063,"number":2069,"owner":1991,"repository":1992,"state":2056,"title":2070,"updated_at":2071,"url":2072,"score":2073},"### Environment\n\nlatest\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha.13\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/gifted-moon-ms65xm\n\n### Description\n\nhovering over a open drop down item in a drawer results in a recursion error.\n\n### Additional context\n\n```vue\n\u003Cscript setup lang=\"ts\">\nconst items = ref([\n {\n label: 'hover me for a recursion error',\n },\n])\n\u003C/script>\n\n\n\u003Ctemplate>\n \u003CUDrawer>\n \u003CUButton label=\"Open Drawer\"/>\n \u003Ctemplate #content>\n \u003CUDropdownMenu\n :items=\"items\"\n >\n \u003CUButton label=\"Open Drop down\"/>\n \u003C/UDropdownMenu>\n \u003C/template>\n \u003C/UDrawer>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\nUncaught InternalError: too much recursion\n NuxtJS 5\n focus\n handleFocusOut\n ct\n f\n focus\n```",[2064,2065,2066],{"name":2014,"color":2015},{"name":1988,"color":1989},{"name":2067,"color":2068},"reka-ui","56d799",3357,"Cant put dropdown inside drawer","2025-04-08T19:49:57Z","https://github.com/nuxt/ui/issues/3357",0.6399858,{"description":2075,"labels":2076,"number":2083,"owner":1991,"repository":1992,"state":2056,"title":2084,"updated_at":2085,"url":2086,"score":2087},"### 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```",[2077,2078,2079,2082],{"name":2014,"color":2015},{"name":1988,"color":1989},{"name":2080,"color":2081},"pro","5BD3CB",{"name":2018,"color":2019},3657,"Setting ui.colorMode = false breaks nuxi typecheck","2025-03-27T20:54:57Z","https://github.com/nuxt/ui/issues/3657",0.65904784,{"description":2089,"labels":2090,"number":2093,"owner":1991,"repository":1992,"state":2056,"title":2094,"updated_at":2095,"url":2096,"score":2097},"### 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```",[2091,2092],{"name":2014,"color":2015},{"name":1988,"color":1989},2655,"Classes of container component are not working properly","2024-11-16T13:13:33Z","https://github.com/nuxt/ui/issues/2655",0.673685,{"description":2099,"labels":2100,"number":2103,"owner":1991,"repository":2104,"state":2056,"title":2105,"updated_at":2106,"url":2107,"score":2108},"Hello, thanks for open-sourcing this repo. I'm exploring the app. \r\n\r\nI would like to understand why pathPrefix is not getting applied to components within the folder `~/components/content`? Is this a convention that's undocumented? Thanks. \r\n\r\n\r\n",[2101],{"name":1985,"color":2102},"ff1ab2",1418,"nuxt.com","Understanding why pathPrefix not set for components/content ","2023-11-21T10:07:33Z","https://github.com/nuxt/nuxt.com/issues/1418",0.67786705,["Reactive",2110],{},["Set"],["ShallowReactive",2113],{"TRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"7ynGaRdVHCynL0VlgK51E1TIAyd17_XhduPFJEAgMMw":-1},"/nuxt/ui/2978"]