```\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.64075917,{"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\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.",[2881,2884],{"name":2882,"color":2883},"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.67158246,{"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.7045091,{"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.7053191,{"description":2915,"labels":2916,"number":2921,"owner":2871,"repository":2872,"state":2873,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Describe the bug\n\n这个情况从中文用户使用中发现,也可能广泛存在于非英语键盘的用户中。输入关键字过程中,尝试给出的结果会中断拼写。\n\n### Reproduction\n\n1. 进入Vitrepress文档首页 https://vitepress.dev/zh/\r\n2. 触发打开搜索框\r\n3. 使用“微软输入法”并尝试**缓慢输入**`复用`,即按顺序输入`f`-`u`-`y`-`o`-`n`-`g`\n\n### Expected behavior\n\n希望能够顺畅的完成关键字输入\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.22631\r\n CPU: (16) x64 AMD Ryzen 7 6800H with Radeon Graphics\r\n Memory: 44.07 GB / 63.18 GB\r\n Binaries:\r\n Node: 20.10.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 10.2.5 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Chromium (121.0.2277.128)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: 1.0.0-rc.44 => 1.0.0-rc.44\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.",[2917,2920],{"name":2918,"color":2919},"upstream","BF29ED",{"name":2868,"color":2869},3604,"algolia搜索框在输入关键字时会中断输入法拼写","2024-04-12T01:59:21Z","https://github.com/vuejs/vitepress/issues/3604",0.7177011,{"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\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,"closed","searchbox","2024-03-24T00:05:34Z","https://github.com/vuejs/vitepress/issues/3589",0.6686367,{"description":2936,"labels":2937,"number":2940,"owner":2871,"repository":2872,"state":2930,"title":2941,"updated_at":2942,"url":2943,"score":2944},"### 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.",[2938,2939],{"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.6958084,{"description":2946,"labels":2947,"number":2951,"owner":2871,"repository":2872,"state":2930,"title":2952,"updated_at":2953,"url":2954,"score":2955},"### Describe the bug\n\nI installed Vitepress, built then ran it locally following the documentation of Vercel and everything seemed fine. But when I deployed it to my personal Vercel, my site keeps loading the 404.html. When I visit the Output of Vercel, I couldn't find any index.html and only 404.html. \r\n\r\nHere is currently [the blog of mine](https://vitepress-doc-kappa.vercel.app/) that I deployed to Vercel.\r\n\r\nThis is my current source on Vercel:\r\n\r\n\r\nThis is my current output on Vercel:\r\n\r\n\r\n\n\n### Reproduction\n\nNot sure if this is the correct way to reproduce, but I'll list down the commands that I ran, from install command to deploy:\r\n\r\n```bash\r\nnpm add -D vitepress\r\nnpx vitepress init ./\r\nnpm run docs:build\r\nnpm run docs:preview\r\nvercel --prod\r\n```\n\n### Expected behavior\n\nPage should load index.html when visiting `/`.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19043\r\n CPU: (4) x64 Intel(R) Pentium(R) CPU G4560 @ 3.50GHz\r\n Memory: 2.27 GB / 7.96 GB\r\n Binaries:\r\n Node: 20.0.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 9.6.4 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (120.0.2210.133)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.39 => 1.0.0-rc.39\n```\n\n\n### Additional context\n\nI use a fresh setup of Vitepress and deploy to a Vercel setting using Node v20.x (which as mentioned on Vercel that is still in Beta). However I did try Node v18.x on Vercel and the error is the same. \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.",[2948],{"name":2949,"color":2950},"bug: pending triage","e99695",3460,"Site auto loads 404.html after deployed to Vercel","2024-01-24T00:04:46Z","https://github.com/vuejs/vitepress/issues/3460",0.7055607,{"description":2957,"labels":2958,"number":2962,"owner":2871,"repository":2872,"state":2930,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### 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.",[2959],{"name":2960,"color":2961},"need more info","bdbefc",3632,"inline html transform error","2024-04-28T12:27:40Z","https://github.com/vuejs/vitepress/issues/3632",0.7095051,{"description":2968,"labels":2969,"number":2971,"owner":2871,"repository":2872,"state":2930,"title":2972,"updated_at":2973,"url":2974,"score":2975},"### 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.",[2970],{"name":2949,"color":2950},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.7113454,["Reactive",2977],{},["Set"],["ShallowReactive",2980],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fC1aClFk9L1uBdxondi5oyAArMBKnk8UTvWEHforY_tc":-1},"/vuejs/vitepress/4468"]