\n```\n\n\n### Description\n\nWhen using `UInputMenu`, each item can be assigned a custom class. However, after filtering, the class assignment seems to mismatch. For example, the \"Green\" item may be displayed in red color.\n\n### Additional context\n\n- Initial state (before filtering): \n\u003Cimg width=\"328\" height=\"243\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/f556d5b4-554e-4328-98f1-e3bb037504bf\" />\n\n- After filtering with \"r\": \n\u003Cimg width=\"338\" height=\"206\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/bbed6c9b-2eae-4c55-9d68-2991f64c26ca\" />\n\nIn the filtered state, the \"Green\" item is incorrectly displayed in red.\n\n### Logs\n\n```shell-script\n\n```",[3158,3161,3164],{"name":3159,"color":3160},"bug","d73a4a",{"name":3162,"color":3163},"v3","49DCB8",{"name":3165,"color":3166},"triage","ffffff",4752,"nuxt","ui","open","UInputMenu item class mismatch after filtering","2025-08-15T01:57:20Z","https://github.com/nuxt/ui/issues/4752",0.729195,{"description":3176,"labels":3177,"number":3184,"owner":3168,"repository":3168,"state":3185,"title":3186,"updated_at":3187,"url":3188,"score":3189},"### Version\n\n[v2.5.1](https://github.com/nuxt.js/releases/tag/v2.5.1)\n\n### Reproduction link\n\n[https://not-needed.com](https://not-needed.com)\n\n### Steps to reproduce\n\n```bash\n$ npx create-nuxt-app nuxt-app\n$ cd nuxt-app\n```\n\nModify `/pages/index.vue`.\n\n```vue\n\u003Ctemplate>\n \u003Csection class=\"container\">\n {{ name }}\n \u003C/section>\n\u003C/template>\n\n\u003Cscript>\nclass Sample {\n static NAME = 'Alice'\n}\n\nexport default {\n data() {\n return {\n name: Sample.NAME\n }\n }\n}\n\u003C/script>\n```\n\nStart Nuxt.js app\n\n```bash\n$ npm run dev\n```\n\n\n### What is expected ?\n\nStart the application and create the instance having data: `{name: 'Alice'}`.\n\n### What is actually happening?\n\nThrow an Error: SyntaxError Unexpected token export\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8946\">#c8946\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3178,3181],{"name":3179,"color":3180},"pending triage","E99695",{"name":3182,"color":3183},"2.x","d4c5f9",5400,"closed","class property does not work in v2.5.1","2023-01-22T15:33:04Z","https://github.com/nuxt/nuxt/issues/5400",0.68397486,{"labels":3191,"number":3198,"owner":3168,"repository":3168,"state":3185,"title":3199,"updated_at":3200,"url":3201,"score":3202},[3192,3195],{"name":3193,"color":3194},"enhancement","8DEF37",{"name":3196,"color":3197},"3.x","29bc7f",13485,"Nuxt link does not have a disable or custom prop","2023-01-19T16:58:01Z","https://github.com/nuxt/nuxt/issues/13485",0.6897823,{"description":3204,"labels":3205,"number":3212,"owner":3168,"repository":3169,"state":3185,"title":3213,"updated_at":3214,"url":3215,"score":3216},"### Environment\n\n\n```\n\"@nuxt/ui\": \"^3.1.3\",\n\"@nuxt/ui-pro\": \"^3.1.3\",\n\"nuxt\": \"^3.17.5\",\n```\n\n\n```\nui: {\n prefix: 'Custom',\n},\n```\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.17.5\n\n### Reproduction\n\nIf I simply switch out the `CustomHeader` to a basic `header` element and remove the `template` tags the nested CustomNavigationMenu works and I'm not getting unable to resolve component warnings.\n\n```\n\u003Cscript setup lang=\"ts\">\nimport type { NavigationMenuItem } from '@nuxt/ui'\n\ndefineProps\u003C{\n links: NavigationMenuItem[]\n}>()\n\u003C/script>\n\n\u003Ctemplate>\n \u003CCustomHeader>\n \u003Ctemplate #left>\n \u003CClientOnly>\n \u003CNuxtLink to=\"/\">\n \u003CBaseLogo />\n \u003C/NuxtLink>\n \u003C/ClientOnly>\n \u003C/template>\n\n \u003CCustomNavigationMenu :items=\"links\" variant=\"link\" />\n\n \u003Ctemplate #right>\n \u003CThemePicker />\n \u003C/template>\n\n \u003Ctemplate #body>\n \u003CCustomNavigationMenu\n orientation=\"vertical\"\n :items=\"links\"\n />\n \u003C/template>\n \u003C/CustomHeader>\n\u003C/template>\n```\n\nerrors:\n[Vue warn]: Failed to resolve component: UButton\nIf this is a native custom element, make sure to exclude it from component resolution via ...\n[Vue warn]: Failed to resolve component: UContainer\nIf this is a native custom element, make sure to exclude it from component resolution via ...\n[Vue warn]: Failed to resolve component: ULink\nIf this is a native custom element, make sure to exclude it from component resolution via ..\n\n### Description\n\nIf i'm setting a custom prefix in the `ui: {}` config object for the components the UHeader component is unable to resolve its nested components.\n\n### Additional context\n\nI think i've seen issues like this previously also posted, and maybe its some import that is missing.\n\n### Logs\n\n```shell-script\n\n```",[3206,3207,3208,3211],{"name":3159,"color":3160},{"name":3162,"color":3163},{"name":3209,"color":3210},"nuxt/ui-pro","00dc82",{"name":3165,"color":3166},4371,"custom prefix not working when set with UHeader","2025-06-18T09:09:47Z","https://github.com/nuxt/ui/issues/4371",0.7006548,{"labels":3218,"number":3219,"owner":3168,"repository":3168,"state":3185,"title":3220,"updated_at":3221,"url":3222,"score":3223},[],13212,"Cannot read properties of undefined (reading '_uid')","2023-01-19T16:48:28Z","https://github.com/nuxt/nuxt/issues/13212",0.71157837,{"labels":3225,"number":3228,"owner":3168,"repository":3168,"state":3185,"title":3220,"updated_at":3229,"url":3230,"score":3231},[3226,3227],{"name":3196,"color":3197},{"name":3179,"color":3180},13101,"2023-01-19T16:57:40Z","https://github.com/nuxt/nuxt/issues/13101",0.71446246,{"description":3233,"labels":3234,"number":3239,"owner":3168,"repository":3168,"state":3185,"title":3240,"updated_at":3241,"url":3242,"score":3243},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v21.1.0`\r\n- Nuxt Version: `3.10.2`\r\n- CLI Version: `3.10.1`\r\n- Nitro Version: `2.8.1`\r\n- Package Manager: `npm@10.2.0`\r\n- Builder: `-`\r\n- User Config: `ssr`, `target`, `experimental`, `app`, `vue`, `css`, `modules`, `storyblok`, `build`, `vite`, `nitro`, `hooks`, `routeRules`, `imports`, `runtimeConfig`, `devtools`\r\n- Runtime Modules: `@storyblok/nuxt@6.0.4`, `@pinia/nuxt@0.5.1`\r\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-prqbf9?file=app.vue\n\n### Describe the bug\n\nIf you use a `nuxt-link` with the `custom` and `external` prop and click on it, a console.error will occur complaing about the nuxt-link not having the external prop set to true, even though it is.\r\n\r\nThe navigation itself still works, its just a console.error that occurs before you leave the page.\r\n\r\nThe interesting part is that the `replace` prop is respected, but not `external`.\n\n### Additional context\n\nI think the issue is coming from this file:\r\nhttps://github.com/nuxt/nuxt/blob/9326b7a8bde1ae793ba046f7dacc4ebbe200b786/packages/nuxt/src/app/components/nuxt-link.ts#L357C15-L357C23\r\n\r\nThe replace prop is included here, but not external.\n\n### Logs\n\n_No response_",[3235,3236],{"name":3196,"color":3197},{"name":3237,"color":3238},"🔨 p3-minor","FBCA04",25866,"The `nuxt-link` component does not respect the external prop","2024-02-21T21:20:15Z","https://github.com/nuxt/nuxt/issues/25866",0.71627516,{"labels":3245,"number":3250,"owner":3168,"repository":3168,"state":3185,"title":3251,"updated_at":3252,"url":3253,"score":3254},[3246,3248,3249],{"name":3247,"color":3166},"stale",{"name":3179,"color":3180},{"name":3182,"color":3183},9973,"Minor bug: CSS with pseudo class with params when staticly generated is different from development","2023-01-22T15:45:05Z","https://github.com/nuxt/nuxt/issues/9973",0.718054,{"description":3256,"labels":3257,"number":3260,"owner":3168,"repository":3169,"state":3185,"title":3261,"updated_at":3262,"url":3263,"score":3264},"### Environment\n\n- Operating System: Windows_NT\n- Node Version: v22.11.0\n- Nuxt Version: 3.14.0\n- CLI Version: 3.17.2\n- Nitro Version: 2.10.4\n- Package Manager: npm@10.9.0\n- Builder: -\n- User Config: default\n- Runtime Modules: @nuxt/icon@1.10.3, @nuxt/content@2.13.4, @nuxt/ui@2.20.0, @dargmuesli/nuxt-cookie-control@8.4.20, @pinia/nuxt@0.9.0\n- Build Modules: -\n\n### Version\n\nv2.20.0\n\n### Reproduction\n\nhttps://stackblitz.com/edit/nuxt-ui-dbszxsce?file=app.vue\n\n### Description\n\nWhen I ran chrome lighthouse, the results showed that the breadcrumb section was detected as not complying with the recommendation.\n\nI'm using `icon` only without label with defined `to` at first of Links array, to make it more descriptive as lighthouse said, i pass `'aria-label'` property and its value to object of `Links`, at first i thought it would work because as the documentation said about Breadcrumb:\n\n> You can also pass any property from the [NuxtLink](https://nuxt.com/docs/api/components/nuxt-link#props) component such as to, exact, etc. \n> Reference: https://ui.nuxt.com/components/breadcrumb#usage\n\nwell the attrbute is not rendered, but if i pass `ariaLabel` property, the attribute is rendered correctly (with `-` symbol) **Without reloading or HMR triggered,** , and if the page refreshed, it's broken (`-` symbol missing) \n\nNote: i always apply it to every NuxtLink though, aria-label is working as expected\n\nIs there any such way to apply aria-label without `'label'` on object of the links?\n\n### Additional context\n\nattribute rendered as expected (HMR trigger)\n\n\ndash symbol is missing after page reload\n",[3258,3259],{"name":3159,"color":3160},{"name":3165,"color":3166},3007,"UBreadcrumb wont render aria attribute","2025-03-24T17:55:54Z","https://github.com/nuxt/ui/issues/3007",0.71920943,{"description":3266,"labels":3267,"number":3273,"owner":3168,"repository":3168,"state":3185,"title":3274,"updated_at":3275,"url":3276,"score":3277},"### Environment\r\n\r\n------------------------------\r\n- Operating System: Linux\r\n- Node Version: v16.14.2\r\n- Nuxt Version: 3.6.5\r\n- Nitro Version: 2.5.2\r\n- Package Manager: yarn@3.2.0\r\n- Builder: vite\r\n- User Config: alias, app, components, css, devtools, experimental, extends, i18n, modules, nitro, pinia, router, runtimeConfig, tailwindcss, telemetry, veeValidate, vite, vue\r\n- Runtime Modules: @pinia/nuxt@^0.4.11, @nuxtjs/stylelint-module@^5.1.0, @nuxtjs/i18n@8.0.0-beta.13, @vueuse/nuxt@10.2.1, @vee-validate/nuxt@^4.9.6, @nuxtjs/tailwindcss@^6.8.0\r\n- Build Modules: -\r\n------------------------------\r\n\r\n### Reproduction\r\nI provide a minimal reproduction\r\n\r\nhttps://stackblitz.com/edit/github-brcyvh?file=pages%2Findex.vue\r\n\r\n### Describe the bug\r\n\r\nI'm using a plugin `$bp` that use `useBreakpoints` from `vueuse` under the hood https://vueuse.org/core/useBreakpoints\r\n\r\nMy goal is to change the `size` of the component `NButton` based on a boolean : `$bp.isLapM`.\r\n\r\nWhen we refresh the page, we see that the `btnSize` inside the button is updated but the class still `-sm`.\r\nIf I resize my window, both are updated\r\n\r\nWe are migrating our app to Nuxt 3, and on Nuxt 2 we didn't have this issue... :cry: \r\n\r\nI'm a doing something wrong about this ? \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_",[3268,3269,3270],{"name":3196,"color":3197},{"name":3179,"color":3180},{"name":3271,"color":3272},"upstream","E8A36D",22722,"class / style attribute does not update on node mismatch","2023-08-23T10:38:59Z","https://github.com/nuxt/nuxt/issues/22722",0.72177833,["Reactive",3279],{},["Set"],["ShallowReactive",3282],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkyufRQJpCzpYFIcJiGAXCzvW92zu6j1AFvKPe_xFNlE":-1},"/nuxt/ui/2306"]