\u003C/svg>',\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nAdd `width=\"24\" height=\"24\" `attribute\r\nLike this\r\n```txt\r\n'\u003Csvg xmlns=\"http://www.w3.org/2000/svg\" width=\"24\" height=\"24\" viewBox=\"0 0 24 24\">' \r\n```\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Linux 6.3 Kali GNU/Linux Rolling 2023.3\r\n CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz\r\n Memory: 8.21 GB / 15.24 GB\r\n Container: Yes\r\n Shell: 5.9 - /usr/bin/zsh\r\n Binaries:\r\n Node: 18.13.0 - /usr/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.2.0 - /usr/bin/npm\r\n Browsers:\r\n Chrome: 116.0.5845.179\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.10 => 1.0.0-rc.10\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.",[3026,3029,3032],{"name":3027,"color":3028},"theme","0754FB",{"name":3030,"color":3031},"a11y","fbca04",{"name":3033,"color":3034},"stale","ededed",2930,"vuejs","vitepress","open","themeConfig.socialLinks.icon ","2024-02-02T09:23:16Z","https://github.com/vuejs/vitepress/issues/2930",0.774262,{"description":3044,"labels":3045,"number":3049,"owner":3036,"repository":3037,"state":3038,"title":3050,"updated_at":3051,"url":3052,"score":3053},"### 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.",[3046],{"name":3047,"color":3048},"bug: pending triage","e99695",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.78116965,{"description":3055,"labels":3056,"number":3058,"owner":3036,"repository":3037,"state":3059,"title":3060,"updated_at":3061,"url":3062,"score":3063},"### Describe the bug\r\n\r\nSuch code:\r\n\r\n````md\r\n```vue twoslash :line-numbers\r\n\u003Cscript setup lang=\"ts\">\r\nimport {ref} from 'vue';\r\n\r\nconst message = ref('Hello world!');\r\n\u003C/script>\r\n```\r\n````\r\n\r\ncode block line numbers would be from 1 to 2, rather than from 1 to 5, [see here](http://localhost:5173/knowledge-base/TODO#bug)\r\n\r\n### Reproduction\r\n\r\nusing such code in `vitepress`:\r\n\r\n````md\r\n```vue twoslash :line-numbers\r\n\u003Cscript setup lang=\"ts\">\r\nimport {ref} from 'vue';\r\n\r\nconst message = ref('Hello world!');\r\n\u003C/script>\r\n```\r\n````\r\n\r\n### Expected behavior\r\n\r\nline number works correctly\r\n\r\n### System Info\r\n\r\n```Text\r\nnone\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.",[3057],{"name":3047,"color":3048},3972,"closed","[BUG]","2024-06-28T04:43:03Z","https://github.com/vuejs/vitepress/issues/3972",0.7443633,{"description":3065,"labels":3066,"number":3070,"owner":3036,"repository":3037,"state":3059,"title":3071,"updated_at":3072,"url":3073,"score":3074},"### Describe the bug\r\n\r\nRunning `pnpm run build` on local VP repo on a Windows machine hangs.\r\n\r\n### Reproduction\r\n\r\nRun `pnpm run build` on a Windows machine\r\n\r\n### Expected behavior\r\n\r\nShouldn't hang\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700H\r\n Memory: 34.88 GB / 63.71 GB\r\n Binaries:\r\n Node: 22.6.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 10.8.2 - C:\\Program Files\\nodejs\\npm.CMD\r\n pnpm: 9.12.3 - C:\\Program Files\\nodejs\\pnpm.CMD\r\n Browsers:\r\n Edge: Chromium (127.0.2651.74)\r\n Internet Explorer: 11.0.19041.4355\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nUsing `fast-glob` just works.\r\n\r\nWe can fix `tinyglobby` using `cwd` and removing absolute path for the workers.\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.",[3067],{"name":3068,"color":3069},"upstream","BF29ED",4357,"`tinyglobby` hangs when build script or running local dev using Windows","2024-11-20T04:44:08Z","https://github.com/vuejs/vitepress/issues/4357",0.75591826,{"description":3076,"labels":3077,"number":3079,"owner":3036,"repository":3037,"state":3059,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Describe the bug\n\nHi team,\r\n\r\nI have tried with a self-hosted gha runner. \r\n\r\nthe gha workflow is copy/paste from the guidance, [here](https://vitepress.dev/zh/guide/deploy#github-pages)\r\n\r\nUnfortunately, I failed at the `Upload artifact` stage\r\n\r\n\r\nHere is my workflow:\r\n```\r\nname: Deploy VitePress site to git pages\r\n\r\non:\r\n push:\r\n branches: [main]\r\n\r\npermissions:\r\n contents: read\r\n pages: write\r\n id-token: write\r\n\r\nconcurrency:\r\n group: pages\r\n cancel-in-progress: false\r\n\r\njobs:\r\n build:\r\n runs-on: self-hosted\r\n steps:\r\n - name: Checkout\r\n uses: actions/checkout@v4\r\n with:\r\n fetch-depth: 0\r\n - name: Setup Node\r\n uses: actions/setup-node@v4\r\n with:\r\n node-version: 18\r\n cache: npm\r\n - name: Setup Pages\r\n uses: actions/configure-pages@v4\r\n - name: Install dependencies\r\n run: npm install\r\n - name: Build with VitePress\r\n env:\r\n NODE_OPTIONS: \"--max_old_space_size=4096\"\r\n run: npm run docs:build\r\n - name: Upload artifact\r\n uses: actions/upload-pages-artifact@v3\r\n with:\r\n path: .vitepress/dist\r\n\r\n deploy:\r\n environment:\r\n name: github-pages\r\n url: ${{ steps.deployment.outputs.page_url }}\r\n needs: build\r\n runs-on: self-hosted\r\n name: Deploy\r\n steps:\r\n - name: Deploy to GitHub Pages\r\n id: deployment\r\n uses: actions/deploy-pages@v4\r\n\r\n```\r\n\r\n\r\n\n\n### Reproduction\n\nRe-runed multiple times, but still failed\n\n### Expected behavior\n\nshould upload artefacts?\n\n### System Info\n\n```Text\ndeploying on git page\r\n\r\nusing self-host runner\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.",[3078],{"name":3047,"color":3048},3792,"Github action deploy failed, instructed by the guildance","2024-05-05T04:41:49Z","https://github.com/vuejs/vitepress/issues/3792",0.76121294,{"description":3085,"labels":3086,"number":3087,"owner":3036,"repository":3037,"state":3059,"title":3088,"updated_at":3089,"url":3090,"score":3091},"### Describe the bug\n\ncustom 404 component in theme/config.ts is not working when update vitepress to vitepress@v1.0.0-alpha.50. the same config is working when vitepress is vitepress@v1.0.0-alpha.49.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-dusqby\n\n### Expected behavior\n\ncustom 404 component should work\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 13.0.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 218.09 MB / 16.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 19.7.0 - /usr/local/bin/node\r\n npm: 9.5.0 - /usr/local/bin/npm\r\n Browsers:\r\n Safari: 16.1\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.",[],2049,"cannot define custom 404 component when use vitepress@v1.0.0-alpha.50","2023-03-17T00:04:21Z","https://github.com/vuejs/vitepress/issues/2049",0.76175773,{"description":3093,"labels":3094,"number":3095,"owner":3036,"repository":3037,"state":3059,"title":3096,"updated_at":3097,"url":3098,"score":3099},"### Is your feature request related to a problem? Please describe.\r\n\r\nYes and no: the logic to change the appearance is not quite simple, since the logic is on `VPSwitchAppearance` component, and it is not just adding/removing a class to the html tag and changing local storage, the logic includes some hack to avoid head flickering, and `VPSwitchAppearance` is not reactive to external changes on local storage.\r\n\r\nI have a case where I need to switch the appearance from outside, and it is a pain.\r\n\r\n### Describe the solution you'd like\r\n\r\nJust expose `useAppearance` logic included on `VPSwitchAppearance` and use that logic also on it, this way we only need to move the logic and export the composable.\r\n\r\n### Describe alternatives you've considered\r\n\r\nNone, since `VPSwitchAppearance` is not reactive, there is no way to avoid some phantom clicks.\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.",[],2192,"expose `useAppearance` as a composable","2023-04-14T00:04:12Z","https://github.com/vuejs/vitepress/issues/2192",0.76395583,{"description":3101,"labels":3102,"number":3104,"owner":3036,"repository":3037,"state":3059,"title":3105,"updated_at":3106,"url":3107,"score":3108},"### Describe the bug\n\nSince 1.0.0-alpha.41, there is a line break before the external link icon (arrow right up) for links going to other websites. \n\n### Reproduction\n\n.\n\n### Expected behavior\n\nHaving it inline with the title of that link.\n\n### System Info\n\n```shell\n.\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.",[3103],{"name":3027,"color":3028},1864,"Fix line break before \"external link icon\"","2023-03-05T00:04:52Z","https://github.com/vuejs/vitepress/issues/1864",0.7672045,{"description":3110,"labels":3111,"number":3115,"owner":3036,"repository":3037,"state":3059,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### 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.",[3112],{"name":3113,"color":3114},"build","377ba8",3305,"Colored Diffs in empty lines breaks + symbol","2024-01-08T00:04:50Z","https://github.com/vuejs/vitepress/issues/3305",0.7674842,{"description":3121,"labels":3122,"number":3124,"owner":3036,"repository":3037,"state":3059,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### Describe the bug\n\nWhy did I encounter Element is missing end tag? I can't understand this error\r\n\r\n\r\n\r\n\r\n```html\r\n\u003C!DOCTYPE html>\r\n\u003Chtml>\r\n \u003Chead lang=\"en\">\r\n \u003Cmeta charset=\"UTF-8\" />\r\n \u003Ctitle>\u003C/title>\r\n \u003Cstyle>\r\n /*申明字体*/\r\n @font-face {\r\n font-family: \"iconfont\";\r\n src: url(\"font/iconfont.eot\"); /* IE9*/\r\n src: url(\"font/iconfont.eot?#iefix\") format(\"embedded-opentype\"), /* IE6-IE8 */\r\n url(\"font/iconfont.woff\") format(\"woff\"),\r\n /* chrome、firefox */ url(\"font/iconfont.ttf\") format(\"truetype\"), /* chrome、firefox、opera、Safari, Android, iOS 4.2+*/\r\n url(\"font/iconfont.svg#iconfont\") format(\"svg\"); /* iOS 4.1- */\r\n }\r\n\r\n p {\r\n width: 200px;\r\n border: 1px solid #000;\r\n line-height: 60px;\r\n font-size: 30px;\r\n margin: 100px auto;\r\n text-align: center;\r\n position: relative;\r\n }\r\n\r\n .icon::before {\r\n content: \"\\e628\";\r\n font-family: iconfont;\r\n color: red;\r\n }\r\n\r\n span {\r\n position: relative;\r\n }\r\n \u003C/style>\r\n \u003C/head>\r\n \u003Cbody>\r\n \u003Cp class=\"icon\">扫码付款\u003C/p>\r\n \u003Cspan class=\"icon\">我是span\u003C/span>\r\n \u003Cdiv class=\"icon\">divvvvvvvvvvv\u003C/div>\r\n \u003C/body>\r\n\u003C/html>\r\n```\r\nIf this is a markdown verification error, can we make Vitepress more compatible with this type of error, or can we have a switch to enable this function\n\n### Reproduction\n\nnothing\n\n### Expected behavior\n\nsucceeful build\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz\r\n Memory: 2.88 GB / 15.85 GB\r\n Binaries:\r\n Node: 18.20.3 - C:\\Program Files\\nodejs\\node.EXE \r\n Yarn: 1.22.22 - ~\\AppData\\Roaming\\npm\\yarn.CMD \r\n npm: 10.7.0 - C:\\Program Files\\nodejs\\npm.CMD \r\n pnpm: 8.15.7 - C:\\Program Files\\nodejs\\pnpm.CMD \r\n bun: 1.1.21 - ~\\.bun\\bin\\bun.EXE\r\n Browsers:\r\n Chrome: 128.0.6613.120\r\n Edge: Chromium (127.0.2651.74)\r\n Internet Explorer: 11.0.19041.4355\r\n npmPackages:\r\n vitepress: ^1.3.1 => 1.3.1\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.",[3123],{"name":3047,"color":3048},4188,"Element is missing end tag.","2024-09-16T04:43:59Z","https://github.com/vuejs/vitepress/issues/4188",0.7703498,["Reactive",3130],{},["Set"],["ShallowReactive",3133],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fk9SPRxwczVL8TZlAtNkn4aHyv4nkHbA4ihl4N9eHVzk":-1},"/vuejs/vitepress/3787"]