```\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.7330063,{"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\nabout #3851 \n\n### Describe the solution you'd like\n\nThe usage of environment variables, such as `process.env.VITE_EXTRA_EXTENSIONS`, warrants a more detailed description in the official documentation.\r\n\r\nIf I haven't seen the source code, I wouldn't know that VITE_EXTRA_EXTENSIONS is a string that concatenates different words with commas.\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.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,2884],{"name":2882,"color":2883},"docs","0075ca",{"name":2868,"color":2869},3852,"Add docs regarding the environment vitepress used","2024-06-09T06:00:59Z","https://github.com/vuejs/vitepress/issues/3852",0.7461456,{"description":2891,"labels":2892,"number":2897,"owner":2871,"repository":2872,"state":2873,"title":2898,"updated_at":2899,"url":2900,"score":2901},"### 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.",[2893,2894],{"name":2868,"color":2869},{"name":2895,"color":2896},"perf","378A61",3509,"DOM is oversized","2025-03-02T18:09:47Z","https://github.com/vuejs/vitepress/issues/3509",0.748211,{"description":2903,"labels":2904,"number":2909,"owner":2871,"repository":2872,"state":2873,"title":2910,"updated_at":2911,"url":2912,"score":2913},"I hit another case of #449 by including the following in a markdown file. The workaround which linked to #662 worked for me. Perhaps this should be off by default? Or detect the compilation error and bring a suggestion? The XML I included seems pretty straightforward. Would have been very hard to diagnose if I hadn't been doing lots of searches against the issues here. \r\n\r\n```xml\r\n\u003Ckeyboard locale=\"mt\" conformsTo=\"techpreview\">\r\n \u003Ckeys>\r\n \u003Ckey id=\"hmaqtugha\" to=\"ħ\" />\r\n \u003Ckey id=\"that\" to=\"ថា\" />\r\n \u003C/keys>\r\n\r\n \u003Clayers form=\"hardware\">\r\n \u003Clayer id=\"base\">\r\n \u003Crow keys=\"hmaqtugha that\" />\r\n \u003C/layer>\r\n \u003C/layers>\r\n\r\n\u003C/keyboard>\r\n```\r\n\r\nSymptom is an error deep inside vue\r\n\r\n```\r\n5:26:34 PM [vitepress] Internal server error: Duplicate attribute.\r\n Plugin: vite:vue\r\n File: /Users/srl295/src/codehivetx.us/en/posts/2022-kbd-progress.md:22:69\r\n 22 | \u003Ckeys>\r\n 23 | \u003Ckey id=\"hmaqtugha\" to=\"ħ\" />\r\n 24 | \u003Ckey id=\"that\" to=\"ថា\" />\r\n | ^\r\n 25 | \u003C/keys>\r\n 26 | \r\n at createCompilerError (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-core/dist/compiler-core.cjs.js:1327:17)\r\n at emitError (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-core/dist/compiler-core.cjs.js:2805:5)\r\n at Object.onattribnameend (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-core/dist/compiler-core.cjs.js:2290:7)\r\n at Tokenizer.handleAttrNameEnd (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-core/dist/compiler-core.cjs.js:872:14)\r\n at Tokenizer.stateInAttrName (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-core/dist/compiler-core.cjs.js:812:12)\r\n at Tokenizer.parse (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-core/dist/compiler-core.cjs.js:1065:16)\r\n at Object.baseParse (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-core/dist/compiler-core.cjs.js:2844:13)\r\n at Object.parse (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-dom/dist/compiler-dom.cjs.js:698:23)\r\n at Object.parse$2 [as parse] (/Users/srl295/src/codehivetx.us/node_modules/@vue/compiler-sfc/dist/compiler-sfc.cjs.js:1846:24)\r\n at createDescriptor (file:///Users/srl295/src/codehivetx.us/node_modules/@vitejs/plugin-vue/dist/index.mjs:74:43) (x2)\r\n```\r\n",[2905,2908],{"name":2906,"color":2907},"build","377ba8",{"name":2868,"color":2869},3401,"better stack trace / error message for markdown-it-attrs failures","2025-03-02T18:10:00Z","https://github.com/vuejs/vitepress/issues/3401",0.76141965,{"description":2915,"labels":2916,"number":2921,"owner":2871,"repository":2872,"state":2873,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Is your feature request related to a problem? Please describe.\n\nIn the monorepo development mode, sometimes the rendering in docs depends on the code in another repository, so when the code in another repository changes, it is expected to trigger a hot reload of docs\n\n### Describe the solution you'd like\n\nSupport configuration to watch specified folders to trigger hot reload\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.",[2917,2920],{"name":2918,"color":2919},"need more info","bdbefc",{"name":2868,"color":2869},4221,"Support hot reload by watching files not under docs","2024-12-03T17:27:50Z","https://github.com/vuejs/vitepress/issues/4221",0.762115,{"description":2927,"labels":2928,"number":2929,"owner":2871,"repository":2872,"state":2930,"title":2931,"updated_at":2932,"url":2933,"score":2934},"### 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.6726177,{"description":2936,"labels":2937,"number":2941,"owner":2871,"repository":2872,"state":2930,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Describe the bug\r\n\r\nYou can check Reproduction Url test.\r\n\r\nEverything works fine when I start the vite project(`apps/playground`) using `pnpm dev:playground`. It crashed when I started vitepress project(`apps/document`) using `pnpm dev:document`.\r\n\r\nMy monorepo project uses `node condition` to link the source code. You can check the `dev` field in `package.json` or `condition: [\"dev\"]` in `vite.config.ts` or `condition: [\"dev\"]` in `config.ts`.\r\n\r\n### Reproduction\r\n\r\nhttps://github.com/i7eo/monorepo-vitepress-bug-report\r\n\r\n### Expected behavior\r\n\r\nStart normally like a vite project(`apps/playground`)\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 14.4.1\r\n CPU: (10) arm64 Apple M1 Max\r\n Memory: 3.61 GB / 64.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.12.2 - ~/.nvm/versions/node/v20.12.2/bin/node\r\n npm: 10.5.0 - ~/.nvm/versions/node/v20.12.2/bin/npm\r\n pnpm: 9.1.0 - ~/.nvm/versions/node/v20.12.2/bin/pnpm\r\n Watchman: 2024.04.08.00 - /opt/homebrew/bin/watchman\r\n Browsers:\r\n Chrome: 124.0.6367.201\r\n Safari: 17.4.1\r\n Safari Technology Preview: 17.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.",[2938],{"name":2939,"color":2940},"bug: pending triage","e99695",3888,"Vitepress project in monorepo reports `Failed to resolve import \"xxx\"`","2024-05-22T04:41:52Z","https://github.com/vuejs/vitepress/issues/3888",0.7137422,{"description":2947,"labels":2948,"number":2951,"owner":2871,"repository":2872,"state":2930,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Describe the bug\n\nI am using a markdown-it plugin to add classes to `\u003Ctable>` tags. This was broken by #3932.\r\n\r\nIf you look at: https://github.com/vuejs/vitepress/pull/3932/files#diff-332834eb76757b8e31926e411cef34f7207564d0bf5fd00a185b41d97b3403bf\r\n```\r\n md.renderer.rules.table_open = function (tokens, idx, options, env, self) {\r\n return '\u003Ctable tabindex=\"0\">\\n'\r\n }\r\n```\r\n\r\nThis breaks the chaining of any other modifications to the table_open rule. My understanding is that you should use the methods on token to modify the token and then chain to the existing rule. This post has a decent description: https://publishing-project.rivendellweb.net/customizing-markdown-it/#adding-classes-to-list-and-list-items\r\n\r\nIt looks like the overriding of `math_blocks` further down in the file _does_ chain the original renderer.\n\n### Reproduction\n\nIn `config.mts`\r\n\r\n```\r\nimport markdownItClass from '@toycode/markdown-it-class'\r\n...\r\nexport default defineConfig({\r\n...\r\n markdown: {\r\n config: (md) => {\r\n md.use(markdownItClass, {table: ['table', 'table-striped']})\r\n },\r\n },\r\n})\r\n```\r\n\n\n### Expected behavior\n\nvitepress markdown.it plugin doesn't break other markdown.it plugin\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 11 10.0.22631\r\n CPU: (16) x64 Intel(R) Core(TM) i9-10885H CPU @ 2.40GHz\r\n Memory: 9.01 GB / 31.75 GB\r\n Binaries:\r\n Node: 20.16.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 10.8.1 - C:\\Program Files\\nodejs\\npm.CMD\r\n pnpm: 9.5.0 - C:\\Program Files\\nodejs\\pnpm.CMD\r\n Browsers:\r\n Edge: Chromium (127.0.2651.74)\r\n Internet Explorer: 11.0.22621.3527\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.",[2949,2950],{"name":2906,"color":2907},{"name":2868,"color":2869},4239,"Regression: #3932 breaks chaining of table_open markdown.it rules ","2025-03-16T04:43:43Z","https://github.com/vuejs/vitepress/issues/4239",0.7233831,{"description":2957,"labels":2958,"number":2961,"owner":2871,"repository":2872,"state":2930,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Describe the bug\r\n\r\nSimilar to https://github.com/vuejs/vitepress/issues/849\r\n\r\nVitepress imports `body-scroll-lock` and `@vueuse/core` from the app, rather than from vitepress (which declares the dependency).\r\n\r\nThis is a problem then modules are resolved with pnpm or Yarn which do not allow for resolution of hoisted node_modules. This has historically been not affected Vite because it would ignore the importing context when resolving dependencies (which is fixed in https://github.com/vitejs/vite/pull/9763)\r\n\r\n### Reproduction\r\n\r\nUse https://github.com/vitejs/vite/pull/9763 for Vite when using Vitepress\r\n\r\n### Expected behavior\r\n\r\nVitepress should instead import and/or resolve `body-scroll-lock` and `@vueuse/core` from Vitepress itself rather than the host app (which probably does not declare dependencies on `body-scroll-lock` and `@vueuse/core`.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 13.3\r\n CPU: (10) arm64 Apple M1 Max\r\n Memory: 18.95 GB / 64.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 18.6.0 - ~/Library/Caches/fnm_multishells/12267_1680539322066/bin/node\r\n npm: 8.13.2 - /opt/uber/bin/npm\r\n Browsers:\r\n Chrome: 111.0.5563.146\r\n Safari: 16.4\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.61 => 1.0.0-alpha.61\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.dev).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2959,2960],{"name":2939,"color":2940},{"name":2868,"color":2869},2187,"Vitepress relies on node_modules hoisting for body-scroll-lock and @vueuse/core","2023-08-14T00:04:20Z","https://github.com/vuejs/vitepress/issues/2187",0.72502846,{"description":2967,"labels":2968,"number":2969,"owner":2871,"repository":2872,"state":2930,"title":2970,"updated_at":2971,"url":2972,"score":2973},"### Describe the bug\n\nClick on the search box and the page will look right offset,This problem also exists in Vue,This is caused by the scroll bar on the right。\n\n### Reproduction\n\nClick on the search box.\n\n### Expected behavior\n\nClick the search box, the page does not offset\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.",[],3589,"searchbox","2024-03-24T00:05:34Z","https://github.com/vuejs/vitepress/issues/3589",0.7510914,["Reactive",2975],{},["Set"],["ShallowReactive",2978],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fwgOno3lUg9GqPJJLptBRtNH3zTeeQQdUCwe0hHIONvY":-1},"/vuejs/vitepress/4009"]