```\r\n\r\nIt doesn't seem to be correct:\r\n\r\n\r\n\r\nHow to make it look correct, just like on the homepage?:\r\n\r\n\r\n\r\n",[2905],{"name":2868,"color":2869},4273,"How to use default Vue components elsewhere","2024-12-03T17:27:39Z","https://github.com/vuejs/vitepress/issues/4273",0.7097662,{"description":2912,"labels":2913,"number":2915,"owner":2874,"repository":2875,"state":2876,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Is your feature request related to a problem? Please describe.\n\nSyntax highlighting is really poor (and often incorrect) for Swift. This is a common issue with the TextMate grammar.\n\n### Describe the solution you'd like\n\nI'd like to see support for alternative ways of syntax highlighting. On the client side, Highlight.js has much better results, but ideally, I'd like to be able to roll my own solution on top of SwiftSyntax (which parses the code as the compiler would) and plug it into VitePress.\r\n\r\nIs there a way to achieve this? Currently, my choice of a static-site generator is tied to their choice of syntax highlighting for Swift, which is not ideal.\n\n### Describe alternatives you've considered\n\n_No response_\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.",[2914],{"name":2868,"color":2869},3352,"Alternative syntax highlighting","2024-01-18T18:48:00Z","https://github.com/vuejs/vitepress/issues/3352",0.7134057,{"description":2921,"labels":2922,"number":2924,"owner":2874,"repository":2875,"state":2876,"title":2925,"updated_at":2926,"url":2927,"score":2928},"### Is your feature request related to a problem? Please describe.\r\n\r\n1. 我是从 `gitbook`,`mdbook` 过来的用户,这两个工具对侧边栏的目录数据,都是从文档的 `SUMMARY.md` 文件读取的。\r\n\r\n2. 最近发现了 `vuepress`,`vitepress` ,了解到这两个工具对侧边栏的目录数据是通过 `themeConfig` 枚举配置的,功能丰富实用强大。\r\n\r\n### Describe the solution you'd like\r\n\r\n但是我们有时候并不希望完全在服务端控制这个书本的目录列表数据,希望可以提供多一个类似 `gitbook`,`mdbook` 的方式,可以让用户自己去编写 `SUMMARY.md` 文件更新侧边栏目录数据。\r\n\r\n一者可以减少 config 文件的修改,二来也能提升各个书本自行对目录的把控。",[2923],{"name":2868,"color":2869},3704,"Multiple Sidebars auto produce/关于侧边栏的自动生成建议","2025-03-02T18:09:29Z","https://github.com/vuejs/vitepress/issues/3704",0.7204494,{"description":2930,"labels":2931,"number":2935,"owner":2874,"repository":2875,"state":2936,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Describe the bug\n\nI installed Vitepress, built then ran it locally following the documentation of Vercel and everything seemed fine. But when I deployed it to my personal Vercel, my site keeps loading the 404.html. When I visit the Output of Vercel, I couldn't find any index.html and only 404.html. \r\n\r\nHere is currently [the blog of mine](https://vitepress-doc-kappa.vercel.app/) that I deployed to Vercel.\r\n\r\nThis is my current source on Vercel:\r\n\r\n\r\nThis is my current output on Vercel:\r\n\r\n\r\n\n\n### Reproduction\n\nNot sure if this is the correct way to reproduce, but I'll list down the commands that I ran, from install command to deploy:\r\n\r\n```bash\r\nnpm add -D vitepress\r\nnpx vitepress init ./\r\nnpm run docs:build\r\nnpm run docs:preview\r\nvercel --prod\r\n```\n\n### Expected behavior\n\nPage should load index.html when visiting `/`.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19043\r\n CPU: (4) x64 Intel(R) Pentium(R) CPU G4560 @ 3.50GHz\r\n Memory: 2.27 GB / 7.96 GB\r\n Binaries:\r\n Node: 20.0.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 9.6.4 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (120.0.2210.133)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.39 => 1.0.0-rc.39\n```\n\n\n### Additional context\n\nI use a fresh setup of Vitepress and deploy to a Vercel setting using Node v20.x (which as mentioned on Vercel that is still in Beta). However I did try Node v18.x on Vercel and the error is the same. \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.",[2932],{"name":2933,"color":2934},"bug: pending triage","e99695",3460,"closed","Site auto loads 404.html after deployed to Vercel","2024-01-24T00:04:46Z","https://github.com/vuejs/vitepress/issues/3460",0.6780996,{"description":2942,"labels":2943,"number":2947,"owner":2874,"repository":2875,"state":2936,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Is your feature request related to a problem? Please describe.\r\n\r\nConveniently use content-adaptive layout in components on the home page\r\n\r\n### Describe the solution you'd like\r\n\r\n`.vitepress/theme/index.ts`:\r\n```ts\r\nimport HomePage from './component/HomePage'\r\n\r\nexport default {\r\n Layout: () => {\r\n return h(Theme.Layout, null, {\r\n 'home-features-after': () => h(HomePage),\r\n })\r\n },\r\n```\r\n\r\n---\r\n\r\n`HomePage.vue`:\r\n\r\n```html\r\n\u003Cscript setup lang=\"ts\">\r\nimport{ VPHomeContent } from 'vitepress/theme'\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n\t\u003CVPHomeContent>\r\n\t\t\u003C!-- my custom content -->\r\n\t\u003C/VPHomeContent>\r\n\u003C/template>\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.",[2944],{"name":2945,"color":2946},"contribution welcome","11E4B8",3954,"[New feature] export `VPHomeContent` to provide content-adaptive layout","2024-06-22T04:41:46Z","https://github.com/vuejs/vitepress/issues/3954",0.682502,{"description":2953,"labels":2954,"number":2957,"owner":2874,"repository":2875,"state":2936,"title":2958,"updated_at":2959,"url":2960,"score":2961},"### Describe the bug\n\n`rewrite` rule doesn't work correctly when create new markdown file.\n\n### Reproduction\n\n1, Set `rewrite`\r\n\r\n```js\r\n// vitepress/config.js\r\nrewrite: [`en/:rest*`]: ':rest*'\r\n```\r\n\r\n2, Create new markdown file `docs/en/test.md`\r\n\r\n3, Expect visit file by url `/test`, but it redirect to `/en/test`.\r\n\r\n4, Restart dev server, problem resolved.\n\n### Expected behavior\n\nExpect `rewrite` rule work correctly when create new markdown file.\n\n### System Info\n\n```Text\nvitepress: 1.5.0\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.",[2955,2956],{"name":2933,"color":2934},{"name":2868,"color":2869},4385,"Rewrite not work when create new markdown file","2025-03-08T04:41:55Z","https://github.com/vuejs/vitepress/issues/4385",0.68337154,{"description":2963,"labels":2964,"number":2965,"owner":2874,"repository":2875,"state":2936,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Describe the bug\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\n直接打开控制台修改官方sidebar里的文字,插入\u003CT>即可复现\r\n\r\n### Expected behavior\r\n\r\n文字对齐\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 14.4.1\r\n CPU: (8) arm64 Apple M2\r\n Memory: 141.77 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.14.0 - ~/.nvm/versions/node/v18.14.0/bin/node\r\n Yarn: 1.18.0 - ~/.nvm/versions/node/v18.14.0/bin/yarn\r\n npm: 9.3.1 - ~/.nvm/versions/node/v18.14.0/bin/npm\r\n pnpm: 8.15.4 - ~/Library/pnpm/pnpm\r\n Browsers:\r\n Chrome: 131.0.6778.86\r\n Safari: 17.4.1\r\n npmPackages:\r\n vitepress: ^1.5.0 => 1.5.0\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] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],4399,"导航中插入的\u003CT>,两个尖括号没有对齐","2024-12-10T04:44:48Z","https://github.com/vuejs/vitepress/issues/4399",0.68605655,["Reactive",2971],{},["Set"],["ShallowReactive",2974],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fb6GyEdLzxb2M0_T3z1Znk9-AIm61CdtvOy0BZAxJMro":-1},"/vuejs/vitepress/4334"]