\r\n```\r\nPreview:\r\n\r\n\n\n### Expected behavior\n\nWhen the title has the badge, the corresponding directory text should not have badge text.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (4) x64 Intel(R) Core(TM) i7-7500U CPU @ 2.70GHz\r\n Memory: 1.70 GB / 15.43 GB\r\nBinaries:\r\n Node: 14.20.0 - D:\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - D:\\nodejs\\yarn.CMD\r\n npm: 6.14.17 - D:\\nodejs\\npm.CMD\r\nBrowsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (108.0.1462.54)\r\n Internet Explorer: 11.0.19041.1566\r\nnpmPackages:\r\n vitepress: ^1.0.0-alpha.36 => 1.0.0-alpha.36\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3058],{"name":3059,"color":3060},"bug: pending triage","e99695",1789,"Outline has badge text","2023-01-21T14:16:43Z","https://github.com/vuejs/vitepress/issues/1789",0.6914289,{"description":3067,"labels":3068,"number":3070,"owner":3027,"repository":3028,"state":3038,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Is your feature request related to a problem? Please describe.\r\n\r\nNow that the pathname protocol has been removed (5836fac) I believe there is no way to configure a sidebar link which points to an external resource.\r\n\r\n### Describe the solution you'd like\r\n\r\nI assume we need the same customisation as is available for nav items:\r\n\r\nhttps://vitepress.dev/reference/default-theme-nav#customize-link-s-target-and-rel-attributes\r\n\r\n\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\r\n\r\n### Additional context\r\n\r\n_No response_\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.",[3069],{"name":3047,"color":3048},2851,"Allow sidebar links to customise target & rel attributes","2023-09-02T00:04:12Z","https://github.com/vuejs/vitepress/issues/2851",0.69427395,{"description":3076,"labels":3077,"number":3079,"owner":3027,"repository":3028,"state":3038,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Describe the bug\r\n\r\nHey, not sure if it's a bug or not, but the anchor in markdown seems not working if the case does not match.\r\n\r\nIn my PhpStorm and Typora, it works. In `GitHub README.md` preview, it works. But in VitePress it doesn't work.\r\n\r\n### Reproduction\r\n\r\nHosted: (`.md` files are the same)\r\n\r\nVitePress: https://docs.aelita.me/docs/vite-plugin-inject-html.html\r\n~~GitHub: https://github.com/xsjcTony/vite-plugin-inject-html/tree/main/packages/vite-plugin-inject-html~~ (Removed anchors, so longer valid. But it's working on GitHub sites anyway)\r\n\r\nPlease try to click on either `externalStyleSheets` or `otherTags`, since they are in camelCase, it's not working in VitePress, no idea if it's a bug or expected behaviour. (Click on links in main content at the top, not the side bar)\r\n\r\n### Expected behavior\r\n\r\nIt should jump to anchor, ignoring the case.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz\r\n Memory: 42.08 GB / 63.84 GB\r\n Binaries:\r\n Node: 18.14.0 - C:\\NodeJS\\node.EXE\r\n Yarn: 1.22.19 - C:\\NodeJS\\yarn.CMD\r\n npm: 9.4.2 - C:\\NodeJS\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (110.0.1587.41)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.45 => 1.0.0-alpha.45\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n_No response_\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.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3078],{"name":3059,"color":3060},1927,"Markdown's anchor is case sensitive","2023-03-23T00:04:25Z","https://github.com/vuejs/vitepress/issues/1927",0.7005591,{"description":3085,"labels":3086,"number":3090,"owner":3027,"repository":3028,"state":3038,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Describe the bug\n\ncode-group is used, but it does not work\r\n\n\n### Reproduction\n\nI used **stackblitz**\r\n\r\nhttps://stackblitz.com/edit/vite-r6wzwe?file=docs/example.md\n\n### Expected behavior\n\nTabs should be switched.\n\n### System Info\n\n```shell\nstackblitz online\n```\n\n\n### Additional context\n\n\r\n\r\n\r\nThe ID is always created the same.\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3087],{"name":3088,"color":3089},"upstream","BF29ED",1981,"code-group does not work","2023-03-23T00:04:22Z","https://github.com/vuejs/vitepress/issues/1981",0.7040985,{"description":3096,"labels":3097,"number":3098,"owner":3027,"repository":3028,"state":3038,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### 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.70887035,{"description":3104,"labels":3105,"number":3106,"owner":3027,"repository":3028,"state":3038,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Is your feature request related to a problem? Please describe.\n\n> This is same as https://github.com/vuejs/vuepress/issues/2704\r\n\r\nThat issue was for prism but VitePress uses shiki. Is it possible to achieve language highlight with diff language?\n\n### Describe the solution you'd like\n\nna\n\n### Describe alternatives you've considered\n\nna\n\n### Additional context\n\nI use language highlighting for now instead of showing diff because without language highlight diff looks really bad. It takes some time for users to under what changes between two snippets but it's better highlighted.\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\n- [X] Read the [docs](https://vitepress.vuejs.org).\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.",[],830,"[Feature Request] Diff and Language Highlights","2023-01-21T14:23:00Z","https://github.com/vuejs/vitepress/issues/830",0.7108526,{"description":3112,"labels":3113,"number":3115,"owner":3027,"repository":3028,"state":3038,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### 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.",[3114],{"name":3059,"color":3060},2094,"Missing woff2 file in MPA mode","2023-03-24T00:04:12Z","https://github.com/vuejs/vitepress/issues/2094",0.71146595,["Reactive",3121],{},["Set"],["ShallowReactive",3124],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fpwSZXb1GfntFIJJBQEWV7xh2iQvX29eISB9L14R1-yA":-1},"/vuejs/vitepress/2534"]