\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_",[3152,3155,3158],{"name":3153,"color":3154},"enhancement","a2eeef",{"name":3156,"color":3157},"v3","49DCB8",{"name":3159,"color":3160},"triage","ffffff",4216,"ui","Allow disabling anchor links per MDC component instance via :ui prop","2025-05-24T15:32:22Z","https://github.com/nuxt/ui/issues/4216",0.7182897,{"description":3168,"labels":3169,"number":3175,"owner":3143,"repository":3143,"state":3144,"title":3176,"updated_at":3177,"url":3178,"score":3179},"### Problem\n\nNuxt 3.15 out of the box can transform `\u003CNuxtLink>` and inline urls starting with `/` into absolute urls that include app's `baseURL`.\n\n```\n// In SFC Template\n\u003Cimg src=\"/images/foo.png\" />\n\n// In dev and production when baseURL = '/subfolder/'\n\u003Cimg src=\"/subfolder/images/foo.png />\n```\n\nThe automatic transformation is not applied when using variables in template.\n\n```\nconst imgSrc = '/images/foo.png';\n\n// In SFC Template\n\u003Cimg :src=\"imgSrc\" />\n\n// In dev and production when baseURL = '/subfolder/'\n\u003Cimg src=\"/images/foo.png />\n// No transformation applied!\n``` \n\n### Workaround\n\nOne way to handle it is to manually retrieve `baseURL` from runtime config and add it to url:\n\n```\nconst runtimeConfig = useRuntimeConfig();\nconst imgSrc = runtimeConfig.app.baseURL + 'images/foo.png';\n\n\u003Cimg :src=\"imgSrc\" />\n```\n\n### Solution\n\nTo improve DX I think Nuxt should provide a composable `useMaybeAbsolutePath`, which returns a function that automatically adds `baseURL` to all paths that start with `/` and does not touch any other paths:\n\n```ts\nexport default useMaybeAbsolutePath()\n{\n const runtimeConfig = useRuntimeConfig();\n return (path: string) => {\n if (path.startsWith('/')) return runtimeConfig.app.baseURL + path.substring(1);\n else return path; // Do not edit relative paths and external links\n }\n}\n```\n\nUsage:\n\n```vue\n\u003Cscript lang=\"ts\" setup>\nconst maybeAbsolutePath = useMaybeAbsolutePath();\nconst imgSrc = '/images/foo.png';\n\u003C/script>\n\n\u003Ctemplate>\n \u003Cimg :src=\"maybeAbsolutePath(imgSrc)\" />\n\u003C/template>\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).",[3170,3172],{"name":3153,"color":3171},"8DEF37",{"name":3173,"color":3174},"discussion","538de2",30850,"`useMaybeAbsolutePath` for triggering automatic `baseURL` treatment","2025-02-12T10:28:59Z","https://github.com/nuxt/nuxt/issues/30850",0.7346967,{"description":3181,"labels":3182,"number":3194,"owner":3143,"repository":3162,"state":3144,"title":3195,"updated_at":3196,"url":3197,"score":3198},"### Description\n\nIt should be possible to opt out partially from the Inertia `Link` for e.g. menu items. Inertia links require routing to valid Inertia pages, otherwise they will open the page in a modal iframe.\n\n### Additional context\n\nWe have a large legacy project that cannot be fully migrated to Inertia yet. Some pages are just blades. ",[3183,3184,3185,3186,3189,3192],{"name":3153,"color":3154},{"name":3156,"color":3157},{"name":3159,"color":3160},{"name":3187,"color":3188},"closed-by-bot","ededed",{"name":3190,"color":3191},"inertia","6b46c1",{"name":3193,"color":3188},"stale",4236,"Inertia Link: Partial opt-out for Navigation components","2025-08-20T08:52:48Z","https://github.com/nuxt/ui/issues/4236",0.736063,{"labels":3200,"number":3206,"owner":3143,"repository":3143,"state":3207,"title":3208,"updated_at":3209,"url":3210,"score":3211},[3201,3202,3203],{"name":3193,"color":3160},{"name":3140,"color":3141},{"name":3204,"color":3205},"2.x","d4c5f9",7541,"closed","Is there the standard, recommended way to make anchor links work properly?","2023-01-22T15:36:01Z","https://github.com/nuxt/nuxt/issues/7541",0.7055289,{"description":3213,"labels":3214,"number":3218,"owner":3143,"repository":3162,"state":3207,"title":3219,"updated_at":3220,"url":3221,"score":3222},"### 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_",[3215,3216,3217],{"name":3153,"color":3154},{"name":3156,"color":3157},{"name":3159,"color":3160},4341,"Opt-out of router integrations","2025-06-16T09:46:25Z","https://github.com/nuxt/ui/issues/4341",0.7116396,{"description":3224,"labels":3225,"number":3228,"owner":3143,"repository":3143,"state":3207,"title":3229,"updated_at":3230,"url":3231,"score":3232},"Feature request: Allow redirects to absolute URLs, SSR and client-side.\r\n\r\nWe have an app (https://domainr.com) with several legacy URLs, some of which redirect to other websites. We’re exploring using Nuxt/Vue for our new website and would like to preserve this behavior.\r\n\r\n## Snippet to reproduce\r\n\r\n`~/pages/_domain/iana.vue`\r\n\r\n```javascript\r\n\u003Cscript>\r\nexport default {\r\n fetch ({ params, redirect }) {\r\n redirect(301, `https://www.iana.org/domains/root/db/${params.domain}.html`)\r\n }\r\n}\r\n\u003C/script>\r\n```\r\n\r\n## Steps to reproduce\r\n\r\nNavigate to `/com/iana`\r\n\r\n## Expected\r\n\r\nRedirect to `https://www.iana.org/domains/root/db/com.html`\r\n\r\n(Click here to see expected behavior: https://domainr.com/com/iana)\r\n\r\n## What actually happens\r\n\r\nRedirect to `/https:/www.iana.org/domains/root/db/com.html` (local URL)\r\n\r\n## Background\r\n\r\nNuxt only allows local redirects to a path, which is prepended with `router.base` here: https://github.com/nuxt/nuxt.js/blob/dev/lib/app/server.js#L39\r\n\n\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\n\u003Cdiv align=\"right\">\u003Csub>\u003Cem>This feature request is available on \u003Ca href=\"https://nuxtjs.cmty.io\">Nuxt.js\u003C/a> community (\u003Ca href=\"https://nuxtjs.cmty.io/nuxt/nuxt.js/issues/c661\">#c661\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3226,3227],{"name":3153,"color":3171},{"name":3204,"color":3205},770,"Allow redirect to absolute URL","2023-01-18T15:39:46Z","https://github.com/nuxt/nuxt/issues/770",0.7145896,{"description":3234,"labels":3235,"number":3243,"owner":3143,"repository":3143,"state":3207,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### Environment\n\nHello everybody, and first of all, thanks to all the team for your incredible job!\n\nHere is the context:\nI have a Nuxt app hosted on a **root domain**.\nSome parts of the app are also accessible via **subdomains** (or even different domains).\n\nTo make assets and API calls work properly across all domains, I’ve set:\n\n`.env`\n```env\nBASE_URL=\"http://labaxxxxxxxxx.fr\"\n```\n\n`nuxt.config.ts`\n```ts\n{\n//...\n app: {\n cdnURL: process.env.BASE_URL\n },\n runtimeConfig: {\n public: {\n baseURL: process.env.BASE_URL,\n }\n },\n experimental: {\n componentIslands: 'local+remote'\n }\n//...\n}\n```\n`components/Markdown.server.vue`\n```vue\n\u003CMarkdown :source=\"config.public.baseURL\" />\n```\n\n\n### Describe the bug\n\n\nEverything works as expected on the **root domain** and even from **subdomains** for assets and API calls.\n\nHowever, server components break when accessed from **subdomains** because their requests seem to be **relative**, not **absolute**.\n\n✅ If the page is open from my **root domain**, everything works as excepted.\n```\nhttps://labaxxxxxxxxx.fr\n``` \n\nBut if I the page is open from a subdomain:\n\n```\nhttps://labrasive.labaxxxxxxxxx.fr\n``` \n\n✅ The `assets` or `api` calls correctly targets the **root domain**, like this `/band`: \n\n\u003Cimg width=\"419\" height=\"85\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/2d43dd7a-edd4-4ad0-8d8e-74fa33d72efd\" /> \n\u003Cbr>\u003Cbr>\n\n❌ But the `Markdown.server.vue` component call is broken because it doesn't target the **root domain**... \n\n\u003Cimg width=\"630\" height=\"67\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/6bf99ef7-d57b-4694-b3b7-faf3a7fbe1ab\" /> \n\u003Cbr>\u003Cbr>\n\n\nSo is there an other way to set a `BASE_URL` to Server Components, or is it a bug?\n\nThank you for your help!",[3236,3237,3240],{"name":3140,"color":3141},{"name":3238,"color":3239},"needs reproduction","FBCA04",{"name":3241,"color":3242},"server components","839413",32751,"Server components (nuxt island) urls are relative and can't be resolved from other domains or subdomains","2025-09-05T13:49:45Z","https://github.com/nuxt/nuxt/issues/32751",0.72083426,{"labels":3249,"number":3252,"owner":3143,"repository":3143,"state":3207,"title":3253,"updated_at":3254,"url":3255,"score":3256},[3250,3251],{"name":3140,"color":3141},{"name":3204,"color":3205},7227,"issue with Nuxt router (SPA mode - website served as static)","2023-01-22T15:34:50Z","https://github.com/nuxt/nuxt/issues/7227",0.72368443,{"description":3258,"labels":3259,"number":3265,"owner":3143,"repository":3143,"state":3207,"title":3266,"updated_at":3267,"url":3268,"score":3269},"### What problem does this feature solve?\r\n\r\nI'm refactoring a system with nuxtjs and that system can be used by users to create your own \"sites\". So each site can be accessed with a configured path, for example mydomain.com/client1, mydomain.com/client2-my-site and mydomain.com/other-user-url (the pages inside each site are fixed, like mydomain.com/client1/about-us, mydomain.com/client1/our-work etc). \r\n\r\nI was able to work with custom routes (extendRoute), like this:\r\n\r\n```\r\nextendRoutes (routes, resolve) {\r\n routes.splice(0, routes.length); // reset nuxt automatic routes config\r\n routes.push({\r\n name: 'about-us',\r\n path: '/:myclient?/about-us',\r\n component: 'pages/about-us.vue',\r\n });\r\n}\r\n```\r\n\r\nBut that way I need to set a base path variable on store (on nuxtServerInit) and use it on all links because sites can also be accessed from external domain (premium feature), like myclient-owndomain.com/about-us. So this base path variable can be \"/\" (accessing from external domain) or \"/:myclient\" (accessing from internal domain) and must be used to render links, like:\r\n\r\n```\r\n\u003Cnuxt-link :to=\"$store.routerBasePath+'/about-us'\">About us\u003C/nuxt-link>\r\n```\r\n\r\nSo I think a better way to solving this is setting the router.base config dynamically (with a function), instead a fixed string.\r\n\r\nOr is there another way to do that on nuxtjs?\r\n\r\nThanks!\r\n\r\n### What does the proposed changes look like?\r\n\r\nThis feature will make router.base config more flexible (an alternative when necessary), using a syntax like that:\r\n\r\n```\r\nrouter: {\r\n base: function(context) {return context.params.myclient}\r\n}\r\n```\r\n\r\n\u003C!--cmty-->\u003C!--cmty_prevent_hook-->\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/c9299\">#c9299\u003C/a>)\u003C/em>\u003C/sub>\u003C/div>",[3260,3261,3264],{"name":3153,"color":3171},{"name":3262,"color":3263},"available soon","6de8b0",{"name":3204,"color":3205},5852,"Dynamic router base","2023-01-22T15:50:56Z","https://github.com/nuxt/nuxt/issues/5852",0.7243058,["Reactive",3271],{},["Set"],["ShallowReactive",3274],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQC2vcuZ5e302hzPj5THegxOeAn6-cOlqcfcvzJ0349I":-1},"/nuxt/ui/4202"]