\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```",[2917,2920,2923,2926],{"name":2918,"color":2919},"bug","d73a4a",{"name":2921,"color":2922},"v3","49DCB8",{"name":2924,"color":2925},"nuxt/ui-pro","00dc82",{"name":2927,"color":2928},"triage","ffffff",4371,"ui","closed","custom prefix not working when set with UHeader","2025-06-18T09:09:47Z","https://github.com/nuxt/ui/issues/4371",0.66943467,{"description":2937,"labels":2938,"number":2942,"owner":2908,"repository":2930,"state":2931,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### Environment\n\n- Operating System: Darwin\n- Node Version: v20.11.1\n- Nuxt Version: 3.16.2\n- CLI Version: 3.25.1\n- Nitro Version: 2.11.12\n- Package Manager: npm@10.2.4\n- Builder: -\n- User Config: css, compatibilityDate, devtools, future, modules, runtimeConfig, ssr, typescript\n- Runtime Modules: @nuxt/eslint@1.4.0, @nuxt/fonts@0.11.4, @nuxt/ui-pro@3.1.2, @pinia/nuxt@0.5.5, @vueuse/nuxt@10.11.1, nuxt-auth-utils@0.5.20, nuxt-authorization@0.3.4\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\nJust use the code of https://github.com/nuxt-ui-pro/dashboard/blob/main/app/pages/settings.vue and add a child to one of the links used for the UNavigationMenu. Like :\n````\n{\n label: \"General\",\n icon: \"i-lucide-user\",\n to: \"/settings\",\n children: [\n {\n label: \"Hello\",\n icon: \"i-lucide-book-open\",\n },\n ],\n exact: true,\n },\n````\n\n### Description\n\nIt seems wrapping the UNavigationMenu component in UDashboardToolbar will cause the UNavigationMenu's links children dropdown to not appear or be hidden.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2939,2940,2941],{"name":2918,"color":2919},{"name":2921,"color":2922},{"name":2924,"color":2925},4177,"UNavigationMenu item children not visible when wrapped in UDashboardToolbar","2025-05-23T12:23:17Z","https://github.com/nuxt/ui/issues/4177",0.68164265,{"description":2948,"labels":2949,"number":2954,"owner":2908,"repository":2908,"state":2931,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Environment\n\n- Operating System: Darwin\r\n- Node Version: v18.12.1\r\n- Nuxt Version: 3.4.3\r\n- Nitro Version: 2.3.3\r\n- Package Manager: pnpm@8.3.1\r\n- Builder: vite\n\n### Reproduction\n\nInside the `app.vue` file I have the following:\r\n\r\n```vue\r\n\u003Cscript setup lang=\"ts\">\r\nconst app = useNuxtApp();\r\n\r\nonMounted(() => {\r\n console.log('onMounted');\r\n});\r\n\r\napp.hook('page:finish', () => {\r\n console.log('page:finish');\r\n});\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"flex min-h-screen flex-col\">\r\n \u003CHtml lang=\"en\" />\r\n \u003CBody class=\"antialiased selection:bg-primary-100 selection:text-primary-600\" />\r\n\r\n \u003CNuxtPage class=\"flex-1\" />\r\n\r\n \u003Csection id=\"about\">Demo section\u003C/section>\r\n \u003C/div>\r\n\u003C/template>\r\n```\n\n### Describe the bug\n\nI'm trying to build a reveal animation when the page is loaded, so I usually create the animation timeline with GSAP inside the \"onMounted\" hook that starts paused and only plays once the page is fully loaded (the `page:finish` hook).\r\n\r\nEverything works perfectly fine if I navigate to any page of the Nuxt app and reload it, except for reloading in pages with a hash in the path AND an actual element with the hash as an id (for example: `http://localhost:8080/#about`). For some reason, if the route path contains a hash of an existing element in the DOM, the `page:finish` hook gets called before `onMounted`. However, if I remove the hash from the URL or there's no element present in the DOM that matches the hash, the order goes back to normal (`onMounted` first and `page:finish` second).\r\n\r\nI don't know why that happens.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2950,2953],{"name":2951,"color":2952},"3.x","29bc7f",{"name":2905,"color":2906},20617,"The `page:finish` hook gets called before `onMounted` only when hash present in path","2023-05-02T03:12:44Z","https://github.com/nuxt/nuxt/issues/20617",0.6955843,{"description":2960,"labels":2961,"number":2967,"owner":2908,"repository":2908,"state":2931,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Environment\n\n- Operating System: `Darwin`\r\n- Node Version: `v18.4.0`\r\n- Nuxt Version: `3.0.0`\r\n- Nitro Version: `1.0.0`\r\n- Package Manager: `yarn@1.22.19`\r\n- Builder: `vite`\r\n- User Config: `srcDir`, `app`, `modules`, `css`, `components`\r\n- Runtime Modules: `@nuxtjs/color-mode@3.2.0`, `@vueuse/nuxt@9.6.0`, `@nuxt/content@2.2.2`, `nuxt-icon@0.1.8`, `@nuxtjs/supabase@0.3.0`, `@pinia/nuxt@0.4.6`, `@pinia-plugin-persistedstate/nuxt@1.0.0`, `@nuxtjs/robots@3.0.0`, `nuxt-windicss@2.6.0`\r\n- Build Modules: `-`\n\n### Reproduction\n\n[https://github.com/arthurdanjou/artdanj-website-v2](https://github.com/arthurdanjou/artdanj-website-v2)\n\n### Describe the bug\n\nIn this [line](https://github.com/ArthurDanjou/artdanj-website-v2/blob/main/src/app/router.options.ts#L26) in the router config, the element is null so the router can't scroll to the element with the hash when I switch page, but it scroll well when I reload the page\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2962,2963,2964],{"name":2951,"color":2952},{"name":2905,"color":2906},{"name":2965,"color":2966},"needs reproduction","FBCA04",15669,"Scrolling to component with hash return error","2023-04-05T10:41:20Z","https://github.com/nuxt/nuxt/issues/15669",0.69742924,{"description":2973,"labels":2974,"number":2981,"owner":2908,"repository":2908,"state":2931,"title":2982,"updated_at":2983,"url":2984,"score":2985},"Hi,\r\nI'm facing a weird issue with a nuxt generated app and a plugin I'm creating.\r\n\r\n```html\r\n\u003Ctemplate>\r\n \u003Cdiv id=\"app\">\r\n \u003Ctop-nav/>\r\n \u003Cksvuefp :options=\"options\" :sections=\"sections\">\r\n \u003Cksvuefp-section\r\n v-for=\"(section,index) in sections\"\r\n :section=\"section\"\r\n :key=\"section\"\r\n :sectionIndex=\"index\"\r\n :background-color=\"section\"\r\n >\r\n \u003Ch2>{{ section }}\u003C/h2>\r\n \u003C/ksvuefp-section>\r\n \u003C/ksvuefp>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\nexport default {\r\n name: 'home',\r\n data () {\r\n return {\r\n sections: ['red', 'blue', 'green'],\r\n options: { }\r\n }\r\n }\r\n}\r\n\u003C/script>\r\n```\r\nWhen using nuxt dev no problem, everything is rendered correctly. But once generated, instead of having 3 sections mounted... I only have 2. The first one is missing. The weirdest is that on loading, this section seems to be mounted, but dieappears when the app is totally loaded...\r\n\r\nMy components code:\r\n\r\nksvuefp-section.vue\r\n```html\r\n\u003Ctemplate>\r\n \u003Ccomponent :is=\"options.animationType\" :options=\"options\" :appear=\"false\">\r\n \u003Ctagger :sectionIndex=\"sectionIndex\" :options=\"options\" class=\"ksvuefp-section\" :style=\"{ backgroundImage: backgroundImage || '', backgroundColor: backgroundColor || '' }\" v-show=\"sectionIndex === $ksvuefp.currentIndex\">\r\n \u003Cspan class=\"ksvuefp-section__overlay\" :style=\"{ background: options.overlay || 'rgba(0,0,0,0.2)' }\" v-if=\"options.overlay\">\u003C/span>\r\n \u003Cdiv class=\"ksvuefp-section__content\">\r\n \u003Cslot>\u003C/slot>\r\n \u003C/div>\r\n \u003C/tagger>\r\n \u003C/component>\r\n\u003C/template>\r\n\r\n\u003Cscript>\r\nimport { slideY, slideX, fade } from '../ksvuefp-animations'\r\nimport imagesLoaded from 'imagesloaded'\r\nexport default {\r\n components: {\r\n slideY,\r\n slideX,\r\n fade,\r\n 'tagger': {\r\n props: ['options', 'sectionIndex'],\r\n render (h) {\r\n return h(this.options.sectionTag || 'div', this.$slots.default)\r\n },\r\n mounted () {\r\n const vm = this\r\n vm.$nextTick(() => {\r\n imagesLoaded(vm.$el, { background: true }, () => {\r\n vm.$ksvuefp.$emit('ksvuefp-section-loaded', vm.sectionIndex)\r\n })\r\n }\r\n }\r\n },\r\n data () {\r\n return {\r\n options: this.$ksvuefp.options || [ ]\r\n }\r\n },\r\n props: ['section', 'backgroundImage', 'backgroundColor', 'sectionIndex']\r\n}\r\n\u003C/script>\r\n```\r\n\r\nAny idea of what could cause the issue? I'm banging my head on the wall since hours ahaha \n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This bug report is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c1622\">#c1622\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[2975,2978],{"name":2976,"color":2977},"available soon","6de8b0",{"name":2979,"color":2980},"2.x","d4c5f9",1807,"Nuxt generate: Missing first item in v-for loop","2023-01-18T15:54:46Z","https://github.com/nuxt/nuxt/issues/1807",0.69980395,{"description":2987,"labels":2988,"number":2992,"owner":2908,"repository":2930,"state":2931,"title":2993,"updated_at":2994,"url":2995,"score":2996},"### Environment\n\n- Nuxt 3.16.2 with Nitro 2.11.9\n- NuxtUI 3.1.1\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.1.1\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/quirky-wood-lnhsf5\n\n### Description\n\nWhen UNavigationMenu is vertical it's impossible to trigger navigation on root elements\neven if you specify `type: 'link', onselect: () => navigateTo('/test'), `\n\n### Additional context\n\nThe only workaround I have found is to do\n```\n\u003Ctemplate #item-label=\"{ item }\">\n \u003CNuxtLink :to=\"item.to\">{{ item.label }}\u003C/NuxtLink>\n\u003C/template>\n```",[2989,2990,2991],{"name":2918,"color":2919},{"name":2921,"color":2922},{"name":2927,"color":2928},4115,"UNavigationMenu vertical not triggering route \"to\" on root elements","2025-05-10T11:18:54Z","https://github.com/nuxt/ui/issues/4115",0.70101154,{"labels":2998,"number":3006,"owner":2908,"repository":2908,"state":2931,"title":3007,"updated_at":3008,"url":3009,"score":3010},[2999,3000,3003],{"name":2951,"color":2952},{"name":3001,"color":3002},"upstream","E8A36D",{"name":3004,"color":3005},"upstream-bug","B60205",12921,"Navigating away and back looses the styling of the root component element from its parent page (using style scoped and fragments)","2024-06-17T15:09:38Z","https://github.com/nuxt/nuxt/issues/12921",0.701285,{"description":3012,"labels":3013,"number":3015,"owner":2908,"repository":2908,"state":2931,"title":3016,"updated_at":3017,"url":3018,"score":3019},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v20.19.0`\n- Nuxt Version: `3.17.5`\n- CLI Version: `3.25.1`\n- Nitro Version: `2.11.12`\n- Package Manager: `npm@10.8.2`\n- Builder: `-`\n- User Config: `compatibilityDate`, `devtools`, `router`, `srcDir`, `dir`\n- Runtime Modules: `-`\n- Build Modules: `-`\n\n### Reproduction\n\nhttps://stackblitz.com/~/github.com/yuriystasiv/nuxt-link-hashtag\nhttps://github.com/yuriystasiv/nuxt-link-hashtag\n\n### Describe the bug\n\nAfter updating Nuxt from 3.11.2 to 13.17.5, I noticed that `scrollBehavior: 'smooth'` no longer works correctly when using `NuxtLink` with a hash (#). Navigation to the element still occurs, but instead of a smooth scroll, it jumps immediately to the target and only applies the smooth scroll animation at the very end, which feels abrupt.\n\nThis seems to be caused by NuxtLink now rendering a plain \u003Ca> tag instead of RouterLink. This change happened in [this PR](https://github.com/nuxt/nuxt/pull/30190). When I switch it back to use RouterLink (like in earlier versions), smooth scrolling works correctly again. Here’s a demo with patch:\nhttps://stackblitz.com/~/github.com/yuriystasiv/nuxt-link-hashtag-patch\nhttps://github.com/yuriystasiv/nuxt-link-hashtag-patch\n\n**Expected behavior**\nSmooth scrolling should work with NuxtLink and hash links, even when it’s rendered as an anchor tag.\n\n### Additional context\n\nIs there something that needs to be handled differently in NuxtLink to make smooth scrolling work as expected when using anchor tags?\n\nAs a workaround, you can prevent the default behavior and use navigateTo or router.push manually, like this:\n```\n\u003CNuxtLink\n to=\"#test\"\n @click.prevent=\"navigateToSection('#test')\"\n >example\n\u003C/NuxtLink>\n\u003Cscript setup lang=\"ts\">\nconst route = useRoute();\nconst navigateToSection = (section: string) => {\n navigateTo(`${route.path}${section}`);\n};\n\u003C/script>\n```\n\n### Logs\n\n```shell-script\n\n```",[3014],{"name":2905,"color":2906},32329,"NuxtLink hashtag and scrollBehavior smooth","2025-06-14T13:06:23Z","https://github.com/nuxt/nuxt/issues/32329",0.7014832,{"description":3021,"labels":3022,"number":3030,"owner":2908,"repository":2908,"state":2931,"title":3031,"updated_at":3032,"url":3033,"score":3034},"### Environment\r\n\r\nWorks in any environment, including StackBlitz:\r\n\r\n```\r\n- Operating System: Linux\r\n- Node Version: v16.20.0\r\n- Nuxt Version: 3.7.1\r\n- CLI Version: 3.7.3\r\n- Nitro Version: 2.6.2\r\n- Package Manager: npm@9.4.2\r\n- Builder: -\r\n- User Config: experimental\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n```\r\n\r\n### Reproduction\r\n\r\nPlease refer to:\r\n\r\nhttps://stackblitz.com/edit/github-ydxe3t?file=pages%2Findex.vue\r\n\r\n1. Do `nuxt generate` and `npx serve .output/public`.\r\n2. CLick the link 'Go to page with scoped styles'\r\n3. **Note the 404 in console on click to the link and absence of the component**\r\n4. Reload the page\r\n5. Note the component was loaded normally\r\n6. Remove scoped attribute from style tag in pageWithScopedStyles.vue and repeat the excercise\r\n\r\n\r\n### Describe the bug\r\n\r\nApparently because scoped styles in Vue are implemented using attributes and the server components are rendered based on attribute values, server components **in some instances** will break (the client will request a non-existing URL of `__nuxt_island/whatever_id`, leading to a 404. This will lead to the component not being displayed. \r\n\r\nThe sufficient conditions for the reproduction are following: \r\n- There is a server component used on two separate pages\r\n- It's not used directly, but through a third component (I used a wrapper) which uses this component as root\r\n- It has a prop that is different on these pages (I injected the route, I suppose it's also possible that a state variable may be passed as a prop\r\n\r\nThis is not reproduced in dev, only if the site is statically generated using `nuxt generate` and the client navigates to the page which uses scoped styles using soft navigation, e.g. `\u003CNuxtLink />`\r\n\r\nI'm not certain what causes the bug.\r\n\r\n### Additional context\r\n\r\nI know this might sound like an edge case but I arrived to this bug in a real-world scenario and I imagine this could be an issue for example for component library creators who want to use .server components (llike myself). An easy enough workaround is to avoid using it as a root in the wrapper but I'm sure there are also other unforeseen scenarios that might trigger this problem.\r\n\r\nThe fact is, it works OK in dev, but breaks during SSG.\r\n\r\n### Logs\r\n\r\n_No response_",[3023,3024,3025,3027],{"name":2951,"color":2952},{"name":2918,"color":2919},{"name":3026,"color":2966},"🔨 p3-minor",{"name":3028,"color":3029},"server components","839413",23051,"Nuxt3 .server (island) components fail to render on soft navigation if they have different props on pages","2023-09-10T08:06:13Z","https://github.com/nuxt/nuxt/issues/23051",0.7014927,["Reactive",3036],{},["Set"],["ShallowReactive",3039],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$ft_6DbQSq0U_IX4SVNqDFPZea11sgglUd6OQuG783Hds":-1},"/nuxt/ui/4416"]