`\r\n\r\nWhat I want to discuss is \r\n* whether this feature is necessary or not. \r\n* If so, Whether the main branch can provide this feature\r\n\r\n### Validations\r\n\r\n- [x] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],3906,"Another way to use vue components in markdown file","2024-06-08T04:41:51Z","https://github.com/vuejs/vitepress/issues/3906",0.6919383,{"description":2909,"labels":2910,"number":2915,"owner":2869,"repository":2870,"state":2895,"title":2916,"updated_at":2917,"url":2918,"score":2919},"The site title gets wrapped when it's too long. I think we should set a max width and `text-overflow: ellipsis`.\r\n\r\nIt's happening on Vite's main branch doc => https://main.vitejs.dev\r\n\r\n\u003Cimg width=\"752\" alt=\"Screen Shot 2023-01-27 at 9 32 57\" src=\"https://user-images.githubusercontent.com/3753672/214981049-d230fb16-c948-4f57-b632-6648c8acaeae.png\">\r\n",[2911,2914],{"name":2912,"color":2913},"theme","0754FB",{"name":2866,"color":2867},1846,"Fix site title wrapping on layout home","2023-08-12T00:04:42Z","https://github.com/vuejs/vitepress/issues/1846",0.6931527,{"description":2921,"labels":2922,"number":2924,"owner":2869,"repository":2870,"state":2895,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Describe the bug\n\nAfter build in MPA mode, the woff2 file aren't copy to assets dir, but style.xxx.css used it.\n\n### Reproduction\n\nany md file\n\n### Expected behavior\n\nIn MPA file, the woff2 file can be copied to assets dir\n\n### System Info\n\n```shell\nwindows vitepress@1.0.0-alpha.60\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2923],{"name":2892,"color":2893},2094,"Missing woff2 file in MPA mode","2023-03-24T00:04:12Z","https://github.com/vuejs/vitepress/issues/2094",0.69821346,{"description":2930,"labels":2931,"number":2932,"owner":2869,"repository":2870,"state":2895,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### Is your feature request related to a problem? Please describe.\n\nI would like to create a vitepress site and store it on a cdn, but it will be served from a different location. For example, the files would live somewhere like `https://cdn.example.com/docs/0.1.2+myhash/`, but be served from `https://example.com/docs`. I would like to configure how the asset locations are generated such that all `link`, `script`, and css `url` references are scoped to `https://cdn.example.com/docs/0.1.2+myhash/`.\n\n### Describe the solution you'd like\n\nIt appears that `vite-plugin-ssr` has the ability to do what I'm suggesting via the `baseAssets` and cites putting assets on a cdn as a primary example: https://vite-plugin-ssr.com/base-url#baseassets. As far as I can tell, `vitepress` only allows you to configure the `base` parameter, which is close to but not exactly what I'm after.\n\n### Describe alternatives you've considered\n\nI've tried two solutions so far, but neither seem to cover the use case 100%:\r\n1. Try to use `vite-plugin-ssr` in my vitepress config. This ends up throwing warning in the build because it can't resolve a `@theme` alias referenced in vitepress (as well as my other custom aliases I've omitted), and it throws an error saying that \"Error: [vite-plugin-ssr][Wrong Usage] At least one page should be defined, see https://vite-plugin-ssr.com/add\"\r\n\r\n```javascript\r\nexport default defineConfig({\r\n title: 'Docs',\r\n description: 'Some docs description',\r\n base: '/docs/',\r\n srcDir: './src',\r\n outDir: './dist',\r\n vite: {\r\n plugins:[\r\n ssr({\r\n baseAssets: cdnPath,\r\n }),\r\n ],\r\n },\r\n});\r\n```\r\n\r\n2. Parse the built document via `transformHtml` and change the references after the fact. This is very close, but does not handle the css `url` references.\r\n\r\n```javascript\r\nexport default defineConfig({\r\n lang: 'en-US',\r\n title: 'Docs',\r\n description: 'Some docs description',\r\n base: '/docs/',\r\n transformHtml: (html) => {\r\n const dom = new JSDOM(html);\r\n const { head } = dom.window.document;\r\n\r\n Array.from(head.getElementsByTagName('link')).forEach((link) => {\r\n link.href = transformUrl(link.href);\r\n });\r\n\r\n Array.from(head.getElementsByTagName('script')).forEach((script) => {\r\n if (script.type === 'module') {\r\n script.src = transformUrl(script.src);\r\n }\r\n });\r\n\r\n return dom.serialize();\r\n },\r\n srcDir: './src',\r\n outDir: './dist',\r\n});\r\n```\r\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],2919,"Support for baseAssets ssr config","2023-09-15T00:04:12Z","https://github.com/vuejs/vitepress/issues/2919",0.7223056,{"description":2938,"labels":2939,"number":2943,"owner":2869,"repository":2870,"state":2895,"title":2944,"updated_at":2945,"url":2946,"score":2947},"I trying to create a dropdown with versions of my app, and remove (or add) elements based on this version. Anyone have example how to make it? or maybe its a proposal to make default in vite",[2940],{"name":2941,"color":2942},"duplicate","cfd3d7",1550,"[Question] How to create a dropdown version?","2023-01-21T14:22:48Z","https://github.com/vuejs/vitepress/issues/1550",0.7232799,{"description":2949,"labels":2950,"number":2955,"owner":2869,"repository":2870,"state":2895,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Describe the bug\n\nWhen sidebar is not present, the page is not scrolled and outline is scrolled down, it overflows the navbar.\r\n\r\n \r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-v81ufa\r\n\r\n1. Make sure width is high enough so that outline is shown\r\n2. Without scrolling the main page content hover over the outline and scroll down\r\n3. Observe that the outline overflows the navbar\n\n### Expected behavior\n\nOutline is clipped when over navbar in the same way when sidebar is present.\n\n### System Info\n\n```sh\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (16) x64 Intel(R) Core(TM) i7-6900K CPU @ 3.20GHz\r\n Memory: 45.66 GB / 63.92 GB\r\n Binaries:\r\n Node: 18.2.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.5 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 9.6.6 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 113.0.5672.127\r\n Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.50)\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.1\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2951,2952],{"name":2912,"color":2913},{"name":2953,"color":2954},"contribution welcome","11E4B8",2442,"Outline overflows navbar when sidebar not present","2023-08-16T00:04:22Z","https://github.com/vuejs/vitepress/issues/2442",0.72394544,{"description":2961,"labels":2962,"number":2963,"owner":2869,"repository":2870,"state":2895,"title":2964,"updated_at":2965,"url":2966,"score":2967},"### Is your feature request related to a problem? Please describe.\n\nLet's say we got a folder structure like this:\r\n\r\n\r\n└─ foo\r\n ├─ 1.0.0.md\r\n ├─ 2.0.0.md\r\n └─ 3.0.0.md\r\n\r\nRight now we would have routes like:\r\n `/foo/1.0.0.html`\r\n `/foo/2.0.0.html`\r\n `/foo/3.0.0.html`\r\n\r\nI'd like to also have a route or alias like the following: `/foo/latest` which will point to the latest version (this can all be determined on build time by looking at the file, I already have a function that gives me the latest \"route\", in this case `/foo/3.0.0.html`.\r\n\r\nHow can I make this `/foo/latest` route exist and be an alias to the one I wanted?\n\n### Describe the solution you'd like\n\nAllow us to define route aliases or redirects\n\n### Describe alternatives you've considered\n\nI've tried with rewrites but that allowed me to make the latest version redirected to /latest instead. I want the reverse.\n\n### Additional context\n\nIf this is not something you think vitepress should have because it's not SSG friendly (there is no latest.html file) then I understand.\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.dev).\n- [X] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[],2922,"Route Alias or Redirect","2023-09-16T00:04:02Z","https://github.com/vuejs/vitepress/issues/2922",0.7264587,["Reactive",2969],{},["Set"],["ShallowReactive",2972],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fLQU7uYBAQytFLEyLPFohCEJYFv4y_Xv3j5KUKwwz120":-1},"/vuejs/vitepress/2084"]