\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.",[2922],{"name":2923,"color":2924},"need more info","bdbefc",3632,"inline html transform error","2024-04-28T12:27:40Z","https://github.com/vuejs/vitepress/issues/3632",0.64719605,{"description":2931,"labels":2932,"number":2934,"owner":2863,"repository":2864,"state":2895,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### 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.",[2933],{"name":2912,"color":2913},3460,"Site auto loads 404.html after deployed to Vercel","2024-01-24T00:04:46Z","https://github.com/vuejs/vitepress/issues/3460",0.6582172,{"description":2940,"labels":2941,"number":2943,"owner":2863,"repository":2864,"state":2895,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### 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.",[2942],{"name":2912,"color":2913},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.66146487,{"description":2949,"labels":2950,"number":2952,"owner":2863,"repository":2864,"state":2895,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### 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.",[2951],{"name":2912,"color":2913},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.6712523,["Reactive",2958],{},["Set"],["ShallowReactive",2961],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fmEvjPyA9kHBIkeiSKPEvs1E3m5Z4FTYr9ylRdkk79_Y":-1},"/vuejs/vitepress/4273"]