\r\n\r\n::: zh-CN\r\n中文\r\n:::\r\n\r\n::: en\r\nEnglish\r\n:::\r\n```\r\n\r\nThis reduces maintenance costs.\r\n\r\nI came up with a very low cost implementation - [CSS-I18N](https://github.com/valaxyjs/css-i18n)\r\nAnd I implemented it in my own project [valaxy](https://github.com/YunYouJun/valaxy).\r\n\r\nIt works well. You can preview it [here](https://valaxy.site/guide/i18n).\r\nAnd this is my implementation: [How to realize CSS i18n?](https://valaxy.site/posts/i18n#css-i18n-another-solution)\r\n\r\n---\r\n\r\nIt is very cost-effective and I hope to integrate it with vitepress.\r\nIf you agree with my proposal, please let me know and I can create a PR for vitepress.\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.",[2905],{"name":2869,"color":2870},3047,"CSS i18n in one page","2025-03-02T18:10:37Z","https://github.com/vuejs/vitepress/issues/3047",0.76794004,{"description":2912,"labels":2913,"number":2918,"owner":2872,"repository":2873,"state":2874,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Describe the bug\n\nI've followed https://vitepress.dev/guide/using-vue#vs-code-intellisense-support to enable intellisense in markdown files. But current intellisense may not work properly when there're Latex contents.\n\n### Reproduction\n\nIt's kinda hard to reproduce though, it randomly occurs for me. And adding spaces in between may or may not resolve the intellisense error. But the problematic intellisense tends to happen when there's `\u003Csomevar\\somecommand` (invalid character), `\\ ` (':' is expected), `xxx$.` (parsed as variable)\n\nUsed markdown from https://github.com/vuejs/vitepress/issues/4290 as the template:\n```markdown\n---\nhello: world\n---\n\n\u003Cscript setup>\nimport { ref } from 'vue'\n\nconst count = ref(0)\n\u003C/script>\n\n## Title\n\nThe count is: {{ count }}\n\n\u003Cbutton :class=\"$style.button\" @click=\"count++\">Increment\u003C/button>\n\n$$\n\u003Cp_i\\leq\n$$\n\n$xxx$.\n\n$\\ $\n\n\u003Cstyle module>\n.button {\n color: red;\n font-weight: bold;\n}\n\u003C/style>\n```\n\n\n\n### Expected behavior\n\nThe intellisense in markdown files should be more robust and can handle these cases when Latex content is presented in the posts.\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 11 10.0.26100\n CPU: (16) x64 AMD Ryzen 7 7435HS\n Memory: 7.24 GB / 23.74 GB\n Binaries:\n Node: 23.6.1 - D:\\Scoop\\apps\\nodejs\\current\\node.EXE\n npm: 10.9.2 - D:\\Scoop\\apps\\nodejs\\current\\npm.CMD\n pnpm: 10.0.0 - D:\\Scoop\\shims\\pnpm.EXE\n Browsers:\n Edge: Chromium (130.0.2849.68)\n Internet Explorer: 11.0.26100.1882\n npmPackages:\n vitepress: 1.5.0 => 1.5.0\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.",[2914,2917],{"name":2915,"color":2916},"upstream","BF29ED",{"name":2869,"color":2870},4528,"Markdown Intellisense Randomly Breaks When Containing Latex","2025-03-02T18:07:44Z","https://github.com/vuejs/vitepress/issues/4528",0.77284116,{"description":2924,"labels":2925,"number":2927,"owner":2872,"repository":2873,"state":2874,"title":2928,"updated_at":2929,"url":2930,"score":2931},"### Is your feature request related to a problem? Please describe.\n\nI started using VitePress a long time ago, about 4 years back. I don't want to waste developers' time listening to me ramble, but the main reason I'm bringing this up is that I've accumulated a lot of notes. \r\n\r\nEvery time I publish a new note, I have to manually add the blog path in Sider, which is really inconvenient! I just want to write notes, and filling in the note path in Sider is a hassle for me. \r\n\r\nOf course, I noticed this issue: https://github.com/vuejs/vitepress/issues/572#issuecomment-1170116225\r\n\r\nBut it seems like it would require more work, which just adds to the burden of writing my notes!\n\n### Describe the solution you'd like\n\nI just want to happily take notes without worrying about file paths. I hope vitepress can intelligently analyze the note paths and stop making the note authors stress over this.\r\n\r\nFor example, if vitepress knows all the locations of my notes, then it should refresh the content of the sider and nav every time it builds.\r\n\r\nPlease don't overlook this issue. Thanks! \r\n\r\nThe number of notes users have keeps increasing over time, and users migrating from other frameworks face this problem even more. They need to manually fill in a lot of sider and nav, which raises their costs. \r\n\r\nPlease don't ignore this issue. Thank you!\n\n### Describe alternatives you've considered\n\nnull\n\n### Additional context\n\nnull\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.",[2926],{"name":2869,"color":2870},4229,"[feature] Request vitepress to automatically generate a sider from the file directory","2024-10-26T17:17:16Z","https://github.com/vuejs/vitepress/issues/4229",0.77802247,{"description":2933,"labels":2934,"number":2935,"owner":2872,"repository":2873,"state":2936,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Is your feature request related to a problem? Please describe.\n\nI need references cited in the paper in the docs like writing papers.\r\n\n\n### Describe the solution you'd like\n\n references cited support can jump each other\r\n\r\nDocusaurus and GitHub support this.but not work for VitePress😭\r\n\r\n\r\neg.\r\n\r\n```\r\nsometext[^1]\r\n[^1]: something\r\n```\r\nsometext[^1]\r\n[^1]: something\r\n\r\n\r\n\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.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.",[],1081,"closed","References cites support","2023-01-21T14:30:03Z","https://github.com/vuejs/vitepress/issues/1081",0.73632956,{"description":2942,"labels":2943,"number":2945,"owner":2872,"repository":2873,"state":2936,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Is your feature request related to a problem? Please describe.\n\nI'd like to be able to customise some navbar links with custom HTML/CSS\n\n### Describe the solution you'd like\n\nRender HTML in navbar links\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\n\u003Cimg width=\"477\" alt=\"Screenshot 2022-11-30 at 11 08 39\" src=\"https://user-images.githubusercontent.com/10400064/204768526-3add748b-1b92-4184-bfd7-15bd4e93e83a.png\">\r\n\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.",[2944],{"name":2866,"color":2867},1652,"Allow HTML in nav links","2023-08-12T00:04:13Z","https://github.com/vuejs/vitepress/issues/1652",0.7463105,{"description":2951,"labels":2952,"number":2954,"owner":2872,"repository":2873,"state":2936,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Describe the bug\n\nbuild error:\nReferenceError: window is not defined\n at file:///E:/docs/.vitepress/.temp/app.js?t=1741415492907:9826:3\n at ModuleJob.run (node:internal/modules/esm/module_job:222:25)\n at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)\n at async build (file:///E:/node_modules/.pnpm/vitepress@1.0.1_@algolia+client-search@4.20.0_@types+node@20.8.10_async-validator@4.2.5_axios_6jmcxapznl6bymfiwls65tjhl4/node_modules/vitepress/dist/node/serve-C_2bYS0g.js:46722:24)\n ELIFECYCLE Command failed with exit code 1.\n ELIFECYCLE Command failed with exit code 1.\n\n\n\n### Reproduction\nVitePress is the most difficult tool I have ever used, because you don't even know where the error is coming from!\n**I can't tell where the error is. This project has tens of thousands of lines of code. How can I find it?**\n\n### Expected behavior\n\nFind the file with the error message\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 10 10.0.19045\n CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz\n Memory: 15.36 GB / 31.94 GB\n Binaries:\n Node: 20.15.0 - C:\\Program Files\\nodejs\\node.EXE\n npm: 10.7.0 - C:\\Program Files\\nodejs\\npm.CMD\n pnpm: 9.14.2 - C:\\Program Files\\nodejs\\pnpm.CMD\n Browsers:\n Chrome: bookmarks.html\ninitial_preferences\n Edge: Spartan (44.19041.1266.0), Chromium (127.0.2651.74)\n Internet Explorer: 11.0.19041.1566\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.",[2953],{"name":2895,"color":2896},4606,"ReferenceError: window is not defined!!!","2025-03-18T04:44:37Z","https://github.com/vuejs/vitepress/issues/4606",0.75335616,{"description":2960,"labels":2961,"number":2965,"owner":2872,"repository":2873,"state":2936,"title":2966,"updated_at":2967,"url":2968,"score":2969},"### Describe the bug\r\n\r\nHey guys!\r\n\r\nI was trying to emulate [team layout from Vite.js docs](https://vitejs.dev/team.html) for an internal company docs where I'm working. My boss want a clear and simple navbar, so he proposed [setup sidebar items to be collapsible](https://vitepress.vuejs.org/guide/theme-sidebar.html#collapsible-sidebar-groups). He wants a team page, so I was working on it using [`page` layout](https://vitepress.vuejs.org/config/frontmatter-configs.html#layout). All good, but I noticed [when sidebar is configured using `SidebarGroup[]` interface](https://vitepress.vuejs.org/config/theme-configs.html#sidebar), `page` layout renders with the sidebar visible, against when I configure sidebar with `SidebarMulti` interface. \r\n\r\nI have tested `aside: false` with no success. I'll be happy if this report is my mistake.\r\n\r\n### Reproduction\r\n\r\n1. config.ts content\r\n\r\n```ts\r\nexport default defineConfig({\r\n themeConfig: {\r\n sidebar: [\r\n {\r\n text: 'Guía',\r\n collapsible: true,\r\n items: [\r\n {\r\n text: 'Motivación',\r\n link: '/guia/motivacion'\r\n },\r\n {\r\n text: 'Introducción',\r\n link: '/guia/'\r\n },\r\n {\r\n text: 'Estructura',\r\n link: '/guia/estructura'\r\n },\r\n ]\r\n },\r\n {\r\n text: 'Configuración',\r\n collapsible: true,\r\n items: [\r\n {\r\n text: 'Motivación',\r\n link: '/config/motivacion'\r\n },\r\n {\r\n text: 'Introducción',\r\n link: '/config/'\r\n },\r\n {\r\n text: 'Desarrollo',\r\n link: '/config/desarrollo'\r\n },\r\n ]\r\n },\r\n ]\r\n }\r\n})\r\n```\r\n\r\n2. Create `team.js` into folder `_data`\r\n3. Create `team.md` in the same level of `index.md`\r\n\r\n\r\n### Expected behavior\r\n\r\n`team.md` should be a page layout without sidebar visible\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 12.5\r\n CPU: (8) arm64 Apple M1\r\n Memory: 89.86 MB / 8.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.15.1 - ~/.nvm/versions/node/v16.15.1/bin/node\r\n npm: 8.12.2 - ~/.nvm/versions/node/v16.15.1/bin/npm\r\n Browsers:\r\n Firefox: 100.0\r\n Safari: 15.6\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nWhen I configure sidebar in this way, it works smooth.\r\n\r\n```ts\r\nsidebar: {\r\n '/guia': [\r\n {\r\n text: 'Guía',\r\n collapsible: true,\r\n items: [\r\n {\r\n text: 'Motivación',\r\n link: '/guia/motivacion'\r\n },\r\n {\r\n text: 'Introducción',\r\n link: '/guia/'\r\n },\r\n {\r\n text: 'Estructura',\r\n link: '/guia/estructura'\r\n },\r\n {\r\n text: 'Desarrollo en local',\r\n link: '/guia/local'\r\n },\r\n {\r\n text: 'Compilación a producción',\r\n link: '/guia/compilacion'\r\n },\r\n {\r\n text: 'Solucion de errores',\r\n link: '/guia/soluciones'\r\n },\r\n ]\r\n }\r\n ],\r\n }\r\n```\r\n\r\nAnd adding another array, p.ex:\r\n ```ts\r\n\r\nsidebar: {\r\n '/guia': [\r\n {\r\n text: 'Guía',\r\n collapsible: true,\r\n items: [\r\n {\r\n text: 'Motivación',\r\n link: '/guia/motivacion'\r\n },\r\n {\r\n text: 'Introducción',\r\n link: '/guia/'\r\n },\r\n {\r\n text: 'Estructura',\r\n link: '/guia/estructura'\r\n },\r\n {\r\n text: 'Desarrollo en local',\r\n link: '/guia/local'\r\n },\r\n {\r\n text: 'Compilación a producción',\r\n link: '/guia/compilacion'\r\n },\r\n {\r\n text: 'Solucion de errores',\r\n link: '/guia/soluciones'\r\n },\r\n ]\r\n }\r\n ],\r\n '/test': [\r\n {\r\n text: 'Test',\r\n collapsible: true,\r\n items: [\r\n {\r\n text: 'Motivación',\r\n link: '/Test/motivacion'\r\n },\r\n {\r\n text: 'Introducción',\r\n link: '/test/'\r\n },\r\n ]\r\n }\r\n ],\r\n }\r\n})\r\n```\r\n\r\nIt doesn't renders \"test\", no matter this structure is correct according interfaces\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.",[2962],{"name":2963,"color":2964},"bug: pending triage","e99695",1141,"`page` layout is ignored when `sidebar` is configured with `SidebarGroup[]` interface","2023-01-21T14:28:49Z","https://github.com/vuejs/vitepress/issues/1141",0.75863427,["Reactive",2971],{},["Set"],["ShallowReactive",2974],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBvsW0q1ez5oLiBJhZLY9KGDzZBQULlgGSfou1ifIrzY":-1},"/vuejs/vitepress/1237"]