```\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.6865836,{"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.7113885,{"description":2891,"labels":2892,"number":2897,"owner":2871,"repository":2872,"state":2873,"title":2898,"updated_at":2899,"url":2900,"score":2901},"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",[2893,2896],{"name":2894,"color":2895},"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.71680474,{"description":2903,"labels":2904,"number":2909,"owner":2871,"repository":2872,"state":2873,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Is your feature request related to a problem? Please describe.\n\nDuring build (or CI) process, external links should be checked for validity.\r\n\r\nCurrently, VP only checks localhost links. Other external links are just added as-is to the page. See https://github.com/vuejs/vitepress/blob/d837e82bc8bde63df737be2a1290a2e70c8a0bf3/src/node/markdown/plugins/link.ts#L39\n\n### Describe the solution you'd like\n\nAt a minimum, ignoreDeadLinks callback option should be extended to return ALL links seen during parsing. VP admin can then write their own logic to do link checking.\r\n\r\nExample:\r\n\r\n```\r\nignoreDeadLinks: [\r\n (url) => {\r\n if (external_URL) {\r\n // Do link checking, i.e. with 'link-check' npm package\r\n } elseif (localhost_URL) {\r\n // Handle localhost checking.\r\n }\r\n }\r\n],\r\n``` \r\n\r\nEven better would be a way to continue to allow VP to handle localhost link checking and provide an option to handle external links separately.\r\n\r\nEven even better might be that external link checking is simply built-in to VP, as an option. (E.g., Sphinx has this ability.). Simple example:\r\n\r\n```\r\nimport 'linkCheck' from 'link-check'\r\n\r\n// ...\r\n\r\nlinkCheck(url_to_check, function (err, result) {\r\n if (err) {\r\n throw new Error('Invalid Link: ' + err)\r\n }\r\n});\r\n```\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\nMore than willing to provide an MR to accomplish this, but since there are so many possibilities on how to allow/enable this I would rather wait for developer input to direct towards the best solution.\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.",[2905,2908],{"name":2906,"color":2907},"has-workaround","1B4515",{"name":2868,"color":2869},4009,"Enabling External Link Validity Checking","2025-03-02T18:09:01Z","https://github.com/vuejs/vitepress/issues/4009",0.7207124,{"description":2915,"labels":2916,"number":2918,"owner":2871,"repository":2872,"state":2873,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Is your feature request related to a problem? Please describe.\n\nAfter the colour system has been improved, I find it harder to find the colour for both dark and light modes.\r\n\r\nIs there any recommended generator that fits the VitePress colour system? At this stage, all I need is the 3 brand colours.\n\n### Describe the solution you'd like\n\nN/A\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],{"name":2868,"color":2869},3212,"Color generator","2023-12-26T20:33:04Z","https://github.com/vuejs/vitepress/issues/3212",0.7360548,{"description":2924,"labels":2925,"number":2927,"owner":2871,"repository":2872,"state":2873,"title":2928,"updated_at":2929,"url":2930,"score":2931},"### Is your feature request related to a problem? Please describe.\n\nI am always frustrated when searching for related content across the site.\n\n### Describe the solution you'd like\n\nIt might be a great idea to have some kind of tag system very much like the way a hashtag works, where you can set the tags in the frontmatter and the vitepress tool would automatically inject those tags at the top of the page or the bottom of the page. These tags would then become searchable via the built-in search tool or you could have a list of tags in the sidebar appear, so when you click on a tag it will display or the related content that is associated to that tag.\n\n### Describe alternatives you've considered\n\nI have not tried any alternatives, I believe that Vitepress does not provide an alternative solution.\n\n### Additional context\n\nI am building a resource for making the law more approachable and accessible to the everyday South African called lawforidiots.org, I have realized that the way that i intend for the content to be laid out would require some kind of tagging system because there will eventually be a lot of content that is related overtime. Therefore, a tagging system would be the best way to go. I see there is another ticket https://github.com/vuejs/vitepress/issues/3029 but I thought I would create a duplicate just for more context on the matter\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":2868,"color":2869},3254,"Searchable tags","2025-03-02T18:10:16Z","https://github.com/vuejs/vitepress/issues/3254",0.7405564,{"description":2933,"labels":2934,"number":2935,"owner":2871,"repository":2872,"state":2936,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Describe the bug\n\nA markdown file with several dots `.` such as `software-1.2.3.md` is not properly routed and leads to a 404 error.\r\nI guess that the router assumes that there is a file named `/software-1.2.3` with the `.3` extension when using cleanUrls.\n\n### Reproduction\n\n1. Create a new VitePress project\r\n2. Create a new markdown file named `software-1.2.3.md` with some content.\r\n3. Create links the `/software-1.2.3` page in the `index.md` file. \r\n```md\r\n[/software-1.2.3](/software-1.2.3)\r\n[/software-1.2.3.md](/software-1.2.3.md)\r\n``` \r\n5. Enable `cleanUrls`.\r\n6. Click the links on the index page.\n\n### Expected behavior\n\nThe router should load the page `/software-1.2.3` when cleanUrls are active.\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 11.7.10\r\n CPU: (4) x64 Intel(R) Core(TM) i5-4258U CPU @ 2.40GHz\r\n Memory: 85.34 MB / 8.00 GB\r\n Shell: 3.2.57 - /bin/bash\r\n Binaries:\r\n Node: 18.13.0 - /usr/local/bin/node\r\n npm: 9.8.1 - /usr/local/bin/npm\r\n pnpm: 8.9.1 - /usr/local/bin/pnpm\r\n Browsers:\r\n Chrome: 118.0.5993.117\r\n Safari: 16.6.1\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.25 => 1.0.0-rc.25\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.",[],3191,"closed","Markdown files with several dots `.` in name are not routed","2023-11-26T00:04:52Z","https://github.com/vuejs/vitepress/issues/3191",0.69025457,{"description":2942,"labels":2943,"number":2947,"owner":2871,"repository":2872,"state":2936,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Describe the bug\n\nThe external link in siderbar seems not work.\r\n\r\nWhen I click the MarkdownCanDo button, the website jumps to `https://www.gantrol.com/en/software/https:/www.markdowncando.com/` instead of `https://www.markdowncando.com/`\r\n\r\n\r\n\n\n### Reproduction\n\nI write [a blog website](https://www.gantrol.com/en/CS/examples) with vitepress ([github](https://github.com/gantrol/gantrol-blog))\r\n\n\n### Expected behavior\n\nHere is a PR that describes the feature, https://github.com/vuejs/vitepress/pull/1881\n\n### System Info\n\n```Text\n\"vitepress\": \"1.0.0-rc.45\"\r\n\r\n[config file](https://github.com/gantrol/gantrol-blog/blob/main/.vitepress/config/en.ts)\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.",[2944],{"name":2945,"color":2946},"bug: pending triage","e99695",3656,"Can sidebar has external links?","2024-03-22T00:04:26Z","https://github.com/vuejs/vitepress/issues/3656",0.6971412,{"description":2953,"labels":2954,"number":2955,"owner":2871,"repository":2872,"state":2936,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### 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,"`vite.clearScreen: false` option is ignorred","2025-01-14T04:42:24Z","https://github.com/vuejs/vitepress/issues/4468",0.6980286,{"description":2961,"labels":2962,"number":2966,"owner":2871,"repository":2872,"state":2936,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Describe the bug\n\nA custom font-face [was added to VitePress](https://github.com/vuejs/vitepress/commit/81ae1c79cd1c0c9c31f48100f131715efc68efbd) to fix rendering issues for quotes in Chinese, but this has inadvertently caused rendering issues in English (and possibly other languages).\r\n\r\nCurly apostrophes are particularly affected as `Can’t` turns into `Can’ t`, because the spacing of the apostrophe is much larger in some Chinese fonts. This happens on systems that default to the SimHei local font and possibly others.\n\n### Reproduction\n\nAdd curly quotes between letters (or enable `typographer` for Markdown)\r\n\r\nhttps://stackblitz.com/edit/vite-jhejpq?file=docs%2Findex.md,docs%2F.vitepress%2Fconfig.ts\r\n\r\nBut it will only reproduce when the system defaults to the SimHei font (Windows I think). \r\n\r\n\r\n\n\n### Expected behavior\n\nCurly quotes should not take any extra space than needed.\n\n### System Info\n\n```Text\nReproduced on Windows systems where the local font used is SimHei.\n```\n\n\n### Additional context\n\nI assume reverting this behaviour would negatively affect Chinese users, so I'll leave it to the discretion of the maintainers as to whether it should be reverted or not. It was very difficult to identify the problem though, so documenting it would at least be helpful so other users know to override the behaviour themselves.\r\n\r\nManually overriding `--vp-font-family-base` is a workaround.\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.",[2963],{"name":2964,"color":2965},"theme","0754FB",3790,"Font face 'Chinese Quotes' causes extra space between English letters","2024-05-05T04:41:52Z","https://github.com/vuejs/vitepress/issues/3790",0.70404494,["Reactive",2972],{},["Set"],["ShallowReactive",2975],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fW0x76rtF1Q3sQ1l4_wQ3862L1t1Eocwk7yyNZAdP-Zo":-1},"/vuejs/vitepress/4239"]