\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.",[3040,3043,3046],{"name":3041,"color":3042},"theme","0754FB",{"name":3044,"color":3045},"a11y","fbca04",{"name":3047,"color":3048},"stale","ededed",2930,"themeConfig.socialLinks.icon ","2024-02-02T09:23:16Z","https://github.com/vuejs/vitepress/issues/2930",0.80256623,{"description":3055,"labels":3056,"number":3060,"owner":3030,"repository":3031,"state":3061,"title":3062,"updated_at":3063,"url":3064,"score":3065},"### Describe the bug\r\n\r\nnew version's issue.\r\n[Vite Doc] https://vitepress.vuejs.org/guide/getting-started was build by .49,\r\n\r\nAt the same time, the problem is that the search jump fails because anchors are not positioned correctly.\r\n\r\n[Vue Doc]https://vuejs.org/guide/essentials/event-handling.html#method-handlers build by .29 ,it's normal.\r\n\r\n### Reproduction\r\n\r\nin production \r\nhttps://vitepress.vuejs.org/guide/getting-started\r\n\r\n### Expected behavior\r\n\r\nURL can correctly locate the element \r\n\r\n\r\n### System Info\r\n\r\n```shell\r\nbrowser: Microsoft Edge\r\nVersion 110.0.1587.57 (Official build) (64-bit)\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] Follow our [Code of Conduct](https://vuejs.org/about/coc.html)\r\n- [X] Read the [docs](https://vitepress.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3057],{"name":3058,"color":3059},"bug: pending triage","e99695",2023,"closed","[DOC BUG] url not changing when scrolling side navbar and url jump failure","2023-03-10T00:04:38Z","https://github.com/vuejs/vitepress/issues/2023",0.698287,{"description":3067,"labels":3068,"number":3069,"owner":3030,"repository":3031,"state":3061,"title":3070,"updated_at":3071,"url":3072,"score":3073},"### Describe the bug\n\nI have written a markdown it plugin, and the code is as follows\r\n```js\r\nexport default defineConfig({\r\n title: \"My Awesome Project\",\r\n markdown: {\r\n config: (md) => {\r\n md.block.ruler.before(\r\n \"paragraph\",\r\n \"myplugin\",\r\n function (state, startLine, endLine) {\r\n var ch,\r\n token,\r\n pos = state.bMarks[startLine] + state.tShift[startLine],\r\n max = state.eMarks[startLine];\r\n ch = state.src.charCodeAt(pos);\r\n\r\n if (ch !== 0x40 /*@*/ || pos >= max) {\r\n return false;\r\n }\r\n\r\n let text = state.src.substring(pos, max);\r\n let rg = /^@\\s(.*)/;\r\n let match = text.match(rg);\r\n\r\n if (match && match.length) {\r\n let result = match[1];\r\n\r\n // Create the opening token for the h1 tag\r\n token = state.push(\"heading_open\", \"h1\", 1);\r\n token.markup = \"@\";\r\n token.map = [startLine, state.line];\r\n // Add class to the h1 tag\r\n token.attrs = [[\"class\", \"bg-red-300\"]];\r\n\r\n // Create the inline content inside the h1 tag\r\n token = state.push(\"inline\", \"\", 0);\r\n token.content = result;\r\n token.map = [startLine, state.line];\r\n token.children = [];\r\n\r\n // Create the closing token for the h1 tag\r\n token = state.push(\"heading_close\", \"h1\", -1);\r\n token.markup = \"@\";\r\n\r\n state.line = startLine + 1;\r\n return true;\r\n }\r\n }\r\n );\r\n },\r\n },\r\n });\r\n```\r\n\r\nIt's just a simple syntax parse(This is not the main point, it is just a simple plugin written to illustrate the issue)\r\n\r\nEnter the following content in the markdown file\r\n```\r\n@ header -> \u003Ch1 class=\"bg-red-300\">header\u003C/h1> \r\n```\r\n\r\nI have followed the [tailwindcss guide](https://tailwindcss.com/docs/guides/vite#vue)Installation\r\n\r\nThen start the development server\r\n```bash\r\nnpm run docs:dev\r\n```\r\n\r\n\r\nBut its'. bg-red-300 'style did not take effect\r\n\r\n\r\nBut when I continued to input an HTML fragment carrying 'bg-red-300' in markdown, it took effect\r\n\r\n\r\n\r\n\r\nWhen I deleted the HTML fragment carrying 'bg-red-300' and restarted the development server, it had no effect again\r\n\r\nrefer to:\r\nhttps://github.com/ajiho/vitepress-tailwindcss-markdown-it\r\n\r\nThis problem has been bothering me for a long time, can you help me?\r\n\n\n### Reproduction\n\n[refer to](https://github.com/ajiho/vitepress-tailwindcss-markdown-it)\n\n### Expected behavior\n\nAfter the parse plugin of markdown it renders, the tailwindcss style should take effect immediately\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (8) x64 Intel(R) Core(TM) i7-4720HQ CPU @ 2.60GHz\r\n Memory: 1.36 GB / 7.91 GB\r\n Binaries:\r\n Node: 22.11.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 10.9.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Chromium (131.0.2903.86)\r\n Internet Explorer: 11.0.19041.3636\r\n npmPackages:\r\n vitepress: ^1.5.0 => 1.5.0\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.",[],4433,"The style does not take effect when using the markdown extension plugin with tailwindcss","2024-12-26T04:43:12Z","https://github.com/vuejs/vitepress/issues/4433",0.7143696,{"description":3075,"labels":3076,"number":3078,"owner":3030,"repository":3031,"state":3061,"title":3079,"updated_at":3080,"url":3081,"score":3082},"### Describe the bug\n\nThe outline nav has the assistive tech text \"Table of Contents for current page\". Giving assistive tech users distinct or exclusive content is not recommended. In this case, the assistive tech-only text is at best duplicative (with the default outline title \"On this page\") and at worst conflicts with the visible text (if the outline title is configured to be something not equivalent to ~'things on this page').\n\n### Reproduction\n\nUse a screen reader to read the outline.\n\n### Expected behavior\n\nAssistive tech recognizes the configured outline title is as the outline's heading. No assistive tech-exclusive text duplicating displayed text is provided.\n\n### System Info\n\n```Text\nBrowser issue but here you go!\r\n\r\n\r\nSystem:\r\n OS: macOS 14.3.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 292.14 MB / 16.00 GB\r\n Shell: 5.9 - /opt/homebrew/bin/zsh\r\n Binaries:\r\n Node: 18.12.0 - ~/.asdf/installs/nodejs/18.12.0/bin/node\r\n Yarn: 1.22.22 - /opt/homebrew/bin/yarn\r\n npm: 8.19.2 - ~/.asdf/installs/nodejs/18.12.0/bin/npm\r\n pnpm: 8.15.6 - ~/Library/pnpm/pnpm\r\n bun: 1.1.4 - ~/.bun/bin/bun\r\n Browsers:\r\n Brave Browser: 123.1.64.122\r\n Chrome: 123.0.6312.124\r\n Edge: 123.0.2420.97\r\n Safari: 17.3.1\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.",[3077],{"name":3058,"color":3059},3800,"accessibility: outline nav has duplicative assistive tech text not displayed visually","2024-05-04T04:42:03Z","https://github.com/vuejs/vitepress/issues/3800",0.7256177,{"description":3084,"labels":3085,"number":3086,"owner":3030,"repository":3031,"state":3061,"title":3087,"updated_at":3088,"url":3089,"score":3090},"\r\n\r\n有大佬可以帮忙指导下这是什么问题吗",[],1387,"最新版本出现这样","2023-01-21T14:25:27Z","https://github.com/vuejs/vitepress/issues/1387",0.73818344,{"description":3092,"labels":3093,"number":3097,"owner":3030,"repository":3031,"state":3061,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### Describe the bug\r\n\r\nvitepress require user to set a specific [base path](https://vitepress.dev/reference/site-config#base) (default to `/`) and do not work on host where the pathname where the website is fetched from is unknown\r\n\r\n3 uses cases where this happen:\r\n- ipfs or other content-addressable network where the pathname is a hash that cannot be known before build time\r\n- archive website like the wayback machine that host website on sub path\r\n- some website that let you embed other website but where you are not in control of the path\r\n\r\nThis works with svelte+kit and so I expect vite to support that itself\r\n\r\n### Reproduction\r\n\r\nSee here the reproduction repo: https://github.com/bug-reproduction/vitepress-dynamic-base\r\n\r\nit is built off the the getting started guide\r\n\r\nit just add the ipfs-gateway-emulator package to show case the issue when the pathname on whcih the website is unknown\r\n\r\n# Reproduction\r\n\r\n```\r\ngit clone https://github.com/bug-reproduction/vitepress-dynamic-base.git\r\n```\r\n\r\n```\r\ncd vitepress-dynamic-base\r\n```\r\n\r\n```\r\npnpm i\r\n```\r\n\r\n```\r\npnpm docs:build\r\n```\r\n\r\n```\r\npnpm docs:ipfs\r\n```\r\n\r\nnavigate to http://127.0.0.1:8080/ \r\n\r\nand see the website is working\r\n\r\n\r\nNow navigate to http://127.0.0.1:8080/ipfs/anyhash \r\n\r\nand see how all the assets failed to load and page url break down\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nI expect to be able to build a vitepress website that use only relative path , that can then be loaded from any pathname\r\n\r\nThis is a requirement for ipfs website, especially when they are loaded from localhost ipfs node that use pathname as the hash\r\n\r\n### System Info\r\n\r\n```Text\r\nnot relevant\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.",[3094],{"name":3095,"color":3096},"wont fix","EDEED1",3057,"vitepress do not work on host where the subpath is unknown","2024-02-27T00:05:53Z","https://github.com/vuejs/vitepress/issues/3057",0.7398984,{"description":3103,"labels":3104,"number":3106,"owner":3030,"repository":3031,"state":3061,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Describe the bug\n\nWhen `cleanUrls` is set to `false`, but in Markdown links, using the following syntax:\n\n`[link](../menu/test){target=_blank}`\n\nThe generated link loses the `.html` suffix.\n\nIt should normally generate `../menu/test.html` instead of `../menu/test`.\n\n### Reproduction\n\n-\n\n### Expected behavior\n\n-\n\n### System Info\n\n```Text\nUsing `{target=_blank}` normally generates the `.html` suffix.\n```\n\n### Additional context\n\n-\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.",[3105],{"name":3058,"color":3059},4578,"`.html` suffix lose","2025-03-05T04:43:43Z","https://github.com/vuejs/vitepress/issues/4578",0.7464027,{"description":3112,"labels":3113,"number":3115,"owner":3030,"repository":3031,"state":3061,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Describe the bug\n\n\r\n\n\n### Reproduction\n\nhttps://vitepress.vuejs.org/\n\n### Expected behavior\n\ncorrect positioning\n\n### System Info\n\n```shell\nMicrosoft Edge\r\nVersion 110.0.1587.57 (Official build) (64-bit)\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.",[3114],{"name":3041,"color":3042},2027,"[DOC bug]error URL navigation","2023-03-18T00:04:21Z","https://github.com/vuejs/vitepress/issues/2027",0.77065724,{"description":3121,"labels":3122,"number":3124,"owner":3030,"repository":3031,"state":3061,"title":3125,"updated_at":3126,"url":3127,"score":3128},"### Describe the bug\n\nMy site is showing these two errors in the console:\n\n> A preload for 'https://.../assets/app.BXR81nYj.js' is found, but is not used because the request credentials mode does not match. Consider taking a look at crossorigin attribute.\n\n> The resource https://.../assets/app.BXR81nYj.js was preloaded using link preload but not used within a few seconds from the window's load event. Please make sure it has an appropriate `as` value and it is preloaded intentionally.\n\nIs there a fix or workaround for this? The closest related issue I was able to find was https://github.com/vercel/next.js/discussions/16850\n\nI'm using vitepress v1.6.3.\n\n### Reproduction\n\nI wasn't able to reproduce the issue in vitepress.new or my local dev server -- these errors only show up on production when deployed to Cloudflare Pages.\n\n### Expected behavior\n\nNo errors should be shown.\n\n### System Info\n\n```Text\nSystem:\n OS: Linux 5.15 Ubuntu 24.04.2 LTS 24.04.2 LTS (Noble Numbat)\n CPU: (16) x64 AMD Ryzen 7 PRO 7840U w/ Radeon 780M Graphics\n Memory: 22.94 GB / 29.21 GB\n Container: Yes\n Shell: 5.2.21 - /bin/bash\n Binaries:\n Node: 22.12.0 - ~/.nvm/versions/node/v22.12.0/bin/node\n npm: 10.9.0 - ~/.nvm/versions/node/v22.12.0/bin/npm\n bun: 1.2.4 - ~/.bun/bin/bun\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\n```\n\n### Additional context\n\nWhen I first started using vitepress (a version before v1.5.0), I did not see any errors.\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":3027,"color":3028},4714,"Compiled assets/app.js file found but not used errors","2025-04-23T04:40:05Z","https://github.com/vuejs/vitepress/issues/4714",0.77405363,["Reactive",3130],{},["Set"],["ShallowReactive",3133],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fDT8RAcIMQ0tDUJJhWGI5ariqKSEQNCXf7XtzC_lTDCw":-1},"/vuejs/vitepress/3449"]