\n \u003C/div>\n\u003C/template>\n```\n\n### Logs\n\n```shell-script\n\n```",[2898,2901],{"name":2899,"color":2900},"bug","d73a4a",{"name":2902,"color":2903},"v3","49DCB8",2755,"ui","Veritcal NavigationMenu - `defaultOpen` doesn't work","2024-11-26T10:29:27Z","https://github.com/nuxt/ui/issues/2755",0.71267986,{"description":2911,"labels":2912,"number":2916,"owner":2871,"repository":2905,"state":2873,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### Description\n\n### For what version of Nuxt UI are you asking this question?\nv2.20.0\n### Description\nHi, I am trying to dynamically update the theme config (appConfig.ui). It works, but I have a problem with updating the config defaults option, such as defaults.divider.\nIt always uses the [props value](https://github.com/nuxt/ui/blob/dev/src/runtime/components/navigation/Breadcrumb.vue#L64), so the updated value (from [useUI](https://github.com/nuxt/ui/blob/dev/src/runtime/components/navigation/Breadcrumb.vue#L76)) is ignored.\n\nIt seems to me it's not correct behavior because all other fields in appConfig.ui update.\n\nLet me know if this is the correct behavior.\nThank you!\n\nmaybe related\nhttps://github.com/nuxt/ui/issues/2828",[2913],{"name":2914,"color":2915},"question","d876e3",2944,"[Breadcrumb]: Dynamically update defaults.divider in appConfig","2025-03-28T17:37:41Z","https://github.com/nuxt/ui/issues/2944",0.7202919,{"labels":2922,"number":2925,"owner":2871,"repository":2871,"state":2873,"title":2926,"updated_at":2927,"url":2928,"score":2929},[2923,2924],{"name":2882,"color":2883},{"name":2885,"color":2886},12317,"[Docs] Bottom prev-next navigation is broken","2023-01-19T16:03:01Z","https://github.com/nuxt/nuxt/issues/12317",0.7496361,{"description":2931,"labels":2932,"number":2935,"owner":2871,"repository":2871,"state":2873,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Describe the feature\r\n\r\n> _I created this issue to highlight my discord [message](https://discord.com/channels/473401852243869706/473407466630152201/1119174763374452746) after reading this issue (because I think both will improve the search): #21930_\r\n\r\nCan we move example to bottom while searching because everytime I search & hit enter I realize I get navigated to sandbox example instead of actual docs.\r\n\r\n\r\n\r\n### Additional information\r\n\r\n- [ ] Would you be willing to help implement this feature?\r\n- [ ] Could this feature be implemented as a module?\r\n\r\n### Final checks\r\n\r\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\r\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[2933,2934],{"name":2882,"color":2883},{"name":2885,"color":2886},21932,"[Proposal] Move examples to bottom in docs search result","2023-10-19T13:23:42Z","https://github.com/nuxt/nuxt/issues/21932",0.75052595,{"description":2941,"labels":2942,"number":2944,"owner":2871,"repository":2871,"state":2873,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Environment\n\nGitHub source code\n\n### Reproduction\n\nVisit this URL: https://github.com/nuxt-modules/algolia/blob/main/docs/content/1.getting-started/1.quick-start.md\n\nYou will see the algolia api key is exposed there\n\n### Describe the bug\n\nSensitive information has been found in a github repo of nuxt js\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2943],{"name":2888,"color":2889},31019,"Alogolia API key exposed publicly","2025-02-18T08:32:57Z","https://github.com/nuxt/nuxt/issues/31019",0.7624429,{"description":2950,"labels":2951,"number":2953,"owner":2871,"repository":2871,"state":2873,"title":2954,"updated_at":2955,"url":2956,"score":2957},"### Environment\n\n- Operating System: `Darwin`\n- Node Version: `v23.6.0`\n- Nuxt Version: `3.15.4`\n- CLI Version: `3.21.1`\n- Nitro Version: `2.10.4`\n- Package Manager: `npm@11.1.0`\n- Builder: `-`\n- User Config: `devtools`, `app`, `routeRules`, `modules`, `runtimeConfig`, `css`, `build`, `ssr`, `spaLoadingTemplate`, `experimental`, `primevue`, `i18n`, `compatibilityDate`, `turnstile`\n- Runtime Modules: `@nuxtjs/tailwindcss@6.12.1`, `@pinia/nuxt@0.5.1`, `@primevue/nuxt-module@4.1.1`, `@nuxtjs/i18n@8.3.1`, `@nuxt/eslint@0.3.13`, `@nuxtjs/turnstile@0.9.10`, `@sentry/nuxt/module@8.55.0`\n- Build Modules: `-`\n\n### Reproduction\n\n[https://stackblitz.com/edit/github-iy4axfop?file=pages%2Fpage2.vue](https://stackblitz.com/edit/github-iy4axfop?file=pages%2Fpage2.vue)\n\n### Describe the bug\n\nWhen doing client-side navigation from one page to another and the second page (the page we are navigating to) is using the useRoute() hook in its setup method. The hook will still contain data from the previous page (path, params, ...). So for example when fetching data in the setup method with useAsyncData will cause issues as the path is not correct and will not contain desired data.\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[2952],{"name":2899,"color":2900},30977,"useRoute() is containing data from previous page when performing client-side navigation","2025-02-20T15:20:35Z","https://github.com/nuxt/nuxt/issues/30977",0.76361483,{"description":2959,"labels":2960,"number":2961,"owner":2871,"repository":2962,"state":2873,"title":2963,"updated_at":2964,"url":2965,"score":2966},"",[],995,"nuxt.com","Move `nuxt.com-next` to `dev` branch","2023-06-06T12:14:21Z","https://github.com/nuxt/nuxt.com/issues/995",0.7664414,{"description":2968,"labels":2969,"number":2961,"owner":2871,"repository":2872,"state":2873,"title":2970,"updated_at":2971,"url":2972,"score":2966},"If you run `yarn run test:e2e` in the [following reproduction](https://codesandbox.io/p/devbox/long-browser-tv43ny), you'll get this error\n```\n TypeError: Cannot read properties of undefined (reading 'options')\n\n at startServer (/project/workspace/node_modules/@nuxt/test-utils/dist/shared/test-utils.BHdilg2X.mjs:119:27)\n at Object.setup2 (/project/workspace/node_modules/@nuxt/test-utils/dist/shared/test-utils.B9x0-cXO.mjs:179:7)\n at Object.test$1.extend._nuxtHooks.scope (/project/workspace/node_modules/@nuxt/test-utils/dist/playwright.mjs:22:7)\n```\n\nThe `nuxt` config from the [use](https://codesandbox.io/p/devbox/long-browser-tv43ny?file=%2Fplaywright.config.ts%3A30%2C4-41%2C7) property is not accessible using the current path `ctx.nuxt.options`: https://github.com/nuxt/test-utils/blob/df8f6c862f1f8d77097733f13b00f236778c9b56/src/core/server.ts#L62 but works using `ctx.options.nuxtConfig` instead.\n\nIt used to work with `ctx.nuxt.options` but I recently upgraded to the latest @nuxt/test-utils and I started seing this. The reproduction testifies of this new issue that I have. Maybe I am misusing the `use:{nuxt:{}` option?\n\n\n\n",[],"Issue when accessing the nuxt test options from context in startServer function","2024-12-05T14:26:41Z","https://github.com/nuxt/test-utils/issues/995",["Reactive",2974],{},["Set"],["ShallowReactive",2977],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fT7pEwi4JprXKXvgjT0pg-X-1mJOk5OXbDT4KBM1ycn8":-1},"/nuxt/nuxt.com/987"]