```\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.7100558,{"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.7361312,{"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\nI'd like to wrap code/fence blocks in vue components without button and language span.\r\nCurrently vitepress forces wrapping with this:\r\nhttps://github.com/vuejs/vitepress/blob/9b1bb4ffc6423ef0f16a213133980fdb6e9bf552/src/node/markdown/markdown.ts#L223\r\n\n\n### Describe the solution you'd like\n\nOffer some options for disabling preWrapperPlugin, or overriding it.\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.",[2893],{"name":2868,"color":2869},4039,"Optionally disable or override preWrapper for fence blocks","2025-03-02T18:09:00Z","https://github.com/vuejs/vitepress/issues/4039",0.7474737,{"description":2900,"labels":2901,"number":2906,"owner":2871,"repository":2872,"state":2873,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### Describe the bug\n\nWhen using a computed value as a prop, that value is only applied once at build, it's not changed during pageload if it differs.\r\n\r\nFor example, when using a computed value to determine the current theme, this will be lightmode on the server, but the user may have dark mode set in their preferences.\r\n\r\nThe `isDark` composable then returns `dark` on the user's machine, but the static HTML has `light` bound to it, and that doesn't change until the `isDark` composable changes state again.\n\n### Reproduction\n\nWebsite: https://lenni009.github.io/vitepress-computed-bug/\r\n\r\nMinimal repo with component: https://github.com/Lenni009/vitepress-computed-bug/blob/main/index.md?plain=1\n\n### Expected behavior\n\nThe application state should be applied to the HTML at pageload, so there are no mismatches.\r\n\r\nIn this case, the text background should be black if the user prefers dark.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz\r\n Memory: 5.45 GB / 15.96 GB\r\n Binaries:\r\n Node: 20.11.1 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 10.3.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 123.0.6312.59\r\n Edge: Chromium (123.0.2420.53)\r\n Internet Explorer: 11.0.19041.3636\r\n npmPackages:\r\n vitepress: ^1.0.1 => 1.0.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.",[2902,2905],{"name":2903,"color":2904},"upstream","BF29ED",{"name":2868,"color":2869},3699,"Computed prop is not changed on pageload","2025-03-02T18:09:30Z","https://github.com/vuejs/vitepress/issues/3699",0.75056446,{"description":2912,"labels":2913,"number":2914,"owner":2871,"repository":2872,"state":2915,"title":2916,"updated_at":2917,"url":2918,"score":2919},"### Describe the bug\n\nVitePress ignores the `vite.clearScreen: false` option - running `vitepress build` will clear the screen regardless.\r\n\r\nThis is causing issues in our turbo build monorepo - when building several packages at once, VitePress's clear screen clears the log output for packages that were built before it.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-dtu41vnr?file=package.json\r\n\r\n1. Install dependencies\r\n2. Run `npx vitepress build docs`\r\n3. See that screen is cleared, despite vite.clearScreen:false in docs/.vitepress/config.ts\n\n### Expected behavior\n\nScreen should not be cleared if vite.clearScreen:false is set\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 15.2\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 78.41 MB / 32.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 22.12.0 - ~/.local/state/fnm_multishells/64248_1736184870871/bin/node\r\n Yarn: 1.22.19 - ~/.local/state/fnm_multishells/64248_1736184870871/bin/yarn\r\n npm: 10.9.0 - ~/.local/state/fnm_multishells/64248_1736184870871/bin/npm\r\n Browsers:\r\n Chrome: 131.0.6778.205\r\n Safari: 18.2\r\n npmPackages:\r\n vitepress: 1.5.0 => 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.",[],4468,"closed","`vite.clearScreen: false` option is ignorred","2025-01-14T04:42:24Z","https://github.com/vuejs/vitepress/issues/4468",0.71457785,{"description":2921,"labels":2922,"number":2923,"owner":2871,"repository":2872,"state":2915,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### 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.7231008,{"description":2929,"labels":2930,"number":2934,"owner":2871,"repository":2872,"state":2915,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### 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.",[2931],{"name":2932,"color":2933},"bug: pending triage","e99695",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.72649205,{"description":2940,"labels":2941,"number":2943,"owner":2871,"repository":2872,"state":2915,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Describe the bug\n\n文章目录不显示一级标题\n\n### Reproduction\n\n```mts\r\nimport {withMermaid} from \"vitepress-plugin-mermaid\";\r\n// https://emersonbottero.github.io/vitepress-plugin-mermaid/guide/getting-started.html\r\n// https://vitepress.dev/reference/site-config\r\nimport {generateSidebar} from 'vitepress-sidebar';\r\n\r\nexport default withMermaid({\r\n title: \"DMP-Docs\",\r\n description: \"DMP-Docs\",\r\n themeConfig: {\r\n // https://vitepress.dev/reference/default-theme-config\r\n nav: [\r\n {text: 'Home', link: '/'},\r\n ],\r\n\r\n search: {\r\n provider: 'local'\r\n },\r\n sidebar: generateSidebar({\r\n documentRootPath: '/docs',\r\n }),\r\n socialLinks: [\r\n {icon: 'github', link: 'http://10.186.18.21/dmp-dev-newbie/caomingkang/DMP-DOC'}\r\n ],\r\n\r\n outline: 'deep'\r\n },\r\n // optionally, you can pass MermaidConfig\r\n mermaid: {\r\n // refer https://mermaid.js.org/config/setup/modules/mermaidAPI.html#mermaidapi-configuration-defaults for options\r\n },\r\n // optionally set additional config for plugin itself with MermaidPluginConfig\r\n mermaidPlugin: {\r\n class: \"mermaid my-class\", // set additional css classes for parent container\r\n },\r\n\r\n})\r\n\r\n\r\n\r\n\r\n\r\n\r\n```\n\n### Expected behavior\n\n显示一级目录导航\n\n### System Info\n\n```Text\nmacos 13\r\n \"vitepress\": \"^1.0.0-rc.29\",\n```\n\n\n### Additional context\n\n\u003Cimg width=\"1159\" alt=\"Xnip2023-11-22_18-52-26\" src=\"https://github.com/vuejs/vitepress/assets/55651847/e1924277-32d5-45bb-a609-763b0e672075\">\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.",[2942],{"name":2932,"color":2933},3234,"文章目录不显示一级标题","2023-12-01T00:05:07Z","https://github.com/vuejs/vitepress/issues/3234",0.73175573,{"description":2949,"labels":2950,"number":2952,"owner":2871,"repository":2872,"state":2915,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Is your feature request related to a problem? Please describe.\n\nGitHub introduced a syntax to have alerts: https://github.com/orgs/community/discussions/16925\r\n\r\nBasically, it's:\r\n\r\n```\r\n> [!NOTE] \r\n> Highlights information that users should take into account, even when skimming.\r\n\r\n> [!TIP]\r\n> Optional information to help a user be more successful.\r\n\r\n> [!IMPORTANT] \r\n> Crucial information necessary for users to succeed.\r\n\r\n> [!WARNING] \r\n> Critical content demanding immediate user attention due to potential risks.\r\n\r\n> [!CAUTION]\r\n> Negative potential consequences of an action.\r\n```\r\n\r\n> [!NOTE] \r\n> Highlights information that users should take into account, even when skimming.\r\n\r\n> [!TIP]\r\n> Optional information to help a user be more successful.\r\n\r\n> [!IMPORTANT] \r\n> Crucial information necessary for users to succeed.\r\n\r\n> [!WARNING] \r\n> Critical content demanding immediate user attention due to potential risks.\r\n\r\n> [!CAUTION]\r\n> Negative potential consequences of an action.\n\n### Describe the solution you'd like\n\nI think it would be nice for VitePress to support that built-in. So markdown files authored that way can have a closer experience when reading on GitHub.\r\n\r\nI wrote a markdown-it plugin for that: https://github.com/antfu/markdown-it-github-alerts that VitePress might be able to use directly. (and also a short intro and preview on my site: https://antfu.me/posts/github-alerts)\r\n\r\nI guess we don't need to align exactly the same as GitHub's styling. We could just render our existing alerts.\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.",[2951],{"name":2868,"color":2869},3278,"Support GitHub-style Alert?","2024-01-29T00:04:26Z","https://github.com/vuejs/vitepress/issues/3278",0.73461574,{"description":2958,"labels":2959,"number":2966,"owner":2871,"repository":2872,"state":2915,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Describe the bug\r\n\r\nDocs navigation is inconsistent.\r\nWhile reading **Guide**, you land at https://vitepress.dev/guide/what-is-vitepress.\r\nOpening https://vitepress.dev/guide brings to error 404 page.\r\n\r\n\r\n### Reproduction\r\n\r\n1. Browse: homepage\r\n2. Click link: Guide\r\n3. See: What is vitepress\r\n4. Edit url: \"/guide/what-is-vitepress\" to \"/guide\"\r\n5. See: Error 404\r\n\r\n### Expected behavior\r\n\r\nParent container routing page should be a container of chapters\r\n\r\n- Introduction\r\n- Writing\r\n- Customization\r\n- Experimental\r\n\r\nEach chapter should have an excerpt of the content, its page links either.\r\n\r\nIf \"it's too much\", `/guide` should simply redirect to default landing page `/guide/what-is-vitepress`\r\n\r\n### System Info\r\n\r\n```Text\r\nNot a software bug, docs navigation related.\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.",[2960,2963],{"name":2961,"color":2962},"docs","0075ca",{"name":2964,"color":2965},"has-workaround","1B4515",4233,"Docs: /guide path is missing (error 404)","2024-10-20T04:43:29Z","https://github.com/vuejs/vitepress/issues/4233",0.73634934,["Reactive",2972],{},["Set"],["ShallowReactive",2975],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fP1ghwNL9j0mn-2sljA2uBzLl9Pe67ftjd8TLu_dbXkA":-1},"/vuejs/vitepress/3604"]