\n\n \u003Ctemplate #panel>\n \u003CRegioloketPreview \n :data=\"row\"\n />\n \u003C/template>\n \u003C/UPopover>\n \u003C/template>\n\n```\n\n",[2891,2892],{"name":2866,"color":2867},{"name":2893,"color":2894},"stale","ededed",2435,"@hover event for UTable rows","2025-02-14T01:58:49Z","https://github.com/nuxt/ui/issues/2435",0.80737865,{"description":2901,"labels":2902,"number":2908,"owner":2872,"repository":2873,"state":2909,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### 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?",[2903,2906,2907],{"name":2904,"color":2905},"duplicate","cfd3d7",{"name":2866,"color":2867},{"name":2869,"color":2870},3218,"closed","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.6962932,{"description":2915,"labels":2916,"number":2920,"owner":2872,"repository":2921,"state":2909,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v21.5.0`\r\n- Nuxt Version: `3.9.0`\r\n- CLI Version: `3.10.0`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.4`\r\n- Builder: `-`\r\n- User Config: `alias`, `app`, `devtools`, `eslint`, `i18n`, `imports`, `modules`, `nitro`, `runtimeConfig`, `ssr`, `testUtils`, `typescript`, `vite`, `vuetify`\r\n- Runtime Modules: `@pinia-plugin-persistedstate/nuxt@1.2.0`, `@pinia/nuxt@0.5.1`, `@nuxtjs/i18n@8.0.0`, `@nuxtjs/eslint-module@4.1.0`, `nuxt-typed-router@3.5.0`, `@nuxt/test-utils/module@3.9.0`, `vuetify-nuxt-module@0.7.3`, `nuxt-lodash@2.5.3`\r\n- Build Modules: `-`\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-cyqbu8\n\n### Describe the bug\n\nAfter upgrading to 3.9.0, I am getting errors when running tests due to missing identifiers in the nuxt package. Reproduction shows error from my middleware test but I get similar errors when running component tests but this time the error is \"Error: Missing \"#build/paths.mjs\" specifier in \"nuxt\" package\"\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2917],{"name":2918,"color":2919},"pending triage","5D08F5",679,"test-utils","Error running test after upgrade to 3.9.0","2024-01-28T11:25:59Z","https://github.com/nuxt/test-utils/issues/679",0.7142095,{"description":2927,"labels":2928,"number":2936,"owner":2872,"repository":2873,"state":2909,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Environment\n\n- Operating System: Darwin\n- Node Version: v22.11.0\n- Nuxt Version: 3.16.0\n- CLI Version: 3.22.5\n- Nitro Version: 2.11.6\n- Package Manager: pnpm@9.15.4\n- Builder: -\n- User Config: modules, devtools, app, css, runtimeConfig, future, compatibilityDate, telemetry, eslint\n- Runtime Modules: @nuxt/ui-pro@3.0.0, @nuxt/eslint@1.0.1, @vueuse/nuxt@12.5.0, @nuxt/image@1.9.0\n- Build Modules: -\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\nv3\n\n### Reproduction\n\nsee below\n\n### Description\n\nI get the follwing error:\n\n```\nruntime-core.esm-bundler.js:51 [Vue warn]: injection \"Symbol(nuxt-ui.locale-context)\" not found. \n at \u003CUSlideover open=false onUpdate:open=fn side=\"left\" ... > \n at \u003CUDashboardSidebar collapsible=\"\" resizable=\"\" > \n at \u003CPrimitive as=undefined class=\"fixed inset-0 flex overflow-hidden\" > \n at \u003CUDashboardGroup> \n at \u003CDefault ref=Ref\u003C undefined > > \n at \u003CAsyncComponentWrapper ref=Ref\u003C undefined > > \n at \u003CLayoutLoader key=\"default\" layoutProps= Object name=\"default\" > \n at \u003CNuxtLayoutProvider layoutProps= Object key=\"default\" name=\"default\" ... > \n at \u003CNuxtLayout> \n at \u003CApp key=4 > \n at \u003CNuxtRoot>\n```\n\nwhen usinng the DashboardSidebar component:\n```\n \u003CUDashboardSidebar\n collapsible\n resizable\n >\n \u003Ctemplate #header>\n \u003Cdiv class=\"flex items-center gap-2\">\n \u003CUIcon\n name=\"i-solar-buildings-2-bold\"\n class=\"w-7 h-7\"\n />\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```",[2929,2932,2933],{"name":2930,"color":2931},"bug","d73a4a",{"name":2869,"color":2870},{"name":2934,"color":2935},"pro","5BD3CB",3549,"injection \"Symbol(nuxt-ui.locale-context)\" not found","2025-03-18T11:12:44Z","https://github.com/nuxt/ui/issues/3549",0.76248884,{"description":2942,"labels":2943,"number":2945,"owner":2872,"repository":2873,"state":2909,"title":2946,"updated_at":2947,"url":2948,"score":2949},"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'. ",[2944],{"name":2869,"color":2870},3687,"Allow specify portal destination for all portaled components","2025-04-21T15:42:56Z","https://github.com/nuxt/ui/issues/3687",0.7718717,{"description":2951,"labels":2952,"number":2955,"owner":2872,"repository":2956,"state":2909,"title":2957,"updated_at":2958,"url":2959,"score":2960},"https://nuxt.com/support/us",[2953],{"name":2930,"color":2954},"ff281a",1167,"nuxt.com","Sponsors page does not show any sponsors","2023-06-06T12:14:43Z","https://github.com/nuxt/nuxt.com/issues/1167",0.7762368,{"description":2962,"labels":2963,"number":2971,"owner":2872,"repository":2873,"state":2909,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### Description\n\nWhile most components support the theming props (globally via app.config and as local props) the UForm component doesn't. For consistency it'd be great if this could be added to the Form component too.\n\n### Additional context\n\n_No response_",[2964,2967,2968],{"name":2965,"color":2966},"enhancement","a2eeef",{"name":2869,"color":2870},{"name":2969,"color":2970},"triage","ffffff",3752,"Form Component: Support theming props","2025-04-10T19:55:39Z","https://github.com/nuxt/ui/issues/3752",0.7850588,{"description":2977,"labels":2978,"number":2981,"owner":2872,"repository":2873,"state":2909,"title":2982,"updated_at":2983,"url":2984,"score":2985},"### Environment\n\n- Operating System: Linux\n- Node Version: v23.4.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.1\n- Builder: -\n- User Config: compatibilityDate, devtools, modules, runtimeConfig, auth, pinia, fonts, css, ui, app\n- Runtime Modules: @nuxt/ui@3.0.0-alpha.12, @sidebase/nuxt-auth@0.10.0, @nuxt/fonts@0.10.3, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n\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\nhttps://github.com/StefanH-AT/NuxtUi3-Shortcut-Meta\n\n### Description\n\n[According to the docs](https://ui3.nuxt.dev/composables/define-shortcuts#usage), `meta` is supposed to be translated to `Ctrl`, but on Linux, the Linux Meta key, which is the same as the Windows key, is detected.\n\nI find the usage of the word \"meta\" confusing due to this double meaning. Meta is commonly used to refer to the Windows aka Super aka Meta key, but not as Control\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2979,2980],{"name":2930,"color":2931},{"name":2869,"color":2870},3220,"Meta keyboard shortcut maps to system meta (\"Windows\") key on linux instead of Ctrl","2025-03-08T12:22:25Z","https://github.com/nuxt/ui/issues/3220",0.7857428,["Reactive",2987],{},["Set"],["ShallowReactive",2990],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIf3cJ0uNhGaQdvD7xnQz83a-Ms7DBzgFWvHunlDJCb4":-1},"/nuxt/ui/3584"]