```\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",[2867],{"name":2868,"color":2869},"stale","ededed",4273,"vuejs","vitepress","open","How to use default Vue components elsewhere","2024-12-03T17:27:39Z","https://github.com/vuejs/vitepress/issues/4273",0.6957368,{"description":2879,"labels":2880,"number":2885,"owner":2871,"repository":2872,"state":2873,"title":2886,"updated_at":2887,"url":2888,"score":2889},"### Is your feature request related to a problem? Please describe.\n\nDue to my markdown file is particularly large, resulting in packaged js file and the corresponding html file size are close to 3M b, which in turn leads to the browser first screen rendering DOM size is too large.\n\n### Describe the solution you'd like\n\nIs it possible to reduce the size of the first screen html and lazy load the rest of the dom?\r\n\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\n\u003Cimg width=\"368\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/73653404/afe26e27-6e7a-489d-983a-42a6acbfff8e\">\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.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.",[2881,2882],{"name":2868,"color":2869},{"name":2883,"color":2884},"perf","378A61",3509,"DOM is oversized","2025-03-02T18:09:47Z","https://github.com/vuejs/vitepress/issues/3509",0.7118536,{"description":2891,"labels":2892,"number":2894,"owner":2871,"repository":2872,"state":2873,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### Is your feature request related to a problem? Please describe.\n\nMy project spans several repositories under a single GitHub user. I'm building a vitepress project (which is in its own repository) for documentation and API reference for all my repositories because they are all related to each other. I like to include Markdown and code snippets from each of the repositories. \r\n\r\nI've tried this for including files from my vitepress repository, like this\r\n\r\n```markdown\r\n\u003C!--@include: ./setup.md-->\r\n```\r\n\r\nand it works nicely, but \r\n\r\n```markdown\r\n\u003C!--@include: https://github.com/CVEProject/cvelistV5/blob/main/README.md#reporting-issues -->\r\n```\r\n\r\ndoes not work. \r\n\r\nIt would be very helpful to be able to include arbitrary markdown and code into my vitepress project. Is there a way to do this?\n\n### Describe the solution you'd like\n\nIt would be very helpful to be able to include arbitrary markdown and code into my vitepress project. \r\n\r\nSections from a Markdown file:\r\n```markdown\r\n\u003C!--@include: https://github.com/CVEProject/cvelistV5/blob/main/README.md#reporting-issues -->\r\n```\r\n\r\nLines from a JSON (or any source code) file:\r\n```markdown\r\n\u003C!--@include: https://github.com/CVEProject/cvelistV5/blob/main/cves/1999/0xxx/CVE-1999-0001.json{123,131} -->\r\n```\r\n\r\nIs there a way to do this?\n\n### Describe alternatives you've considered\n\nOne possible alternative to doing it in vitepress' markdown extension is to write a Vue component that reads in the file and displays that, but having it as a feature of vitepress so others can use it would be more useful to the vitepress community.\n\n### Additional context\n\nI think this feature would be useful for writing Guides and API References, but also other documentation (e.g., a full tutorial for using Vue and vitepress in a Docker container, in a section for how to set up the development environment) where it would be even more important so that the doc is always up-to-date with its dependent projects.\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.",[2893],{"name":2868,"color":2869},3349,"@include markdown and code files from an arbitrary public URL","2025-03-02T18:10:08Z","https://github.com/vuejs/vitepress/issues/3349",0.7301195,{"description":2900,"labels":2901,"number":2905,"owner":2871,"repository":2872,"state":2906,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### Describe the bug\n\n本地搜索功能,不能搜索到中文,只能搜索到段落的第一个字或标点符号后面的汉字\n\n### Reproduction\n\n本地搜索功能,不能搜索到中文,只能搜索到段落的第一个字或标点符号后面的汉字\n\n### Expected behavior\n\n本地搜索功能,不能搜索到中文,只能搜索到段落的第一个字或标点符号后面的汉字\n\n### System Info\n\n```Text\n本地搜索功能,不能搜索到中文,只能搜索到段落的第一个字或标点符号后面的汉字\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.",[2902],{"name":2903,"color":2904},"bug: pending triage","e99695",4350,"closed","本地搜索功能,不能搜索到中文,只能搜索到段落的第一个字或标点符号后面的汉字","2024-11-18T04:44:48Z","https://github.com/vuejs/vitepress/issues/4350",0.67508733,{"description":2912,"labels":2913,"number":2915,"owner":2871,"repository":2872,"state":2906,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Describe the bug\n\nhttps://github.com/vuejs/vitepress/blob/3eb4374af286362d7f4257b288fd2d5b9173dcba/src/client/theme-default/styles/vars.css#L177\r\n\r\nIncorrectly output as:\r\n```\r\n --vp-c-text-1: rgba(60, 60, 67);\r\n```\n\n### Reproduction\n\nThis can be found easily from the npm repo: https://www.npmjs.com/package/vitepress?activeTab=code\r\n\r\nThen go to `dist/client/theme-default/styles/vars.css`, line 177.\n\n### Expected behavior\n\nShould be\r\n```\r\n --vp-c-text-1: rgba(60, 60, 67, 1);\r\n```\n\n### System Info\n\n```Text\nNot relevant\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.",[2914],{"name":2903,"color":2904},4439,"Variable \"--vp-c-text-1\" is incorrect in the bundle ouput","2024-12-29T04:43:46Z","https://github.com/vuejs/vitepress/issues/4439",0.6771699,{"description":2921,"labels":2922,"number":2926,"owner":2871,"repository":2872,"state":2906,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Describe the bug\n\nThere is a SSR error on the production build output that happens with a specific user navigation (see below for reproduction steps).\r\n\r\nWhen a `\u003CTeleport />` has a conditional rendered children using `v-if`, the following error is thrown:\r\n\r\n```shell\r\nTypeError: Cannot read properties of null (reading 'nextSibling')\r\n at nextSibling (framework.w6niQ9Mc.js:17:682)\r\n at kt (framework.w6niQ9Mc.js:13:29640)\r\n at N (framework.w6niQ9Mc.js:13:21176)\r\n at v (framework.w6niQ9Mc.js:13:23760)\r\n at Object.process (framework.w6niQ9Mc.js:13:37355)\r\n at N (framework.w6niQ9Mc.js:13:21489)\r\n at v (framework.w6niQ9Mc.js:13:23760)\r\n at O (framework.w6niQ9Mc.js:13:23130)\r\n at L (framework.w6niQ9Mc.js:13:22048)\r\n at N (framework.w6niQ9Mc.js:13:21426)\r\n```\n\n### Reproduction\n\nMinimal reproduction link: https://stackblitz.com/edit/vitepress-nextsibling-ssr-error\r\n\r\nSee the `TeleportedComponent.vue` and `error-demo.md` files.\r\n\r\n___\r\n\r\n**Reproduction steps**:\r\n\r\n- Create a production build (`npm run docs:build`)\r\n- Serve the production (`npm run docs:dev`)\r\n- Go directly the URL where the custom component is imported\r\n- Interact with the custom component button to trigger the menu\r\n- An error is thrown in the console, the component doesn't work\r\n\r\nNow, this issue can be avoided if the user go to any other page that doesn't contain the component, and go back to this page.\n\n### Expected behavior\n\nThe conditional rendering of the children using a `v-if`, inside the `\u003CTeleport />`, should not cause any issues on the first page load.\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 14.5\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 95.19 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.14.0 - ~/.nvm/versions/node/v20.14.0/bin/node\r\n Yarn: 1.22.19 - ~/.yarn/bin/yarn\r\n npm: 10.7.0 - ~/.nvm/versions/node/v20.14.0/bin/npm\r\n pnpm: 8.15.1 - ~/Library/pnpm/pnpm\r\n Browsers:\r\n Brave Browser: 126.1.67.123\r\n Chrome: 126.0.6478.126\r\n Safari: 17.5\r\n npmPackages:\r\n vitepress: 1.2.3 => 1.2.3\n```\n\n\n### Additional context\n\nI've first noticed the issue when working on an open-source [vue3-select-component](https://github.com/TotomInc/vue3-select-component).\r\n\r\nE.g. go to https://vue3-select-component.vercel.app/demo/single-select.html and interact with the component. You'll see the same error thrown in the console.\r\n\r\nFor reference: https://github.com/TotomInc/vue3-select-component/issues/78\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.",[2923],{"name":2924,"color":2925},"need more info","bdbefc",3987,"SSR issue with Teleport and conditional rendering of its children (Cannot read properties of null (reading 'nextSibling'))","2024-07-04T04:41:55Z","https://github.com/vuejs/vitepress/issues/3987",0.688069,{"description":2932,"labels":2933,"number":2935,"owner":2871,"repository":2872,"state":2906,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### Describe the bug\r\n\r\nThe original md document:\r\n\r\n```\r\n hello \u003Cpicture>\r\n \u003Cimg src=\"https://github.com/markdown-it/markdown-it/assets/73653404/63aa836d-2541-40bb-a4be-aaf02495426d\"/>\r\n \u003C/picture>\r\n```\r\n\r\nAfter executing md.render it will be:\r\n```\r\n \u003Cp>hello \u003Cpicture>\u003C/p>\r\n \u003Cimg src=\"https://github.com/markdown-it/markdown-it/assets/73653404/63aa836d-2541-40bb-a4be-aaf02495426d\"/>\r\n \u003C/picture>\r\n```\r\n\r\n### Reproduction\r\n\r\nyou can try this markdown content:\r\n```\r\n hello \u003Cpicture>\r\n \u003Cimg src=\"https://github.com/markdown-it/markdown-it/assets/73653404/63aa836d-2541-40bb-a4be-aaf02495426d\"/>\r\n \u003C/picture>\r\n```\r\n### Expected behavior\r\n\r\nI hope after executing md.render it should be:\r\n```\r\n \u003Cp>hello\u003C/p>\u003Cpicture>\r\n \u003Cimg src=\"https://github.com/markdown-it/markdown-it/assets/73653404/63aa836d-2541-40bb-a4be-aaf02495426d\"/>\r\n \u003C/picture>\r\n```\r\n\r\n### System Info\r\n\r\n\r\n\u003Cimg width=\"1045\" alt=\"image\" src=\"https://github.com/markdown-it/markdown-it/assets/73653404/63aa836d-2541-40bb-a4be-aaf02495426d\">\r\n\r\n\r\n\r\n### Additional context\r\n\r\nThis seems to be caused by using some mdit plugin, because I tried it [here](https://markdown-it.github.io/#md3=%7B%22source%22%3A%22%20%20%20hello%20%3Cpicture%3E%5Cn%20%20%20%20%20%3Csource%20type%3D%5C%22image%2Favif%5C%22%20srcset%3D%5C%22https%3A%2F%2Fpicbed-1306720359.cos.ap-guangzhou.myqcloud.com%2Fupic%2F2024-02-07-17-37-OUE54Z.webp%3FimageMogr2%2Fformat%2Favif%5C%22%3E%5Cn%20%20%20%20%20%3Cimg%20src%3D%5C%22https%3A%2F%2Fpicbed-1306720359.cos.ap-guangzhou.myqcloud.com%2Fupic%2F2024-02-07-17-37-OUE54Z.webp%5C%22%20alt%3D%5C%22https%3A%2F%2Fpicbed-1306720359.cos.ap-guangzhou.myqcloud.com%2Fupic%2F2024-02-07-17-37-OUE54Z.webp%5C%22%20loading%3D%5C%22lazy%5C%22%2F%3E%5Cn%20%20%20%3C%2Fpicture%3E%22%2C%22defaults%22%3A%7B%22html%22%3Atrue%2C%22xhtmlOut%22%3Afalse%2C%22breaks%22%3Afalse%2C%22langPrefix%22%3A%22language-%22%2C%22linkify%22%3Atrue%2C%22typographer%22%3Atrue%2C%22_highlight%22%3Atrue%2C%22_strict%22%3Afalse%2C%22_view%22%3A%22src%22%7D%7D) and it converted correctly\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.",[2934],{"name":2924,"color":2925},3632,"inline html transform error","2024-04-28T12:27:40Z","https://github.com/vuejs/vitepress/issues/3632",0.6897934,{"description":2941,"labels":2942,"number":2943,"owner":2871,"repository":2872,"state":2906,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Describe the bug\r\n\r\nPossible similar issues:\r\n- https://github.com/vuejs/vitepress/issues/4099\r\n- https://github.com/vuejs/vitepress/issues/4167\r\n- https://github.com/vuejs/vitepress/issues/3780\r\n\r\n---\r\n\r\nHydration mismatch occurs only when reloading a specific page in the production build.\r\nIt can be reproduced locally as well.\r\nIt doesn’t happen in the development build, nor when navigating through the sidebar.\r\n\r\nhttps://github.com/user-attachments/assets/2bb6387c-2d62-4dc2-96e4-ecd5bdf3491f\r\n\r\n### Reproduction\r\n\r\nThis repository (my product)\r\n\r\nhttps://github.com/ubugeeei/reading-vuejs-core-vapor\r\n\r\n```sh\r\ngit clone https://github.com/ubugeeei/reading-vuejs-core-vapor\r\ncd reading-vuejs-core-vapor\r\nni\r\nDEBUG='*' nr build\r\nDEBUG='*' nr preview\r\n```\r\n\r\n---\r\n\r\n※ During the initial build, a fetch to GitHub will run, so it may take a little time.\r\n(From the second time onward, the cache will be used)\r\n\r\nThe plugin implementation is here.\r\nhttps://github.com/ubugeeei/reading-vuejs-core-vapor/tree/9fa8c614c6047241dc2a6bdac39dca1815318d6a/.vitepress/plugins/markdown-it/github\r\n\r\n### Expected behavior\r\n\r\nHydration should complete normally and the screen should render correctly even after reloading.\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 13.2.1\r\n CPU: (12) arm64 Apple M2 Max\r\n Memory: 43.41 GB / 96.00 GB\r\n Shell: 3.6.1 - /opt/homebrew/bin/fish\r\n Binaries:\r\n Node: 20.16.0 - ~/.volta/tools/image/node/20.16.0/bin/node\r\n Yarn: 1.22.22 - ~/.volta/tools/image/yarn/1.22.22/bin/yarn\r\n npm: 10.8.1 - ~/.volta/tools/image/node/20.16.0/bin/npm\r\n pnpm: 9.7.1 - ~/.volta/tools/image/pnpm/9.7.1/bin/pnpm\r\n bun: 1.1.27 - ~/.bun/bin/bun\r\n Browsers:\r\n Chrome: 129.0.6668.70\r\n Safari: 16.3\r\n npmPackages:\r\n vitepress: ^1.3.4 => 1.3.4\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.",[],4231,"Hydration mismatch only occurs when reloading in the production build.","2024-10-05T04:43:33Z","https://github.com/vuejs/vitepress/issues/4231",0.69290125,{"description":2949,"labels":2950,"number":2952,"owner":2871,"repository":2872,"state":2906,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Describe the bug\n\nWhen the vertical scroll bar appears in some long content pages, the page width changes, which results in a bad user experience.\r\n\r\nMaybe add placeholder space for the scrollbar?\r\n\r\n\r\nhttps://github.com/user-attachments/assets/e43a537c-6e7c-4880-99bb-5c8ac7d39f2e\r\n\r\n\n\n### Reproduction\n\nhttps://vitepress.dev/reference/default-theme-carbon-ads\r\n\r\ncompare to \r\n\r\nhttps://vitepress.dev/reference/default-theme-search\r\n\n\n### Expected behavior\n\nthe content width don't be changed, which means the toc's and nav bar's position will not change.\n\n### System Info\n\n```Text\nall\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],{"name":2903,"color":2904},4215,"The page width be changed when y scrollbar appears cause bad ux","2024-09-27T04:43:38Z","https://github.com/vuejs/vitepress/issues/4215",0.6999678,{"description":2958,"labels":2959,"number":2967,"owner":2871,"repository":2872,"state":2906,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Describe the bug\n\nLandmarks should have a unique role or role/label/title (i.e. accessible name) combination\r\nCurrently, the nav at the bottom of the page containing \"prev\" and \"next\" links does not\r\nIt makes it hard for accessibility tools to understand the difference between this one and the main one\n\n### Reproduction\n\nNavigate to a doc page having \"prev\" or \"next\" navigation (or both) at the bottom\r\nInspect the accessibility of the nav component, it does not have an accessible name\r\n\r\nTriggers an error in Axe Devtools\n\n### Expected behavior\n\nShould have an accessible name to be distinct from main navigation (ideally, main navigation should have an accessible name too)\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 14.2.1\r\n CPU: (8) arm64 Apple M2\r\n Memory: 393.92 MB / 24.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.10.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /opt/homebrew/bin/yarn\r\n npm: 10.2.5 - /usr/local/bin/npm\r\n pnpm: 8.9.2 - /opt/homebrew/bin/pnpm\r\n Browsers:\r\n Safari: 17.2.1\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.31 => 1.0.0-rc.35\n```\n\n\n### Additional context\n\n\u003Cimg width=\"921\" alt=\"Screenshot 2024-01-29 at 15 49 37\" src=\"https://github.com/vuejs/vitepress/assets/58045985/546c396b-a86b-4550-8d35-9d75ba4d6c0d\">\r\n\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.",[2960,2963,2966],{"name":2961,"color":2962},"theme","0754FB",{"name":2964,"color":2965},"a11y","fbca04",{"name":2868,"color":2869},3516,"accessibility: prev / next navigation landmark does not have a unique name","2024-05-04T04:42:02Z","https://github.com/vuejs/vitepress/issues/3516",0.70963424,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fFFcx9z57Ne7WDQGt_y4JbQUA8NZir6xg6wk9KTmoSZw":-1},"/vuejs/vitepress/3422"]