\n \u003CNuxtWelcome />\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup lang=\"ts\">\nconsole.log(\"111\");\n\u003C/script>\n```\n\n### Expected Behavior\nBuilt-in components should be auto-imported without errors during development.\n\n### Actual Behavior\nConsole errors occur for built-in components (e.g., `NuxtWelcome`), and auto-importing fails.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\nWARN [Vue warn]: Failed to resolve component: NuxtRouteAnnouncer\nIf this is a native custom element, make sure to exclude it from component resolution via compilerOptions.isCustomElement. \n at \u003CApp> \n at \u003CNuxtRoot>\n\nthis is setup\n```",[2898],{"name":2899,"color":2900},"pending triage","E99695",32290,"[Bug] AutoImport Fails for Components with `vite.esbuild.minifyWhitespace=true` in Dev Mode","2025-06-04T10:57:34Z","https://github.com/nuxt/nuxt/issues/32290",0.7274661,{"description":2907,"labels":2908,"number":2912,"owner":2877,"repository":2878,"state":2879,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Environment\n\n```\n System:\n OS: macOS 15.5\n CPU: (14) arm64 Apple M3 Max\n Memory: 555.83 MB / 36.00 GB\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 23.11.0 - /opt/homebrew/bin/node\n Yarn: 1.22.22 - /opt/homebrew/bin/yarn\n npm: 10.9.2 - /opt/homebrew/bin/npm\n pnpm: 9.12.3 - /opt/homebrew/bin/pnpm\n Watchman: 2025.04.28.00 - /opt/homebrew/bin/watchman\n npmPackages:\n nuxt: ^3.17.3 => 3.17.4 \n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.17.4\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/nuxt-ui3-n3sxks\n\n### Description\n\nWhen using the UNavigationMenu component from Nuxt UI 3 in a fresh Nuxt 3 app, the following warning appears in the browser console:\n\n```shell-script\n> [Vue warn] toRefs() expects a reactive object but received a plain one.\n```\n\nThis occurs even when rendering the component barebones:\n\n**pages/index.vue:**\n\n```vue\n\u003Cscript setup lang=\"ts\">\nimport type { NavigationMenuItem } from '@nuxt/ui'\n\nconst items = ref\u003CNavigationMenuItem[]>([\n {\n label: 'Guide',\n icon: 'i-lucide-book-open',\n to: '/getting-started',\n children: [\n {\n label: 'Introduction',\n description: 'Fully styled and customizable components for Nuxt.',\n icon: 'i-lucide-house'\n },\n {\n label: 'Installation',\n description: 'Learn how to install and configure Nuxt UI in your application.',\n icon: 'i-lucide-cloud-download'\n },\n {\n label: 'Icons',\n icon: 'i-lucide-smile',\n description: 'You have nothing to do, @nuxt/icon will handle it automatically.'\n },\n {\n label: 'Colors',\n icon: 'i-lucide-swatch-book',\n description: 'Choose a primary and a neutral color from your Tailwind CSS theme.'\n },\n {\n label: 'Theme',\n icon: 'i-lucide-cog',\n description: 'You can customize components by using the `class` / `ui` props or in your app.config.ts.'\n }\n ]\n },\n {\n label: 'Composables',\n icon: 'i-lucide-database',\n to: '/composables',\n children: [\n {\n label: 'defineShortcuts',\n icon: 'i-lucide-file-text',\n description: 'Define shortcuts for your application.',\n to: '/composables/define-shortcuts'\n },\n {\n label: 'useOverlay',\n icon: 'i-lucide-file-text',\n description: 'Display a modal/slideover within your application.',\n to: '/composables/use-overlay'\n },\n {\n label: 'useToast',\n icon: 'i-lucide-file-text',\n description: 'Display a toast within your application.',\n to: '/composables/use-toast'\n }\n ]\n },\n {\n label: 'Components',\n icon: 'i-lucide-box',\n to: '/components',\n active: true,\n children: [\n {\n label: 'Link',\n icon: 'i-lucide-file-text',\n description: 'Use NuxtLink with superpowers.',\n to: '/components/link'\n },\n {\n label: 'Modal',\n icon: 'i-lucide-file-text',\n description: 'Display a modal within your application.',\n to: '/components/modal'\n },\n {\n label: 'NavigationMenu',\n icon: 'i-lucide-file-text',\n description: 'Display a list of links.',\n to: '/components/navigation-menu'\n },\n {\n label: 'Pagination',\n icon: 'i-lucide-file-text',\n description: 'Display a list of pages.',\n to: '/components/pagination'\n },\n {\n label: 'Popover',\n icon: 'i-lucide-file-text',\n description: 'Display a non-modal dialog that floats around a trigger element.',\n to: '/components/popover'\n },\n {\n label: 'Progress',\n icon: 'i-lucide-file-text',\n description: 'Show a horizontal bar to indicate task progression.',\n to: '/components/progress'\n }\n ]\n },\n {\n label: 'GitHub',\n icon: 'i-simple-icons-github',\n badge: '3.8k',\n to: 'https://github.com/nuxt/ui',\n target: '_blank'\n },\n {\n label: 'Help',\n icon: 'i-lucide-circle-help',\n disabled: true\n }\n])\n\u003C/script>\n\u003Ctemplate>\n \u003CUNavigationMenu :items=\"items\" class=\"w-full justify-center\" />\n\u003C/template>\n\n```\n\n**Minimal Reproduction**\nRepro created using Nuxt 3 + Nuxt UI 3 starter structure.\n\npackage.json:\n```json\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 \"lint\": \"eslint .\",\n \"lint:fix\": \"eslint --fix .\"\n },\n \"dependencies\": {\n \"@iconify-json/lucide\": \"^1.2.44\",\n \"@iconify-json/simple-icons\": \"^1.2.35\",\n \"@nuxt/ui\": \"^3.1.1\",\n \"nuxt\": \"^3.17.3\"\n },\n \"devDependencies\": {\n \"@nuxt/eslint\": \"^1.4.1\",\n \"eslint\": \"^9.27.0\",\n \"typescript\": \"^5.8.3\"\n }\n}\n```\n\nNotes\n\t•\tReproduces consistently in local dev.\n\t•\tDoes not reproduce on Codesandbox with the Nuxt UI 3 starter (possibly due to different runtime setup).\n\t•\tNo functional issues observed so far, but the warning pollutes the console.\n\t•\tThis warning has only recently started appearing in the console logs, despite no code changes to this component on our end — possibly introduced in a recent dependency update.\n",[2909,2910,2911],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},4257,"[Vue warn] toRefs() expects a reactive object but received a plain one - \u003CUNavigationMenu />","2025-05-29T23:48:43Z","https://github.com/nuxt/ui/issues/4257",0.7276407,{"description":2918,"labels":2919,"number":2924,"owner":2877,"repository":2877,"state":2879,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Environment\n\n#### My machine:\n- Operating System: Windows_NT\n- Node Version: v20.16.0\n- Nuxt Version: 3.14.1592\n- CLI Version: 3.15.0\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.8.3\n- Builder: -\n- User Config: default\n- Runtime Modules: -\n- Build Modules: -\n\n#### CodeSandbox reproduction:\n- Operating System: Linux\n- Node Version: v20.12.0\n- Nuxt Version: 3.10.1\n- CLI Version: 3.10.0\n- Nitro Version: 2.8.1\n- Package Manager: npm@10.5.0\n- Builder: -\n- User Config: devtools\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nDemo: https://codesandbox.io/p/devbox/2n7n2z\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cmain />\n \u003CTeleport defer to=\"main\">\n \u003CNuxtLayout>\n \u003CNuxtPage />\n \u003C/NuxtLayout>\n \u003C/Teleport>\n \u003C/div>\n\u003C/template>\n```\n\n### Describe the bug\n\nUsing the \u003CNuxtLayout> component within a deferred Teleport consistently throws the following warning in the console:\n\n```\n WARN [nuxt] Your project has pages but the \u003CNuxtPage /> component has not been used. You might be using the \u003CRouterView /> component instead, which will not work correctly in Nuxt. You can set pages: false in nuxt.config if you do not wish to use the Nuxt vue-router integration.\n```\n\nThis does not occur if the Teleport is not deferred, but I need to defer it for my use case. It also does not occur if `ssr: false` is specified, so I assume the `app:rendered` and `app:suspense:resolve` hooks are probably [relevant](https://github.com/nuxt/nuxt/blob/edc299a04344897ac110aca3b3a2c2705b0cef35/packages/nuxt/src/pages/runtime/plugins/check-if-page-unused.ts#L22). \n\nVue lets me suppress the inevitable hydration mismatch warning with `\u003Cmain data-allow-mismatch=\"children\" />`, but Nuxt does not let me suppress the warning, so it clutters the console.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2920,2921],{"name":2899,"color":2900},{"name":2922,"color":2923},"dx","C39D69",30001,"\u003CNuxtLayout> within \u003CTeleport defer> throws warning: \"Your project has pages but the \u003CNuxtPage /> component is not being used\"","2024-11-27T15:13:13Z","https://github.com/nuxt/nuxt/issues/30001",0.7296236,{"description":2930,"labels":2931,"number":2933,"owner":2877,"repository":2877,"state":2934,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Environment\n\n- Operating System: Linux\n- Node Version: v18.20.3\n- Nuxt Version: 3.15.4\n- CLI Version: 3.22.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.2.3\n- Builder: -\n- User Config: future, compatibilityDate, devtools, srcDir, serverDir, dir\n- Runtime Modules: -\n- Build Modules: -\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-c3zbe4c6-cpg2sv8f\n\n### Describe the bug\n\nIntended Directory Structure:\n\n```\n.\n├── nuxt.config.ts\n└── src\n ├── app ✅ works\n │ ├── app.vue\n │ └── utils ✅ auto-import works\n │ └── app-utils.ts\n ├── public ✅ works\n │ └── public.txt\n ├── server ✅ works\n │ └── utils ✅ auto-import works\n │ └── server-utils.ts\n └── shared 🚫 auto-import fail\n └── shared-utils.ts\n```\n\nNuxt Config:\n\n```typescript\nexport default defineNuxtConfig({\n future: { compatibilityVersion: 4 },\n compatibilityDate: '2024-11-01',\n devtools: { enabled: true },\n\n srcDir: 'src/app',\n serverDir: 'src/server',\n dir: {\n public: 'src/public',\n shared: 'src/shared', // 🚫 this got ignored\n },\n});\n```\n\nThere is no viable workarounds (i.e. imports.dir works for `srcDir` but not `serverDir`), other than doing manual imports.\n\n### Additional context\n\nInspecting the generated types in .nuxt suggests `options.dir.shared` is ignored during auto-import.\n\nFrom reproduction\n\napp.vue\n\n```vue\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cul>\n \u003Cli>Function from app/utils: {{ appUtilsFunction() }}\u003C/li>\n \u003Cli>\n Function from shared/utils: {{ catchWrapper(sharedUtilsFunction) }}\n \u003C/li>\n \u003C/ul>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript setup>\nconst catchWrapper = (fn) => {\n try {\n return fn();\n } catch {\n return 'Unable to access this function';\n }\n};\n\u003C/script>\n```\n\nshows\n```\nFunction from app/utils: This works!\nFunction from shared/utils: Unable to access this function\n```\n\nroutes/server.js\n\n```javascript\nexport default defineEventHandler(() => {\n const outputFromServerUtils = serverUtilsFunction();\n\n let outputFromSharedUtils;\n try {\n outputFromSharedUtils = sharedUtilsFunction();\n } catch {}\n\n return {\n serverUtilsFunction: outputFromServerUtils,\n sharedUtilsFunction: outputFromSharedUtils ?? '',\n };\n});\n```\n\nshows\n\n```json\n{\n \"serverUtilsFunction\": \"This works!\",\n \"sharedUtilsFunction\": \"\"\n}\n```\n\n### Logs\n\n```shell-script\n\n```",[2932],{"name":2899,"color":2900},31082,"closed","Nuxt config's `dir.shared` is ignored in auto-imports","2025-02-23T09:31:41Z","https://github.com/nuxt/nuxt/issues/31082",0.70834446,{"description":2940,"labels":2941,"number":2950,"owner":2877,"repository":2878,"state":2934,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Environment\n\n- Nuxt Vesrion: '3.15.1'\n- Nuxt/ui Version: '3.0.1'\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.15.1\n\n### Reproduction\n\nhttps://github.com/nuxt/ui/pull/2251\n\n### Description\n\nThis issue was previously addressed and fixed in [PR #2251](https://github.com/nuxt/ui/pull/2251). However, after upgrading to Nuxt UI v3.0.1, the dir prop no longer exists, making it impossible to switch the direction of the Carousel.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2942,2943,2946,2947],{"name":2868,"color":2869},{"name":2944,"color":2945},"needs reproduction","CB47CF",{"name":2871,"color":2872},{"name":2948,"color":2949},"closed-by-bot","ededed",3705,"Missing \"dir\" Prop in Carousel Component After Nuxt UI v3.0.1 Update","2025-05-31T02:09:01Z","https://github.com/nuxt/ui/issues/3705",0.70878226,{"description":2956,"labels":2957,"number":2962,"owner":2877,"repository":2877,"state":2934,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Environment\r\n\r\n- Operating System: `Darwin`\r\n- Node Version: `v16.17.0`\r\n- Nuxt Version: `3.4.1`\r\n- Nitro Version: `2.3.3`\r\n- Package Manager: `npm@8.15.0`\r\n- Builder: `vite`\r\n- User Config: `runtimeConfig`, `app`, `css`, `components`\r\n- Runtime Modules: `-`\r\n- Build Modules: `-`\r\n\r\n\r\n### Reproduction\r\n\r\npage/[...id].vue\r\n\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Ccomponent\r\n v-for=\"(item, key) in data\"\r\n :key=\"key\"\r\n :is=\"item.type\" \r\n \r\n v-bind=\"item\"\r\n\r\n @lgc-action=\"$emit($event.handler, $event)\"\r\n\r\n\r\n @update:payload=\"(value) => item.payload = value\"\r\n @update:form=\"(value) => item.form = value\"\r\n @update:restriction=\"(value) => item.restriction = value\"/>\r\n \r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\n\r\n const route = useRoute()\r\n const runtimeConfig = useRuntimeConfig()\r\n const [path] = route.params.id.slice(-1)\r\n const { data } = reactive(await $fetch(`${runtimeConfig.public.BASE_URL}${runtimeConfig.public.SERVICE}/web/portal/${runtimeConfig.public.POI_NAME}/form/${path}`))\r\n \r\n\u003C/script>\r\n```\r\n\r\n\r\ncomponent/form.vue\r\n\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"lgc-form-input-group\">\r\n \u003Cp v-if=\"label\" class=\"lgc-form-input-group__label\">{{ label }}\u003C/p>\r\n \u003Cdiv class=\"lgc-form-input-group__form\">\r\n \u003C!-- v-bind=\"!item.type.toLowerCase().includes('form') ? { data: item } : item\" -->\r\n \u003Ccomponent :attr=\"index\" v-for=\"(item, index) in data\" :key=\"index\" :is=\"item.type\" v-bind=\"item\" \r\n @update:isValid=\"item.isValid = $event\"\r\n @emit-value=\"constructPayload(item, $event)\"\r\n @emit-input-and-value=\"constructPayload($event.input, $event.payload)\"\r\n @add-error=\"errorManagement('add', $event)\"\r\n @remove-error=\"errorManagement('remove', $event)\"\r\n @lgc-action=\"$emit($event.handler, $event)\"\r\n >\u003C/component>\r\n \u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup>\r\nimport { v4 as uuidv4 } from 'uuid';\r\n\r\nconst emit = defineEmits(['emit-value','lgc-action'])\r\n\r\nconst props = defineProps({\r\n data: {\r\n type: Array,\r\n required: true\r\n },\r\n id: {\r\n type: String,\r\n required: false\r\n },\r\n label: {\r\n type: String,\r\n required: false\r\n },\r\n value: {\r\n type: Object,\r\n required: false,\r\n default() {\r\n return {}\r\n }\r\n },\r\n uuid: {\r\n type: String,\r\n required: false,\r\n default() {\r\n return uuidv4()\r\n }\r\n }\r\n })\r\n\r\n\r\n const inputValue= reactive(props.value ? props.value : {})\r\n\r\n function constructPayload(input, payload) {\r\n inputValue[input.id] = payload\r\n }\r\n\r\n function errorManagement(action, error) {\r\n let component = props.data.find(el => el.type === 'lgc-form-error');\r\n if (component) {\r\n let already = component.errors.find(el => el.key === error.key && el.byClient)\r\n let index = component.errors.indexOf(already)\r\n switch (action) {\r\n case 'add':\r\n if (component) {\r\n if (already) component.errors.splice(index, 1)\r\n if (error.value) component.errors.push(error)\r\n }\r\n break;\r\n case 'remove':\r\n if (component) {\r\n if (already) component.errors.splice(index, 1)\r\n }\r\n break;\r\n default:\r\n break;\r\n }\r\n } else {\r\n emit(`${action}-error`, error)\r\n }\r\n }\r\n\r\n async function submit() {\r\n emit('emit-value', inputValue)\r\n }\r\n\r\n\u003C/script>\r\n\r\n```\r\n\r\n### Describe the bug\r\n\r\nThe problem occurred when switching from nuxt2 to nuxt3.\r\nthis is a problem with the display order of compose with the `\u003Ccomponent :is=\"\" v-for=\"\" :key=\"\">` tag, in all that I find as documentation, it tells me offers 2 solutions:\r\n- make a sort function but even then, it doesn't work\r\n- that it is an asynchronous problem and must be made synchronous. Off, nuxt3 with \u003Cscript setup> makes compose directly asynchronous. It would then possibly be a \"bug\" linked to the frame work.\r\n\r\nafterwards, I haven't seen any documentation on the problem caused here: depending on the index, the order changes.\r\nIn addition to the tests you had done, I tried to put a uuid in key, the whole display is reversed.\r\nwithout key, it's good\r\nthe index, gives the current problem\r\na fixed key or just the item gives an even different display.\r\nregarding the key, ideally, the uuid should be in the object since using the index seems to be a bad practice\r\n \r\n The problem occurs in the compose form\r\n \r\n result nuxt 2 & nuxt3 no :key\r\n\u003Cimg width=\"701\" alt=\"Capture d’écran 2023-04-26 à 10 51 51\" src=\"https://user-images.githubusercontent.com/98752049/234523209-431b7cfc-d0c0-4397-a82d-d6120635a12a.png\">\r\n\r\nresult nuxt 3 whit :key=\"index\"\r\n\u003Cimg width=\"675\" alt=\"Capture d’écran 2023-04-26 à 10 55 16\" src=\"https://user-images.githubusercontent.com/98752049/234524004-76a98dde-1312-4266-9455-d9f28c1c521d.png\">\r\n\r\nresult nuxt3 whit :key=\"uuidv4()\"\r\n\u003Cimg width=\"678\" alt=\"Capture d’écran 2023-04-26 à 10 57 25\" src=\"https://user-images.githubusercontent.com/98752049/234524648-d85ae34d-70b5-4f58-a23d-005e8afd829a.png\">\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2958,2961],{"name":2959,"color":2960},"3.x","29bc7f",{"name":2899,"color":2900},20522,"Nuxt2 to Nuxt3, not display component in a correct order ","2023-04-26T09:06:18Z","https://github.com/nuxt/nuxt/issues/20522",0.7157392,{"description":2968,"labels":2969,"number":2971,"owner":2877,"repository":2877,"state":2934,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Environment\n\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v20.14.0\r\n- Nuxt Version: 3.12.4\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: pnpm@9.7.1\r\n- Builder: -\r\n- User Config: runtimeConfig, extends, modules, ui, colorMode, routeRules, devtools, typescript, future, eslint, nitro, i18n, compatibilityDate\r\n- Runtime Modules: @nuxt/eslint@0.5.0, @nuxt/fonts@0.7.1, @nuxt/ui@2.18.4, @vueuse/nuxt@10.11.0, @nuxtjs/i18n@8.5.0\r\n- Build Modules: -\r\n------------------------------\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-u6tm1b?file=app.vue\n\n### Describe the bug\n\nWhen using a `v-model` prop with some initial object values (such as fetched already selected data from backend), the `\u003CUSelectMenu>` component doesn't show these as selected and seems to ignore them completely.\r\n\r\nEven when selecting the same objects again, it just seems to add them to the array and disregard anything, that was there previously.\n\n### Additional context\n\nThe behaviour changes when setting the `by` prop. In my case, I set it to `id`, after which I can see the object as selected, **but only** in the dropdown.\r\nThe button itself still shows `0 selected`.\n\n### Logs\n\n_No response_",[2970],{"name":2899,"color":2900},28733,"SelectMenu initial object values","2024-08-28T03:27:34Z","https://github.com/nuxt/nuxt/issues/28733",0.72176605,{"description":2977,"labels":2978,"number":2982,"owner":2877,"repository":2878,"state":2934,"title":2983,"updated_at":2984,"url":2985,"score":2986},"### Environment\n\n- Operating System: `Linux`\n- Node Version: `v22.14.0`\n- Nuxt Version: `3.17.3`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `bun@1.2.13`\n- Builder: `-`\n- User Config: `future`, `compatibilityDate`, `devtools`, `modules`, `css`, `components`, `i18n`, `icon`, `runtimeConfig`, `app`, `hooks`, `site`, `sitemap`, `pwa`, `fonts`\n- Runtime Modules: `@nuxt/eslint@1.4.0`, `@nuxt/fonts@0.11.4`, `@nuxt/image@1.10.0`, `@nuxt/scripts@0.11.7`, `@nuxt/ui@3.1.2`, `@nuxtjs/i18n@9.5.4`, `@vueuse/nuxt@13.2.0`, `@pinia/nuxt@0.11.0`, `@nuxtjs/sitemap@7.2.10`, `@vite-pwa/nuxt@1.0.1`\n- Build Modules: `-`\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3.1.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/wizardly-shamir-f8924y\n\n### Description\n\nThe `URadioGroup` component's table variant renders borders incorrectly in RTL mode. This appears to be a visual issue specific to RTL layouts. The expected result is that borders should match the appearance of the LTR layout, but they do not.\n\n### Additional context\n\nIn LTR Mode:\n\n\nIn RTL Mode:\n",[2979,2980,2981],{"name":2868,"color":2869},{"name":2871,"color":2872},{"name":2874,"color":2875},4190,"URadioGroup table variant borders display incorrectly in RTL mode","2025-05-22T12:36:45Z","https://github.com/nuxt/ui/issues/4190",0.72266716,["Reactive",2988],{},["Set"],["ShallowReactive",2991],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fciN4918nR-7V2ZWECv7qEzoXelLaNDFvKA_PvLaVi7Q":-1},"/nuxt/ui/4131"]