\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```",[3048,3051,3054,3057],{"name":3049,"color":3050},"bug","d73a4a",{"name":3052,"color":3053},"v3","49DCB8",{"name":3055,"color":3056},"nuxt/ui-pro","00dc82",{"name":3058,"color":3059},"triage","ffffff",4371,"ui","custom prefix not working when set with UHeader","2025-06-18T09:09:47Z","https://github.com/nuxt/ui/issues/4371",0.7006548,{"labels":3067,"number":3068,"owner":3026,"repository":3026,"state":3027,"title":3069,"updated_at":3070,"url":3071,"score":3072},[],13212,"Cannot read properties of undefined (reading '_uid')","2023-01-19T16:48:28Z","https://github.com/nuxt/nuxt/issues/13212",0.71157837,{"labels":3074,"number":3077,"owner":3026,"repository":3026,"state":3027,"title":3069,"updated_at":3078,"url":3079,"score":3080},[3075,3076],{"name":3038,"color":3039},{"name":3020,"color":3021},13101,"2023-01-19T16:57:40Z","https://github.com/nuxt/nuxt/issues/13101",0.71446246,{"description":3082,"labels":3083,"number":3088,"owner":3026,"repository":3026,"state":3027,"title":3089,"updated_at":3090,"url":3091,"score":3092},"### 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_",[3084,3085],{"name":3038,"color":3039},{"name":3086,"color":3087},"🔨 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":3094,"number":3099,"owner":3026,"repository":3026,"state":3027,"title":3100,"updated_at":3101,"url":3102,"score":3103},[3095,3097,3098],{"name":3096,"color":3059},"stale",{"name":3020,"color":3021},{"name":3023,"color":3024},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":3105,"labels":3106,"number":3109,"owner":3026,"repository":3061,"state":3027,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### 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",[3107,3108],{"name":3049,"color":3050},{"name":3058,"color":3059},3007,"UBreadcrumb wont render aria attribute","2025-03-24T17:55:54Z","https://github.com/nuxt/ui/issues/3007",0.71920943,{"description":3115,"labels":3116,"number":3122,"owner":3026,"repository":3026,"state":3027,"title":3123,"updated_at":3124,"url":3125,"score":3126},"### 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_",[3117,3118,3119],{"name":3038,"color":3039},{"name":3020,"color":3021},{"name":3120,"color":3121},"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,{"description":3128,"labels":3129,"number":3131,"owner":3026,"repository":3026,"state":3027,"title":3132,"updated_at":3133,"url":3134,"score":3135},"### Environment\n\nWorking directory: /home/projects/github-nb19p87o nuxi 7:50:25 PM\nNuxt project info: nuxi 7:50:26 PM\n\n------------------------------\n- Operating System: Linux\n- Node Version: v20.19.1\n- Nuxt Version: 3.17.6\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.13\n- Package Manager: pnpm@8.15.6\n- Builder: -\n- User Config: compatibilityDate, devtools, future\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-nb19p87o?file=app%app.vue\n\n1. Run `pnpx nuxi typecheck`\n\n### Describe the bug\n\nVue allows for setting conditional classes by using object syntax. The property key being the class name and an expression evaluating to true or false decides if the class is applied. Our project uses SCSS to generate BEM-style classes using interpolation to create the class names. See the [docs](https://sass-lang.com/documentation/style-rules/#interpolation) for interpolation.\n\nOnce you set `future.compatibilityVersion: 4` in nuxt.config.ts, this starts to throw `error TS2464: A computed property name must be of type 'string', 'number', 'symbol', or 'any'.` for any class generated with those computed properties.\n\n### Additional context\n\nI assume this is because vuejs language tools recently added a compiler option for strict module checks. See the [related PR](https://github.com/vuejs/language-tools/pull/5164).\n\nSetting `vueCompilerOptions.strictCssModules: false` in tsconfig.json did not fix the issue.\n\n### Logs\n\n```shell-script\n\n```",[3130],{"name":3020,"color":3021},32552,"Nuxt 4 compatibility version breaks scss module styles","2025-07-07T19:40:45Z","https://github.com/nuxt/nuxt/issues/32552",0.7223721,["Reactive",3137],{},["Set"],["ShallowReactive",3140],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fkyufRQJpCzpYFIcJiGAXCzvW92zu6j1AFvKPe_xFNlE":-1},"/nuxt/ui/2306"]