\n\n\u003C!-- Or more granular control -->\n\u003CMDC \n :value=\"content\"\n :ui=\"{\n prose: {\n h1: { leading: 'hidden', leadingIcon: 'hidden' },\n h2: { leading: 'hidden', leadingIcon: 'hidden' }\n }\n }\"\n/>\n```\n\n## Use Case\n\n**Displaying AI/LLM generated content** where anchor links are undesirable:\n- Game interfaces showing AI-generated text\n- Chat applications with LLM responses \n- Content previews or excerpts\n- Educational tools displaying sample outputs\n\nIn these scenarios, anchor links serve no purpose and can be distracting or break the user experience.\n\n## Expected Behavior\n\n- Component-level `:ui` prop should merge with global prose configuration\n- Should work consistently with both `@nuxt/content` and standalone MDC usage\n- Should not require global configuration changes for per-component customization\n\n## Current Versions\n\n- `@nuxt/ui-pro` (v3)\n- 'uiPro.mdc' set to true or false in `nuxt.config` does not make a difference\n\n## Additional Context\n\nThis would align with Nuxt UI's existing pattern of allowing component-level customization via `:ui` props, providing developers with fine-grained control while maintaining sensible defaults.\n\n### Additional context\n\n_No response_",[3039,3040,3041],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4216,"Allow disabling anchor links per MDC component instance via :ui prop","2025-05-24T15:32:22Z","https://github.com/nuxt/ui/issues/4216",0.79297173,{"description":3048,"labels":3049,"number":3053,"owner":3029,"repository":3029,"state":3031,"title":3054,"updated_at":3055,"url":3056,"score":3057},"### Environment\n\nBrowser\nChrome 137\n\n### Reproduction\n\nGo here\nhttps://nuxt.com/docs/guide/directory-structure/components\n\nGo to Version 4\n(https://nuxt.com/docs/guide/directory-structure/app/components)\n\nGo back to Version 3\nhttps://nuxt.com/docs/guide/directory-structure/app/components will stay and not change back to version 3 url\n\n404 happens\n\n### Describe the bug\n\nA version selection which updates the URL will not update back to orignal URL and leads to 404\n\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n```shell-script\n\n```",[3050],{"name":3051,"color":3052},"pending triage","E99695",32484,"Docs: Version selection breaks url on navigation back","2025-06-26T15:02:24Z","https://github.com/nuxt/nuxt/issues/32484",0.80014235,{"description":3059,"labels":3060,"number":3069,"owner":3029,"repository":3029,"state":3031,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### Describe the feature\r\n\r\nFor many types of websites reactivity on useAppConfig is redundant due to a reason that website UI doesn't allow user to affect project configuration. Change to config usually happens at build time or SSR after page is fully refreshed or on, for example, router change (which doesn't require reactivity because whole page/layout is remounted). At the same time configuration object can become very big and we already see substantial memory leaks in some cases of using useAppConfig in certain scenarios. We workaround this with stringifying the object from the composable, but ideally no reactivity should be present as an option on Nuxt config itself. \r\n\r\n### Additional information\r\n\r\n- [X] 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).",[3061,3063,3066],{"name":3020,"color":3062},"8DEF37",{"name":3064,"color":3065},"discussion","538de2",{"name":3067,"color":3068},"performance","E84B77",24588,"[Feature Request] Provide an option to opt-out from reactivity on useAppConfig() composable","2024-06-30T11:06:41Z","https://github.com/nuxt/nuxt/issues/24588",0.8046628,{"description":3075,"labels":3076,"number":3080,"owner":3029,"repository":3030,"state":3081,"title":3082,"updated_at":3083,"url":3084,"score":3085},"### Description\n\nI'm trying to use Nuxt UI in a project that doesn't use Vue Router nor Inertia (for the record, it uses https://hybridly.dev/, but I don't want a `Link` component integration at all).\n\nWhen not using the `inertia` parameter, the following error occurs in the browsers' console:\n\n```\nUncaught SyntaxError: The requested module 'http://[::1]:5173/@id/__vite-optional-peer-dep:vue-router:@nuxt/ui' doesn't provide an export named: 'useRoute'\n```\n\n\n\nWhen setting `inertia` to `true`, I have the following one:\n\n```\nUncaught SyntaxError: The requested module 'http://[::1]:5173/@id/__vite-optional-peer-dep:@inertiajs/vue3:@nuxt/ui' doesn't provide an export named: 'usePage'\n```\n\n\n\nBoth of these seem to be due to Nuxt UI expecting either `vue-router` or `inertia-vue3` to be installed, which I don't want.\n\nIt would be nice if Nuxt UI supported a routerless option.\n\n### Additional context\n\n_No response_",[3077,3078,3079],{"name":3020,"color":3021},{"name":3023,"color":3024},{"name":3026,"color":3027},4341,"closed","Opt-out of router integrations","2025-06-16T09:46:25Z","https://github.com/nuxt/ui/issues/4341",0.70968735,{"description":3087,"labels":3088,"number":3096,"owner":3029,"repository":3030,"state":3081,"title":3097,"updated_at":3098,"url":3099,"score":3100},"### Environment\n\n------------------------------\n- Operating System: Darwin\n- Node Version: v22.14.0\n- Nuxt Version: -\n- CLI Version: 3.25.0\n- Nitro Version: -\n- Package Manager: pnpm@9.15.0\n- Builder: -\n- User Config: -\n- Runtime Modules: -\n- Build Modules: -\n------------------------------\n\n### Is this bug related to Nuxt or Vue?\n\nVue\n\n### Version\n\n3.1.0\n\n### Reproduction\n\nNA\n\n### Description\n\nI’m using Vue 3 with Inertia. I upgraded to v3.1 and now it behaves strangely: components—like a dropdown menu inside a button group—redirect instead of honoring the onSelect and performing the intended actions. In my case, I want to update a ref when clicking a dropdown item and open a drawer containing a form.\n\n### Additional context\n\nLaravel 12 with vue 3 and nuxtui 3.1 \n\n### Logs\n\n```shell-script\n\n```",[3089,3092,3093],{"name":3090,"color":3091},"bug","d73a4a",{"name":3023,"color":3024},{"name":3094,"color":3095},"inertia","6b46c1",3974,"Inertia: onSelect in dropdown items stop working","2025-05-13T12:45:19Z","https://github.com/nuxt/ui/issues/3974",0.7556614,{"labels":3102,"number":3107,"owner":3029,"repository":3029,"state":3081,"title":3108,"updated_at":3109,"url":3110,"score":3111},[3103,3104],{"name":3020,"color":3062},{"name":3105,"color":3106},"2.x","d4c5f9",8391,"feat: enable opting-in to breaking changes","2023-01-22T15:52:44Z","https://github.com/nuxt/nuxt/issues/8391",0.76252913,{"description":3113,"labels":3114,"number":3117,"owner":3029,"repository":3029,"state":3081,"title":3118,"updated_at":3119,"url":3120,"score":3121},"### What problem does this feature solve?\r\n\r\nCurrently the navigation behavior with Nuxt is the following:\r\n\r\n1. User clicks on a link\r\n2. Loading of new page starts\r\n3. User waits for new page load to complete\r\n4. Route updates\r\n5. Exit transition of current view plays\r\n6. Enter transition of new view plays\r\n7. Navigation is complete\r\n\r\nThis is not ideal UX-wise. Even when I make efforts to make my page quite fast and enable the loading indicator, the load times are inconsistent, and the page feels broken and frozen upon clicking a link as a result.\r\n\r\n\r\n### What does the proposed changes look like?\r\n\r\nI think a better behavior would be the following:\r\n\r\n1. User clicks on a link\r\n2. Route updates\r\n3. Loading of new page starts\r\n4. Exit transition of current view plays\r\n5. User waits for new page load to complete\r\n6. Enter transition of new view plays\r\n7. Navigation is complete\r\n\r\nThis way, we mitigate the problems significantly by taking advantage of two common patterns: offering immediate feedback after user interaction, and using exit transition duration to hide part of the loading time.\r\n\r\nI don't think there's need to take away the current behavior, but to rather a new alternative as an option, and also consider using it as a default. I'm sure I'm not the first one thinking of this but could still find no issues or discussion around it. Also whether the route visibly updating immediately or during the transition phase... probably not that big a deal, but immediate feedback is good.\r\n\r\nI'm not really up-to-date on all the tech behind the navigation logic, but I think this could drastically improve the perceived performance of Nuxt sites, hiding most of the page loads behind transitions.\r\n\r\n**EDIT:** \r\n\r\nA couple more points to clarify:\r\n\r\n- I'm not proposing any changes to the loading bar - at least nothing comes to mind that would need it.\r\n- I could already move loading logic from `asyncData` to other lifecycle hooks, in which case I get detailed control over my loading and wait time behavior. But I of course rely on `asyncData` for a reason, which is I want my prerendered pages to have the content available.\r\n- I'm **not** proposing rendering the new page without asyncData completing first. I'm proposing removing current page without delay, and waiting for the new page to load after that, if loading still takes time.\r\n\r\nOf course it would be awesome to have even more controls over how long loading times are handled between transitions, or even rendering (some) pages before asyncData completes in SPA mode only (i.e. allowing devs to write custom loading behavior while still staying server-render-friendly).\r\n\r\n\u003C!--cmty-->\r\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://cmty.app/nuxt\">Nuxt\u003C/a> community (\u003Ca href=\"https://cmty.app/nuxt/nuxt.js/issues/c8620\">#c8620\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3115,3116],{"name":3020,"color":3062},{"name":3105,"color":3106},4978,"When moving to a new route, transition current view out without delay","2024-06-14T16:10:17Z","https://github.com/nuxt/nuxt/issues/4978",0.7871419,{"description":3123,"labels":3124,"number":3129,"owner":3029,"repository":3029,"state":3081,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Describe the feature\n\nFor example we have file tree like this\r\ncomponents/\r\n - menu.vue\r\npage/\r\n type/\r\n - [type].vue\r\nlayouts/\r\n - type.vue\r\n\r\nwe have a menu component that placed in layout and contain NuxtLink to page/type/[type] page with other parameter value. menu component has a onMounted hook and when we navigate through links evety time onMounted will fired. Page not change, layout not change. how can we freeze a menu component and layout when navigate like this?\r\n\r\nminimal example here\r\nhttps://stackblitz.com/edit/github-gypnfa?file=layouts%2Ftype.vue\r\n \n\n### Additional information\n\n- [X] Would you be willing to help implement this feature?\n- [ ] Could this feature be implemented as a module?\n\n### Final checks\n\n- [X] Read the [contribution guide](https://nuxt.com/docs/community/contribution).\n- [X] Check existing [discussions](https://github.com/nuxt/nuxt/discussions) and [issues](https://github.com/nuxt/nuxt/issues).",[3125,3128],{"name":3126,"color":3127},"3.x","29bc7f",{"name":3051,"color":3052},21565,"Caching or freezing component in layout when use routing","2023-06-14T10:46:08Z","https://github.com/nuxt/nuxt/issues/21565",0.7904756,{"description":3135,"labels":3136,"number":3144,"owner":3029,"repository":3029,"state":3081,"title":3145,"updated_at":3146,"url":3147,"score":3148},"### Environment\n\n------------------------------\r\n- Operating System: Windows_NT\r\n- Node Version: v20.13.1\r\n- Nuxt Version: 3.12.2\r\n- CLI Version: 3.12.0\r\n- Nitro Version: 2.9.6\r\n- Package Manager: npm@10.5.2\r\n- Builder: -\r\n- User Config: devtools\r\n- Runtime Modules: -\r\n- Build Modules: -\r\n------------------------------\n\n### Reproduction\n\nRepo: https://github.com/admg/nuxt_optional_route_issue\n\n### Describe the bug\n\nlayout `default.vue`:\r\n```\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003CNuxtLink to=\"/a\">Link to A\u003C/NuxtLink> \u003Cbr />\r\n \u003CNuxtLink to=\"/a/id\">Link to A + param\u003C/NuxtLink>\r\n \u003C/div>\r\n\r\n \u003Cdiv>\r\n \u003CNuxtLink to=\"/b\">Link to B\u003C/NuxtLink> \u003Cbr />\r\n \u003CNuxtLink to=\"/b/id\">Link to B + param\u003C/NuxtLink>\r\n \u003C/div>\r\n\r\n \u003Cdiv>\r\n \u003CNuxtPage />\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cstyle lang=\"css\">\r\n.router-link-active {\r\n background-color: yellow;\r\n}\r\n\u003C/style>\r\n```\r\n\r\nfolder structure:\r\n```\r\nlayouts\r\n - default.vue\r\npages\r\n - a\r\n - [[id]].vue\r\n - b\r\n - [id].vue\r\n - index.vue\r\n - a.vue\r\n - b.vue\r\n```\r\n\r\n`a.vue` and `b.vue` contains:\r\n```\r\n\u003Ctemplate>\r\n \u003CNuxtPage />\r\n\u003C/template>\r\n```\r\n\r\nWorks ok for required parameter `[id]` and not properly for optional parameter `[[id]]`.\r\nAdding `.router-link-active` class works ok for `Link to B` on `/b` route and children routes like `/b/id`.\r\nSame is not working properly for `Link to A` link. Class is added only for exact route for urls `/a` and `/a/id`\r\n\r\n\r\n\n\n### Additional context\n\n_No response_\n\n### Logs\n\n_No response_",[3137,3138,3141],{"name":3051,"color":3052},{"name":3139,"color":3140},"pages","00DFB5",{"name":3142,"color":3143},"upstream","E8A36D",27841,"Optional route parameter doesn't trigger active class for parent links","2025-02-10T21:37:03Z","https://github.com/nuxt/nuxt/issues/27841",0.79208225,["Reactive",3150],{},["Set"],["ShallowReactive",3153],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fqd84uWUBUFVKsR9KCaNCtfVZUSXI_ohOIDSMpeZJqUQ":-1},"/nuxt/ui/4236"]