\n\n### Reproduction\n\nnone\n\n### Expected behavior\n\nThe text inside the Badge component should not wrap and should remain on the same line to avoid disrupting the table layout.\n\n### System Info\n\n```Text\nnone\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.",[3028],{"name":3029,"color":3030},"bug: pending triage","e99695",4764,"vuejs","vitepress","open","Badge component unexpectedly breaks line in tables with long text","2025-05-27T08:28:39Z","https://github.com/vuejs/vitepress/issues/4764",0.782512,{"description":3040,"labels":3041,"number":3045,"owner":3032,"repository":3033,"state":3034,"title":3046,"updated_at":3047,"url":3048,"score":3049},"### Is your feature request related to a problem? Please describe.\r\n\r\nWhen I ported my MD document over, I encountered many problems and found that it was due to some\u003C>tags being incorrectly parsed (in fact, I didn't want them to be parsed). This has caused some trouble.\r\nThe example is as follows:\r\n~~~\r\n| 参数 | 含义 |\r\n| ----------------- | -------------------------------------------------- |\r\n| -d | 指定当前唯一通过 USB 连接的 Android 设备为命令目标 |\r\n| -e | 指定当前唯一运行的模拟器为命令目标 |\r\n| -s \u003CserialNumber>| 指定相应 serialNumber 号的设备/模拟器为命令目标 |\r\n\r\nAn error will be reported at this time:[plugin:vite:vue] Element is missing end tag.\r\n\r\nAlthough it can be solved by :| -s `\u003CserialNumber>`| ,\r\n~~~\r\n\r\n### Describe the solution you'd like\r\n\r\nI think simply prohibit parsing\u003C>in the table, is the simplest and most effective approach.I want to know how to disable parsing in a table.\r\n\r\nBecause I hope that documents that can be parsed normally in MD software such as Typora can be easily ported. The parsing of tags has caused some trouble.\r\n\r\n### Describe alternatives you've considered\r\n\r\nPerhaps globally banning the \"Using Vue in Markdown\" feature would also be effective?\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] 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.",[3042],{"name":3043,"color":3044},"needs more discussion","C2E0C6",4216,"Prohibit parsing\u003C>tags in markdown","2025-03-22T14:04:39Z","https://github.com/vuejs/vitepress/issues/4216",0.7934221,{"description":3051,"labels":3052,"number":3056,"owner":3032,"repository":3033,"state":3034,"title":3057,"updated_at":3058,"url":3059,"score":3060},"### Describe the bug\n\nThe documentation for the logo states \r\n> Logo file to display in nav bar, right before the site title. Accepts a path string, or an object to set a different logo for light/dark mode.\r\nand the following suggests that putting a logo in the root folder works:\r\n```\r\n export default {\r\n themeConfig: {\r\n logo: '/logo.svg'\r\n }\r\n}\r\n```\r\n\r\nDocumentation about static assets suggests that\r\n> Common image, media, and font filetypes are detected and included as assets automatically.\r\n\r\nHowever, it seems that the logo has to be put in the `public` folder to be picked up.\n\n### Reproduction\n\n* Set up default site with `npx vitepress init`\r\n*include a logo as given above\r\n* put it in root\r\n* see it not being picked up\n\n### Expected behavior\n\nEither documentation should mention including the logo in `public` or it should get picked up from root.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 6.5 Debian GNU/Linux trixie/sid\r\n CPU: (16) x64 AMD Ryzen 7 PRO 4750U with Radeon Graphics\r\n Memory: 17.38 GB / 30.58 GB\r\n Container: Yes\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node\r\n npm: 10.1.0 - ~/.nvm/versions/node/v20.9.0/bin/npm\r\n```\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.",[3053],{"name":3054,"color":3055},"stale","ededed",3246,"Logo not picked up if not in `public` folder","2024-12-03T17:28:48Z","https://github.com/vuejs/vitepress/issues/3246",0.79359025,{"description":3062,"labels":3063,"number":3065,"owner":3032,"repository":3033,"state":3034,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Describe the bug\n\nThe EasyList social filter rules include `.social-links-list` selector, which causes certain elements on VitePress pages to not display properly.\n\nHere’s the affected component code:\nhttps://github.com/vuejs/vitepress/blob/827259b0d5e4032ec6e7a696969ecc2ed77c6bc2/src/client/theme-default/components/VPNavBarExtra.vue#L58\n\nHere’s the source of the EasyList rule (Be cautious when accessing this file — it’s quite large and may crash your browser):\nhttps://github.com/easylist/easylist/blob/053fcd167ec66bd798cb9c3dde99c2906b1ffde8/fanboy-addon/fanboy_social_general_hide.txt#L8004\n\n\u003Cimg width=\"261\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/c920152b-c413-4ddf-9241-0823abba69f0\" />\n\n### Reproduction\n\nWhen ad blockers like uBO or Adblock Plus have the social rules enabled, the affected element disappears.\n\n\u003Cimg width=\"493\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/77fe95e0-2d55-4b0a-9b4b-1add1da38930\" />\n\n\u003Cimg width=\"1137\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/3100bd1f-8c92-4e8b-a0ec-99f1213bf746\" />\n\nDisabling the relevant rule restores them to normal.\n\n\u003Cimg width=\"499\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/fa8d2a12-1c2c-42e1-a0cd-cc880e2a17ea\" />\n\n### Expected behavior\n\nI'm aware this is a Fanboy rule and not enabled by default, but ad blockers often make it easy for users to enable it. Renaming the class to something not on the blocklist is a simpler and more practical workaround.\n\nChanging it to `social-links-items` should work, though in the long run, it might be better to avoid using names like `social-link` altogether.\n\n### System Info\n\n```Text\nNot necessary.\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.",[3064],{"name":3029,"color":3030},4732,"[Suggestion] Avoid using `social-links-list` class, as it may be blocked by EasyList","2025-05-04T15:38:12Z","https://github.com/vuejs/vitepress/issues/4732",0.7941729,{"description":3071,"labels":3072,"number":3075,"owner":3032,"repository":3033,"state":3034,"title":3076,"updated_at":3077,"url":3078,"score":3079},"### Describe the bug\r\n\r\nGenerating the page structure from data is incorrect if the level of h2 headers has to be generated:\r\n\r\n```html\r\n\u003Cscript setup>\r\nconst repos = [\r\n { name: 'Client' },\r\n { name: 'Server' },\r\n { name: 'Socket' }\r\n]\r\n\u003C/script>\r\n\r\n# Repositories\r\n\r\n\u003Ctemplate v-for=\"repo in repos\">\r\n\r\n## {{ repo.name }}\r\n\r\n\u003C/template>\r\n```\r\n\r\nResulting HTML uses the wrong `id` for all `h2` elements. Instead of deriving the anchor id from the rendered text, the JavaScript expression `repo-name` is used:\r\n\r\n```html\r\n\u003Cdiv>\r\n \u003Ch1 id=\"repositories\" tabindex=\"-1\">Repositories \u003Ca class=\"header-anchor\" href=\"#repositories\"\r\n aria-label=\"Permalink to "Repositories"\">\u003C/a>\u003C/h1>\r\n \u003Ch2 id=\"repo-name\" tabindex=\"-1\">Client \u003Ca class=\"header-anchor\" href=\"#repo-name\"\r\n aria-label=\"Permalink to "{{ repo.name }}"\">\u003C/a>\u003C/h2>\r\n \u003Ch2 id=\"repo-name\" tabindex=\"-1\">Server \u003Ca class=\"header-anchor\" href=\"#repo-name\"\r\n aria-label=\"Permalink to "{{ repo.name }}"\">\u003C/a>\u003C/h2>\r\n \u003Ch2 id=\"repo-name\" tabindex=\"-1\">Socket \u003Ca class=\"header-anchor\" href=\"#repo-name\"\r\n aria-label=\"Permalink to "{{ repo.name }}"\">\u003C/a>\u003C/h2>\r\n\u003C/div>\r\n```\r\n\r\nThis also seems to cause problems with hydration, probably because the ids are not unique.\r\n\r\n### Reproduction\r\n\r\nSee https://stackblitz.com/edit/vite-avxyva?file=docs%2Fexample.md\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nThe 'id' for each 'h2' element is generated properly from the actual text content:\r\n\r\n```html\r\n\u003Cdiv>\r\n \u003Ch1 id=\"repositories\" tabindex=\"-1\">Repositories \u003Ca class=\"header-anchor\" href=\"#repositories\"\r\n aria-label=\"Permalink to "Repositories"\">\u003C/a>\u003C/h1>\r\n \u003Ch2 id=\"client\" tabindex=\"-1\">Client \u003Ca class=\"header-anchor\" href=\"#client\"\r\n aria-label=\"Permalink to "Client"\">\u003C/a>\u003C/h2>\r\n \u003Ch2 id=\"server\" tabindex=\"-1\">Server \u003Ca class=\"header-anchor\" href=\"#server\"\r\n aria-label=\"Permalink to "Server"\">\u003C/a>\u003C/h2>\r\n \u003Ch2 id=\"socket\" tabindex=\"-1\">Socket \u003Ca class=\"header-anchor\" href=\"#socket\"\r\n aria-label=\"Permalink to "Socket"\">\u003C/a>\u003C/h2>\r\n\u003C/div>\r\n```\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (16) x64 Intel(R) Xeon(R) W-11955M CPU @ 2.60GHz\r\n Memory: 10.40 GB / 31.73 GB\r\n Binaries:\r\n Node: 18.18.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 10.1.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Watchman: 20231008.002904.0 - C:\\ProgramData\\chocolatey\\bin\\watchman.EXE\r\n Browsers:\r\n Edge: Spartan (44.19041.3570.0), Chromium (118.0.2088.61)\r\n Internet Explorer: 11.0.19041.3570\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.24 => 1.0.0-rc.24\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.",[3073,3074],{"name":3029,"color":3030},{"name":3054,"color":3055},3133,"H2 anchors generated incorrectly if content generated dynamically","2023-12-26T20:33:15Z","https://github.com/vuejs/vitepress/issues/3133",0.7956619,{"description":3081,"labels":3082,"number":3084,"owner":3032,"repository":3033,"state":3085,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Describe the bug\n\nWhen we have long lines within a Code block, lines do not split into multiple lines\r\n\u003Cimg width=\"254\" alt=\"image\" src=\"https://user-images.githubusercontent.com/48757340/207985200-49a9dff9-339c-45c1-8b56-798689266f35.png\">\r\n\r\nAlso, if the first line is long enough it got interfered with upper right language name\r\n\u003Cimg width=\"92\" alt=\"image\" src=\"https://user-images.githubusercontent.com/48757340/207985142-5c825804-785c-4120-aebd-a232b3ed64cc.png\">\r\n\n\n### Reproduction\n\nFor Example:\r\n\r\n```sql\r\nDECLARE @pathNameDB NVARCHAR(512) \r\n\r\nSET @pathNameDB = 'D:\\Backup\\DBServerName_' + Convert(varchar(8), GETDATE(), 112) + '.bak' \r\nBACKUP DATABASE [DataBaseName] TO DISK = @pathNameDB WITH NOFORMAT, NOINIT, NAME = N'db_backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10\r\n\r\nGO\r\n```\n\n### Expected behavior\n\nLine splitted, so reader dont need to use scroll bars to see the whole line\n\n### System Info\n\n```shell\nwindows, alpha31\n```\n\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3083],{"name":3029,"color":3030},1697,"closed","No line splitting in Code Blocks","2023-01-21T14:17:14Z","https://github.com/vuejs/vitepress/issues/1697",0.76096314,{"description":3091,"labels":3092,"number":3096,"owner":3032,"repository":3033,"state":3085,"title":3097,"updated_at":3098,"url":3099,"score":3100},"_Originally posted by @brc-dd in https://github.com/vuejs/vitepress/issues/1152#issuecomment-1214753422_",[3093],{"name":3094,"color":3095},"theme","0754FB",1169,"UI inconsistencies with code blocks","2023-01-21T14:28:44Z","https://github.com/vuejs/vitepress/issues/1169",0.7762765,{"description":3102,"labels":3103,"number":3105,"owner":3032,"repository":3033,"state":3085,"title":3106,"updated_at":3107,"url":3108,"score":3109},"### Describe the bug\n\nSome design tokens (CSS Variables) for text color do not meet a11y standards for accessible text color. I am noticing particularly with `--vp-c-text-2` in the light theme. Its off by a delta of only ~0.2 points so I'm betting there is a happy medium of a minor adjustment that can be made to the colors to meet the standard of a 4.5:1 ratio.\r\n\r\n\n\n### Reproduction\n\n- Visit https://vitepress.vuejs.org/\r\n- Enable light theme\r\n- Use the browser inspect accessibility tab and filter by contrast (I use Firefox)\r\n- Notice all the checks about contrast\n\n### Expected behavior\n\nThere should be no contrast checks for light theme (also dark theme should be audited as well).\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 12.1\r\n CPU: (10) arm64 Apple M1 Pro\r\n Memory: 144.91 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.16.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /opt/homebrew/bin/yarn\r\n npm: 8.19.2 - /opt/homebrew/bin/npm\r\n Browsers:\r\n Chrome: 110.0.5481.177\r\n Firefox: 110.0.1\r\n Safari: 15.2\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.49 => 1.0.0-alpha.49\n```\n\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3104],{"name":3094,"color":3095},2038,"[a11y][theme] Text color does not meet WCAG standards for accessible text","2023-03-23T00:04:27Z","https://github.com/vuejs/vitepress/issues/2038",0.7835396,{"description":3111,"labels":3112,"number":3116,"owner":3032,"repository":3033,"state":3085,"title":3117,"updated_at":3118,"url":3119,"score":3120},"### Describe the bug\n\nI found in `vue-html` code blocks + line number mode, there is no `line-numbers-mode` CSS class on the div wrapper, which leads to the layout bug like below:\r\n\r\n\r\n\r\n\r\n\n\n### Reproduction\n\n`index.md`:\r\n\r\n```\r\n\\```html\r\n\u003Cdiv id=\"event-handling\">\r\n \u003Cp>{{ message }}\u003C/p>\r\n \u003Cbutton v-on:click=\"reverseMessage\">Reverse Message\u003C/button>\r\n\u003C/div>\r\n\\```\r\n\r\n\\```vue-html\r\n\u003Cdiv id=\"event-handling\">\r\n \u003Cp>{{ message }}\u003C/p>\r\n \u003Cbutton v-on:click=\"reverseMessage\">Reverse Message\u003C/button>\r\n\u003C/div>\r\n\\```\r\n```\r\n\r\n`.vitepress/config.js`:\r\n\r\n```\r\nmodule.exports = () => ({\r\n markdown: {\r\n lineNumbers: true\r\n }\r\n})\r\n```\n\n### Expected behavior\n\nBy manually adding the CSS class in devtools, it goes normal.\r\n\r\n\r\n\r\n\r\n\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 13.0\r\n CPU: (8) arm64 Apple M1\r\n Memory: 130.56 MB / 8.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.14.2 - ~/.nvm/versions/node/v16.14.2/bin/node\r\n Yarn: 1.22.18 - ~/.yarn/bin/yarn\r\n npm: 8.5.0 - ~/.nvm/versions/node/v16.14.2/bin/npm\r\n Browsers:\r\n Chrome: 103.0.5060.134\r\n Safari: 16.0\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.4 => 1.0.0-alpha.4\n```\n\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.vuejs.org).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3113],{"name":3114,"color":3115},"build","377ba8",1105,"The layout of vue-html code block in line number mode","2023-01-21T14:28:55Z","https://github.com/vuejs/vitepress/issues/1105",0.78686106,{"description":3122,"labels":3123,"number":3125,"owner":3032,"repository":3033,"state":3085,"title":3126,"updated_at":3127,"url":3128,"score":3129},"### Describe the bug\r\n\r\n```md\r\n```js\r\n// [!code ++:4]\r\nconsole.log(1);\r\nconsole.log(1);\r\n\r\nconsole.log(1);\r\n\\```\r\n```\r\n\r\nRenders this following example:\r\n\r\n\r\n\r\nThis is due because a `\u003Cspan class=\"line diff add\">\u003C/span>` (line 3) is created without any content, if we change it to `\u003Cspan class=\"line diff add\"> \u003C/span>`, it now renders correctly.\r\n\r\n\r\n\r\nNot sure if a blank space is the best fix. \r\n\r\nAlso, should a line only containing `// [!code ++:4]` be highlighted as well? \r\n\r\n### Reproduction\r\n\r\nabove\r\n\r\n### Expected behavior\r\n\r\nto work normally\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.3 LTS 22.04.3 LTS (Jammy Jellyfish)\r\n CPU: (20) x64 13th Gen Intel(R) Core(TM) i5-13600K\r\n Memory: 16.53 GB / 23.47 GB\r\n Container: Yes\r\n Shell: 5.8.1 - /usr/bin/zsh\r\n Binaries:\r\n Node: 20.9.0 - ~/.nvm/versions/node/v20.9.0/bin/node\r\n npm: 10.2.1 - ~/.nvm/versions/node/v20.9.0/bin/npm\r\n pnpm: 8.10.5 - ~/.nvm/versions/node/v20.9.0/bin/pnpm\r\n bun: 1.0.7 - ~/.bun/bin/bun\r\n npmPackages:\r\n vitepress: 1.0.0-rc.31 => 1.0.0-rc.31\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.",[3124],{"name":3114,"color":3115},3305,"Colored Diffs in empty lines breaks + symbol","2024-01-08T00:04:50Z","https://github.com/vuejs/vitepress/issues/3305",0.7879352,["Reactive",3131],{},["Set"],["ShallowReactive",3134],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fllOJCAU2ro7s1E9w6hudFPff_pCgigHh6-q3uxgJmd0":-1},"/vuejs/vitepress/1033"]