```\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",[3045],{"name":3020,"color":3021},4273,"How to use default Vue components elsewhere","2024-12-03T17:27:39Z","https://github.com/vuejs/vitepress/issues/4273",0.6899167,{"description":3052,"labels":3053,"number":3058,"owner":3023,"repository":3024,"state":3025,"title":3059,"updated_at":3060,"url":3061,"score":3062},"### Describe the bug\r\n\r\n```md\r\n## Powered by Vite \u003CBadge>HERE\u003C/Badge>\r\n```\r\n\r\nThis header\r\n\r\n1. is not properly slugified (expected `powered-by-vite`, actual `powered-by-vite-here`),\r\n2. and cannot be configurated to be properly slugified.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-hnczhc\r\n\r\nor the official doc: https://vitepress.dev/reference/default-theme-badge#title-custom-element ← see this anchor\r\n\r\n### Expected behavior\r\n\r\n1. The header should be slugified without badge children (if I use props instead, it is slugified as expected, but I cannot do so).\r\n2. I use the following config to make it look better:\r\n\r\n```ts\r\n markdown: {\r\n anchor: {\r\n slugify: (str) => slugify(str.replace(/ *\u003Cbadge.+/i, '')),\r\n },\r\n },\r\n```\r\n\r\nIt is working alright in the past, but not working for now. Actually the `str` received is `Powered by Vite HERE`, without tag information.\r\n\r\nI believe this is a regression from vitepress or mdit-vue.\r\n\r\n\r\n### System Info\r\n\r\n```Text\r\nN/A\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n**Why don't you use props instead of children?**\r\n\r\nBecause this is an i18n doc site. The children can be translated via Crowdin, but props cannot.\r\n\r\nWith such inconsistencies, at least I don't think the designers of the badge component fully considered the i18n experience. Vitepress is an excellent project and I hope it gets better.\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.",[3054,3057],{"name":3055,"color":3056},"build","377ba8",{"name":3020,"color":3021},3511,"Bug: cannot properly slugify badge with children","2025-03-02T18:09:46Z","https://github.com/vuejs/vitepress/issues/3511",0.6974195,{"description":3064,"labels":3065,"number":3070,"owner":3023,"repository":3024,"state":3025,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Is your feature request related to a problem? Please describe.\r\n\r\nI would like to show a text in the footer like:\r\n\r\n`Edited at ${updatedAt} (${commitHash})`.\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\n`updatedAt` is being fetched from this [`getGitTimestamp`](https://github.com/vuejs/vitepress/blob/4c2300318952bfdaabd766a6f16f26419ee854da/src/node/utils/getGitTimestamp.ts#L4) function.\r\n\r\nI would like to propose a new function called `getCommitHash` function which also receives a `file: string` as an argument called `updatedCommitHash` and then add it to the [`page` type](https://github.com/vuejs/vitepress/blob/54042ef5760e0af5590b616d909e7f23effedc22/types/shared.d.ts#L8-L19)\r\n\r\n### Describe alternatives you've considered\r\n\r\nI am going to built this code for my own `vitepress` project, but I think it might be beneficial for other pepole.\r\n\r\n### Additional context\r\n\r\nI would like to make a PR if we agree this is a good thing to add to `vitepress`. \r\n\r\nFirst, I would like to hear an OK from the maintainers. \r\n\r\nPD: Suggest better names as I think my proposed names are not very descriptive 😄 \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] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\r\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[3066,3069],{"name":3067,"color":3068},"has-workaround","1B4515",{"name":3020,"color":3021},3520,"Add `updatedCommitHash` to the `page` object","2025-03-02T18:09:45Z","https://github.com/vuejs/vitepress/issues/3520",0.70380336,{"description":3076,"labels":3077,"number":3082,"owner":3023,"repository":3024,"state":3025,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Is your feature request related to a problem? Please describe.\n\nIt is not related to a direct problem that I have but instead a feature that I would be a great addition to the overall documentation experience that Vitepress provides,\n\n### Describe the solution you'd like\n\nIt would be great if the links that we embed into a page would have some kind of preview popup that gets displayed to the user via the use of an iframe or simply using the open graph protocol. Similar to what Trello does here \r\n\u003Cimg width=\"617\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/26552540/8c86f966-1edb-4ac6-8fe4-8cd17e7a5467\">\r\n As you can see, when I hover over the link a preview is displayed to the user with information regarding the link, it could be through an iframe open graph or both.\n\n### Describe alternatives you've considered\n\nI have not considered any alternatives because I believe that non exist that fulfil the idea that I have in mind\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.",[3078,3081],{"name":3079,"color":3080},"theme","0754FB",{"name":3020,"color":3021},3263,"Link previews","2025-03-02T18:10:14Z","https://github.com/vuejs/vitepress/issues/3263",0.7046286,{"description":3088,"labels":3089,"number":3095,"owner":3023,"repository":3024,"state":3025,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### Describe the bug\n\n\r\n\r\nOpen the image in a new page and zoom in, you will see the transparency causes the overlaying lines of the letters to be visible and this makes things to look ugly.on\n\n### Reproduction\n\n1. You can use this font to test things out: https://fonts.google.com/specimen/Vazirmatn\r\n2. Change the font-family to this ^^^ font.\r\n3. Change to dark mode.\r\n4. Use this text: `اعتبارسنجی اسکیما تایپاسکریپت-اول`\r\n5. Zoom and you can see it too.\n\n### Expected behavior\n\nSo the overlaying paths/lines are not visible.\n\n### System Info\n\n```Text\n.\n```\n\n\n### Additional context\n\nI think this doesn't happen with all Farsi/Persian fonts, but it's something that happens very often.\r\n\r\nThe only solution is to not use opacity with text content.\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.",[3090,3091,3094],{"name":3079,"color":3080},{"name":3092,"color":3093},"a11y","fbca04",{"name":3020,"color":3021},3313,"Consider not using opacity for any text content","2024-05-23T19:48:59Z","https://github.com/vuejs/vitepress/issues/3313",0.7069564,{"description":3101,"labels":3102,"number":3106,"owner":3023,"repository":3024,"state":3107,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### 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.",[3103],{"name":3104,"color":3105},"bug: pending triage","e99695",4215,"closed","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.5909757,{"description":3113,"labels":3114,"number":3116,"owner":3023,"repository":3024,"state":3107,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### 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.",[3115],{"name":3104,"color":3105},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.6670875,{"description":3122,"labels":3123,"number":3125,"owner":3023,"repository":3024,"state":3107,"title":3126,"updated_at":3127,"url":3128,"score":3129},"### 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.",[3124],{"name":3104,"color":3105},3460,"Site auto loads 404.html after deployed to Vercel","2024-01-24T00:04:46Z","https://github.com/vuejs/vitepress/issues/3460",0.6683632,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f3D46IUDA4rkq5gn27q0nE20JU3XdiemHpDhv5meeJWY":-1},"/vuejs/vitepress/4288"]