\n \u003Cspan class=\"flex items-center gap-2 font-semibold text-lg logo\">example\u003C/span>\n \u003C/div>\n \u003C/template>\n \u003CUNavigationMenu\n orientation=\"vertical\"\n :items=\"links\"\n />\n \u003Cdiv class=\"flex-1\" />\n \u003CUNavigationMenu\n orientation=\"vertical\"\n :items=\"footerLinks\"\n />\n \u003CUSeparator class=\"sticky bottom-0\" />\n \u003Ctemplate #footer>\n \u003Cspan class=\"text-xs text-neutral-500 tracking-tight\">Version {{ useRuntimeConfig().public.version }}\u003C/span>\n \u003C/template>\n \u003C/UDashboardSidebar>\n\n```\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3037,3040,3041],{"name":3038,"color":3039},"bug","d73a4a",{"name":3024,"color":3025},{"name":3042,"color":3043},"pro","5BD3CB",3549,"closed","injection \"Symbol(nuxt-ui.locale-context)\" not found","2025-03-18T11:12:44Z","https://github.com/nuxt/ui/issues/3549",0.7027253,{"description":3051,"labels":3052,"number":3058,"owner":3027,"repository":3028,"state":3045,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### Environment\n\n- Mac OS \n- Node version v20.18.1\n- Nuxt v3.15.4\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.0.0-alpha13\n\n### Reproduction\n\n1. follow installation from guide:\n\nnpx nuxi init -t ui3 \u003Cmy-app>\n\n2. start: npm run dev\n\n\n### Description\n\n\nThere are no colors, no buttons, no borders, no tailwind classes...\n\n\u003Cimg width=\"870\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/e5d46f25-3e77-4509-9349-6bec41ea8d63\" />\n\nI am not sure what happened and when. Just discovered today after cleaning node_modules and reinstalling all packages that tailwind is not loaded correctly. \n\nAs you can see the same is for fresh install from provided starter.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3053,3054,3055],{"name":3038,"color":3039},{"name":3024,"color":3025},{"name":3056,"color":3057},"upstream","78bddb",3374,"Tailwind CSS 4.0.8 not loading correctly","2025-03-14T20:19:15Z","https://github.com/nuxt/ui/issues/3374",0.72102076,{"description":3064,"labels":3065,"number":3067,"owner":3027,"repository":3028,"state":3045,"title":3068,"updated_at":3069,"url":3070,"score":3071},"Currently, portal components (modals, popovers, etc.) are directly attached to the root of the body. It would be beneficial to allow specifying their destination within the configuration .This would provide greater control over rendering order and potential styling conflicts, especially in complex applications with open shadow Dom. \n\nFor instance, a developer might want to render a modal within a specific container to inherit styles or avoid interference with other elements on the page (I currently using Nuxt ui as a web component withing WordPress). \n\nThe proposed configuration option could be a CSS selector string, allowing for flexible targeting of any existing element in the DOM defaulting to 'body'. ",[3066],{"name":3024,"color":3025},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.7310247,{"description":3073,"labels":3074,"number":3082,"owner":3027,"repository":3028,"state":3045,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Description\n\nThere is currently no easy way to know what state the modal is in. Adding a `toggle` method would make life very much easier.\n\nI'm willing to make a PR\n\n### Additional context\n\n_No response_",[3075,3078,3079],{"name":3076,"color":3077},"enhancement","a2eeef",{"name":3024,"color":3025},{"name":3080,"color":3081},"triage","ffffff",3720,"feat: add toogle for useOverlay","2025-04-09T15:26:14Z","https://github.com/nuxt/ui/issues/3720",0.73580647,{"description":3088,"labels":3089,"number":3092,"owner":3027,"repository":3093,"state":3045,"title":3094,"updated_at":3095,"url":3096,"score":3097},"Noticed that the animation on the timeline does not work properly on mobile (only first item appears) AND we have an issue for the image when navigating on client-side (at least on Safari):\n\nhttps://user-images.githubusercontent.com/904724/180595606-b112686f-b2ce-4686-8be6-0620ab31dac5.MOV\n\nAlso notice the layout shift on reload, might be due to a lack of height specified on images.",[3090],{"name":3038,"color":3091},"ff281a",831,"nuxt.com","[Community] About page timeline mobile","2023-02-15T12:31:02Z","https://github.com/nuxt/nuxt.com/issues/831",0.7389982,{"description":3099,"labels":3100,"number":3108,"owner":3027,"repository":3028,"state":3045,"title":3109,"updated_at":3110,"url":3111,"score":3112},"### Description\n\nIm using a prefix in nuxt.ui.config for nuxtui components\n```\n // nuxt ui settings\n ui: {\n colorMode: false, // disable light dark\n prefix: \"Nuxtui\", // component name prefix\n },\n```\n\nNow when I use the code from the table documentation (https://ui3.nuxt.dev/components/table#columns)\nI am getting a warning that UAvatar (which is linked to UBadge somehow) should be defined as custom Element.\n\n\n\n```\nconst nuxtuiBadge = resolveComponent(\"NuxtuiBadge\");\n\n....\n\ncell: ({ row }) => {\n const color = {\n true: \"success\" as const,\n false: \"error\" as const,\n }[row.getValue(\"isActive\") as string];\n\n return h(\n nuxtuiBadge,\n { class: \"capitalize\", variant: \"subtle\", color },\n () => (row.getValue(\"isActive\") ? \"Aktiv\" : \"Inaktiv\")\n );\n},\n\n....\n```\n\n\nDefining UAvatar as a custom element in nuxt.config solves the warning but isnt it a bug?",[3101,3104,3107],{"name":3102,"color":3103},"duplicate","cfd3d7",{"name":3105,"color":3106},"question","d876e3",{"name":3024,"color":3025},3218,"UAvatar warning when using nuxtui prefix, UBadge and h in table cell","2025-02-01T11:31:15Z","https://github.com/nuxt/ui/issues/3218",0.74038947,{"description":3114,"labels":3115,"number":3117,"owner":3027,"repository":3093,"state":3045,"title":3118,"updated_at":3119,"url":3120,"score":3121},"",[3116],{"name":3038,"color":3091},1140,"[Cards]: external links icon missing","2023-02-15T12:31:11Z","https://github.com/nuxt/nuxt.com/issues/1140",0.7403964,{"description":3123,"labels":3124,"number":3128,"owner":3027,"repository":3028,"state":3045,"title":3129,"updated_at":3130,"url":3131,"score":3132},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@10.2.1\n- Builder: -\n- User Config: devtools, modules, css, future, compatibilityDate\n- Runtime Modules: @nuxt/ui@3.0.0, @nuxt/eslint@1.2.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.16.0\n\n### Reproduction\n\nhttps://github.com/deetz99/ui3-layer-test\n\n**Nuxt UI 2 working as expected**\nhttps://github.com/deetz99/ui2-layer-test\n\n### Description\n\nTailwind classes aren't resolved when using layers.\n\nAs seen in the repro, when using `pnpm dev` to run the .playground, the header, footer and layout styles are missing. \n\nUButton is still rendered correctly with the custom blue in the layer main.css file.\n\n`npx nuxi dev` (run the layer) renders the header, footer and layout correctly.\n\nAm I missing something here?\n\n## pnpm dev\n\n\u003Cimg width=\"1720\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/245bae83-2c86-42d1-a883-e472da30e6f7\" />\n\n## npx nuxi dev\n\n\u003Cimg width=\"1717\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c362da21-f5f9-4c7d-a91c-f60bf6de9c0b\" />\n\n### Additional context\n\nThe classes are recognized in the .playground it seems. If I redefine the header, footer and layout in the playground they are displayed correctly. \n\n[header/footer/layout added to .playground](https://github.com/deetz99/ui3-layer-test/tree/test)\n\nIt seems that the styles aren't applied to the components that come from the layer.\n\n### Logs\n\n```shell-script\n\n```",[3125,3126,3127],{"name":3038,"color":3039},{"name":3024,"color":3025},{"name":3080,"color":3081},3544,"Tailwind classes missing when using layers","2025-03-14T19:00:15Z","https://github.com/nuxt/ui/issues/3544",0.7428295,{"description":3134,"labels":3135,"number":3140,"owner":3027,"repository":3028,"state":3045,"title":3141,"updated_at":3142,"url":3143,"score":3144},"### Description\n\nHello, i was wondering if its possible to create something similar to this perhaps using the existing radio-group component.\r\n\r\nExample: https://tailwindui.com/components/application-ui/forms/radio-groups\r\n\u003Cimg width=\"1201\" alt=\"Screenshot 2024-01-11 at 7 59 09 PM\" src=\"https://github.com/nuxt/ui/assets/33962719/5c1bd9cb-7c96-4306-83c5-46eda713de10\">\r\n\n\n### Additional context\n\n_No response_",[3136,3137,3138],{"name":3102,"color":3103},{"name":3076,"color":3077},{"name":3139,"color":3081},"wontfix-v2",1221,"Radio Groups cards","2025-03-24T15:01:33Z","https://github.com/nuxt/ui/issues/1221",0.7480033,["Reactive",3146],{},["Set"],["ShallowReactive",3149],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fVdXKZ5BZlLsom48NzH1Zb0wxGGcTibDA9ib2Vfog5So":-1},"/nuxt/ui/3752"]