\r\n\u003C/template>\r\n```\r\nAny help with this would be great! Thanks so much for all your hard work.\r\n\r\n### Additional context\r\n\r\n_No response_\r\n\r\n### Logs\r\n\r\n_No response_",[2909],{"name":2879,"color":2880},1690,"Cannot pass NuxtLink `replace` to Nav components","2025-05-14T14:22:12Z","https://github.com/nuxt/ui/issues/1690",0.7197965,{"description":2916,"labels":2917,"number":2919,"owner":2860,"repository":2860,"state":2889,"title":2920,"updated_at":2921,"url":2922,"score":2923},"### Environment\n\n```\r\n- Operating System: Linux\r\n- Node Version: v18.19.1\r\n- Nuxt Version: 3.12.3\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.7\r\n- Package Manager: bun@1.1.20\r\n- Builder: -\r\n- User Config: alias, app, components, css, devtools, hooks, i18n, imports, modules, pwa, runtimeConfig, shadcn, srcDir, ssr, supabase, tailwindcss, typescript, vite, vue, compatibilityDate\r\n- Runtime Modules: @pinia/nuxt@0.5.1, @vite-pwa/nuxt@0.9.1, @nuxtjs/i18n@8.3.1, @nuxtjs/supabase@1.2.2, @nuxtjs/tailwindcss@6.12.0, shadcn-nuxt@0.10.4\r\n- Build Modules: -\r\n```\n\n### Reproduction\n\nhttps://stackblitz.com/edit/github-pnptkr?file=app.vue\n\n### Describe the bug\n\nAfter upgrade to 3.12.3 navigation stops to work on pages that use navigation guards from Nuxt.\r\n\r\nBy default no return in `onBeforeRouteLeave` should work but after adding explicit `return true` below message is printed in the console. \r\n\r\n\r\nSo this makes it clear that as a workaround I need to add all parameters and call `next()` explicitly.\r\n\r\nI see in tsconfig that latest version has changed how `#vue-router` is imported:\r\n\r\n\r\nIt does not seem to be related from the issue perspective but maybe above finding might also help with solving other router issues, since warnings might not be shown in default usage:\r\nhttps://github.com/nuxt/nuxt/issues/28086\r\nhttps://github.com/nuxt/nuxt/issues/28122\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[2918],{"name":2857,"color":2858},28141,"Navigation guards like onBeforeRouteLeave might prevent all navigation after upgrade to 3.12.3","2024-07-13T17:01:34Z","https://github.com/nuxt/nuxt/issues/28141",0.72298294,{"description":2925,"labels":2926,"number":2934,"owner":2860,"repository":2888,"state":2889,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.13.1\n- Nuxt Version: 3.16.2\n- CLI Version: 3.24.1\n- Nitro Version: 2.11.8\n- Package Manager: pnpm@10.8.1\n- Builder: -\n- User Config: app, compatibilityDate, css, devtools, devServer, eslint, imports, modules, nitro, runtimeConfig, sourcemap, ssr, fonts, icon, ui, colorMode\n- Runtime Modules: @nuxt/eslint@1.3.0, @nuxt/ui@3.0.2, @vueuse/nuxt@13.0.0\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nNuxt\n\n### Version\n\n3.16.2\n\n### Reproduction\n\nhttps://codesandbox.io/p/devbox/amazing-cdn-vgydgy\n\n### Description\n\nI want to close `UContextMenu` programmatically by setting `v-model:open` to `false`, but it doesn’t close the menu as expected.\n\n## Reproduction:\n```\n\u003Ctemplate>\n \u003Cdiv class=\"flex flex-col items-center justify-center gap-4 h-screen\">\n \u003CUContextMenu v-model:open=\"contextMenuOpen\" :items=\"menuItems\">\n \u003Cdiv class=\"w-50 h-20 border-1 rounded flex items-center justify-center bg-slate-500\">Right Click Here\u003C/div>\n \u003C/UContextMenu>\n \u003Cdiv class=\"mt-5\">contextMenuOpen: {{contextMenuOpen}}\u003C/div>\n \u003C/div>\n\u003C/template>\n\n\u003Cscript lang=\"ts\" setup>\nconst contextMenuOpen = ref(false)\n\nconst menuItems = [[\n {\n label: 'Item1'\n },\n {\n label: 'Item2'\n }\n]]\n\nwatch(contextMenuOpen,(newValue)=>{\n if(newValue){\n setTimeout(()=>{\n contextMenuOpen.value = false\n }, 3000)\n }\n})\n\u003C/script>\n```\n\n## What happens\nAfter opening the context menu and waiting for 3 seconds, `contextMenuOpen` is set to `false`, but the menu remains open.\n\n## What I expected\nWhen `contextMenuOpen` becomes `false`, the context menu should close.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2927,2930,2931],{"name":2928,"color":2929},"enhancement","a2eeef",{"name":2882,"color":2883},{"name":2932,"color":2933},"reka-ui","56d799",4107,"Cannot close `UContextMenu` programmatically via `v-model:open` = false","2025-05-10T15:45:52Z","https://github.com/nuxt/ui/issues/4107",0.7237642,{"description":2940,"labels":2941,"number":2950,"owner":2860,"repository":2888,"state":2889,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Environment\n\nNuxt v3.1.0\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\nv3.1.0\n\n### Reproduction\n\nNot sure how to share out an intertia/laravel app.\n\n### Description\n\nI was able to move forward with the Intertia JS improvements with Links, however... I'm trying to use the Header component and the toggle isn't working. I can see in the header.vue component that useRoute is being used, and it' causing the app to not open and close the menu correctly.\n\nI can see it opening for a flash, then closed. I tried doing something manually with watching for the update:open, but I can see this is not the solution... I immediately had issues closing and losing the link focus trap when the menu appears.\n\nI'm using Nuxt UI Pro v3.1.0 - I'm about to purchase a liceense so I can confirm this works with SSR enabled, but I'm blocked with this basic implemention.\n\n```\n \u003CUApp>\n \u003CUHeader mode=\"drawer\">\n \u003Ctemplate #title>\n \u003CApplicationLogo class=\"h-6 w-auto\" />\n \u003C/template>\n\n \u003CUNavigationMenu :items=\"items\" />\n\n \u003Ctemplate #right>\n \u003CUColorModeSelect />\n \u003C/template>\n\n \u003Ctemplate #body>\n \u003CUNavigationMenu :items=\"items\" orientation=\"vertical\" class=\"-mx-2.5\" />\n \u003C/template>\n \u003C/UHeader>\n\u003C/UApp>\n```\n\nI can see this will be a problem with more components...\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2942,2943,2944,2947],{"name":2879,"color":2880},{"name":2882,"color":2883},{"name":2945,"color":2946},"@nuxt/ui-pro","5BD3CB",{"name":2948,"color":2949},"inertia","b60205",3990,"Header toogle menu not working in an Intertia app (useRoute still being used)","2025-05-04T15:36:46Z","https://github.com/nuxt/ui/issues/3990",0.7243587,{"description":2956,"labels":2957,"number":2963,"owner":2860,"repository":2888,"state":2889,"title":2964,"updated_at":2965,"url":2966,"score":2967},"### 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```",[2958,2959,2960],{"name":2879,"color":2880},{"name":2882,"color":2883},{"name":2961,"color":2962},"nuxt/ui-pro","00dc82",4177,"UNavigationMenu item children not visible when wrapped in UDashboardToolbar","2025-05-23T12:23:17Z","https://github.com/nuxt/ui/issues/4177",0.7248191,{"description":2969,"labels":2970,"number":2975,"owner":2860,"repository":2860,"state":2889,"title":2976,"updated_at":2977,"url":2978,"score":2979},"### 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_",[2971,2972],{"name":2898,"color":2899},{"name":2973,"color":2974},"🔨 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.72841495,["Reactive",2981],{},["Set"],["ShallowReactive",2984],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fxdLi9Yb8DRRPnlmmYrCPMiR8y8gk-fcHbEZxem8tcrc":-1},"/nuxt/ui/2098"]