\n\n### Expected behavior\n\nI hope to use SVG and other methods instead of using masks to display icons, which can avoid frequent redrawing\n\n### System Info\n\n```Text\n\"vitepress\": \"^1.6.4\",\n```\n\n### Additional context\n\n\u003Cimg width=\"2559\" height=\"1042\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/39db5990-f3ee-47bb-8bcf-49272a1918f4\" />\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.",[3159],{"name":3160,"color":3161},"bug: pending triage","e99695",4917,"Bug: Frequent triggering of redrawing of navigation bar icons","2025-08-21T09:14:41Z","https://github.com/vuejs/vitepress/issues/4917",0.746631,{"description":3168,"labels":3169,"number":3179,"owner":3149,"repository":3150,"state":3151,"title":3180,"updated_at":3181,"url":3182,"score":3183},"### Describe the bug\r\n\r\nUsing `@babylonjs/loaders` will cause an error during the build phase: `KHR_animation_pointer.data.js`: config must export or return an object.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-v1c8np4w\r\n\r\nRun `npm run docs:build`.\r\n\r\n### Expected behavior\r\n\r\nThe error \"config must export or return an object\" should not occur.\r\n\r\nRemoving `import '@babylonjs/loaders'` will prevent any errors from occurring.\r\n\r\nI suspect it might be due to the filename `KHR_animation_pointer.data.js`, which might cause VitePress to mistakenly identify it as a `data loader`, leading to this error.\r\n\r\nIf my guess is correct, might there be a need for a way to exclude specific files?\r\n\r\n### System Info\r\n\r\n```Text\r\n@babylonjs/loaders: 7.43.0\r\nvitepress: 1.5.0\r\n```\r\n\r\n\r\n### Additional context\r\n\r\n> vitepress build docs\r\n\r\n\r\n vitepress v1.5.0\r\n\r\n⠇ building client + server bundles...failed to load config from /home/projects/vite-v1c8np4w/node_modules/@babylonjs/loaders/glTF/2.0/Extensions/KHR_animation_pointer.data.js\r\nx Build failed in 3.63s\r\n✖ building client + server bundles...\r\nbuild error:\r\n[commonjs--resolver] Could not load /home/projects/vite-v1c8np4w/node_modules/@babylonjs/loaders/glTF/2.0/Extensions/KHR_animation_pointer.data.js: config must export or return an object.\r\n[commonjs--resolver] Could not load /home/projects/vite-v1c8np4w/node_modules/@babylonjs/loaders/glTF/2.0/Extensions/KHR_animation_pointer.data.js: config must export or return an object.\r\n at Module.loadConfigFromFile (file:///home/projects/vite-v1c8np4w/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:66589:13)\r\n at async Object.load (file:///home/projects/vite-v1c8np4w/node_modules/vitepress/dist/node/chunk-DMuPggCS.js:44533:21)\r\n \r\n \r\n\r\n\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.",[3170,3173,3176],{"name":3171,"color":3172},"build","377ba8",{"name":3174,"color":3175},"stale","ededed",{"name":3177,"color":3178},"needs more discussion","C2E0C6",4482,"Using babylonjs/loaders, the error \"config must export or return an object\" occurs","2025-03-02T18:07:54Z","https://github.com/vuejs/vitepress/issues/4482",0.75762856,{"description":3185,"labels":3186,"number":3187,"owner":3149,"repository":3150,"state":3188,"title":3189,"updated_at":3190,"url":3191,"score":3192},"### Is your feature request related to a problem? Please describe.\n\nMy site config:\r\n\r\n```\r\nexport default defineConfig({\r\n themeConfig: {\r\n nav: [\r\n { link: '/about', text: 'About' },\r\n { link: '/feed.rss', text: 'RSS' },\r\n ]\r\n }\r\n})\r\n```\r\n\r\nThe link which will be generated for `/feed.rss` is `/feed.rss.html`\n\n### Describe the solution you'd like\n\nAdd `exactMatch?: boolean` to the interface `NavItemWithLink`.\r\n```\r\nexport default defineConfig({\r\n themeConfig: {\r\n nav: [\r\n { link: '/about', text: 'About' },\r\n { link: '/feed.rss', text: 'RSS', exactMatch: true },\r\n ]\r\n }\r\n})\r\n```\r\n\r\nIf `exactMatch` is `true`, do not append the suffix `.html` to the generated navigation link.\n\n### Describe alternatives you've considered\n\nN/A\n\n### Additional context\n\nN/A\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.",[],3851,"closed","Support exact match for navigation link","2024-05-10T04:42:00Z","https://github.com/vuejs/vitepress/issues/3851",0.70134014,{"description":3194,"labels":3195,"number":3199,"owner":3149,"repository":3150,"state":3188,"title":3200,"updated_at":3201,"url":3202,"score":3203},"### Is your feature request related to a problem? Please describe.\n\nThe home page looks quite good on a larger display. Once you switch to a documentation page, the conent feels a bit squeezed together. This is mostly due to paddings from the left and right sidebar and the content. Each \"padding\" considered alone is not very large. However, when added together, I think a lot of space is wasted here.\r\n\r\n\n\n### Describe the solution you'd like\n\nAdd a \"full width\" mode for desktop view, configureable via the theme settings (true/false). This should reduce the paddings and maximize the content width.\r\n\r\nNow :\r\n\u003Cimg width=\"1624\" alt=\"Screenshot1\" src=\"https://github.com/vuejs/vitepress/assets/30625794/941774fd-b73f-4b03-8095-f1eda053f247\">\r\n\r\n\r\nExpected :\r\n\u003Cimg width=\"1624\" alt=\"Screenshot2\" src=\"https://github.com/vuejs/vitepress/assets/30625794/62a77e31-80a6-4f54-b894-28f58d3460af\">\r\n\r\nI think this will result in some better readability when you have a documentation with some screenshots or larger code parts.\r\n\n\n### Describe alternatives you've considered\n\nMaybe you can try to write some hacky CSS overrides, but this is not a good solution.\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.",[3196],{"name":3197,"color":3198},"theme","0754FB",3160,"Full width layout for larger screens like desktop","2023-11-08T00:04:17Z","https://github.com/vuejs/vitepress/issues/3160",0.71923083,{"description":3205,"labels":3206,"number":3210,"owner":3149,"repository":3150,"state":3188,"title":3211,"updated_at":3212,"url":3213,"score":3214},"### Describe the bug\n\nbuild error:\nReferenceError: window is not defined\n at file:///E:/docs/.vitepress/.temp/app.js?t=1741415492907:9826:3\n at ModuleJob.run (node:internal/modules/esm/module_job:222:25)\n at async ModuleLoader.import (node:internal/modules/esm/loader:316:24)\n at async build (file:///E:/node_modules/.pnpm/vitepress@1.0.1_@algolia+client-search@4.20.0_@types+node@20.8.10_async-validator@4.2.5_axios_6jmcxapznl6bymfiwls65tjhl4/node_modules/vitepress/dist/node/serve-C_2bYS0g.js:46722:24)\n ELIFECYCLE Command failed with exit code 1.\n ELIFECYCLE Command failed with exit code 1.\n\n\n\n### Reproduction\nVitePress is the most difficult tool I have ever used, because you don't even know where the error is coming from!\n**I can't tell where the error is. This project has tens of thousands of lines of code. How can I find it?**\n\n### Expected behavior\n\nFind the file with the error message\n\n### System Info\n\n```Text\nSystem:\n OS: Windows 10 10.0.19045\n CPU: (6) x64 Intel(R) Core(TM) i5-9400 CPU @ 2.90GHz\n Memory: 15.36 GB / 31.94 GB\n Binaries:\n Node: 20.15.0 - C:\\Program Files\\nodejs\\node.EXE\n npm: 10.7.0 - C:\\Program Files\\nodejs\\npm.CMD\n pnpm: 9.14.2 - C:\\Program Files\\nodejs\\pnpm.CMD\n Browsers:\n Chrome: bookmarks.html\ninitial_preferences\n Edge: Spartan (44.19041.1266.0), Chromium (127.0.2651.74)\n Internet Explorer: 11.0.19041.1566\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.",[3207],{"name":3208,"color":3209},"need more info","bdbefc",4606,"ReferenceError: window is not defined!!!","2025-03-18T04:44:37Z","https://github.com/vuejs/vitepress/issues/4606",0.7371764,{"description":3216,"labels":3217,"number":3221,"owner":3149,"repository":3150,"state":3188,"title":3222,"updated_at":3223,"url":3224,"score":3225},"Hi,\r\n\r\nI almost finished my lib docs and now I am refactoring demos and I want to put demo section links in my custom card.\r\n\r\n\r\n\r\nHow can I convert my `h2` tag like `markdown-it` tag so it can get anchor based on its name.",[3218],{"name":3219,"color":3220},"has-workaround","1B4515",960,"Generate IDs for headers added through Vue components or raw HTML","2023-09-02T00:04:05Z","https://github.com/vuejs/vitepress/issues/960",0.73719215,{"description":3227,"labels":3228,"number":3230,"owner":3149,"repository":3150,"state":3188,"title":3231,"updated_at":3232,"url":3233,"score":3234},"### 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.",[3229],{"name":3160,"color":3161},3972,"[BUG]","2024-06-28T04:43:03Z","https://github.com/vuejs/vitepress/issues/3972",0.73889804,{"description":3236,"labels":3237,"number":3239,"owner":3149,"repository":3150,"state":3188,"title":3240,"updated_at":3241,"url":3242,"score":3243},"### Describe the bug\n\nHover state on link in `.vp-doc` is always matched, seems `:hover` is being truncated.\r\n\r\n\r\nCopy button in code block is also messed up.\r\n\r\n\r\n\r\nTable style messed up as well.\r\n\r\nI guess there's a lot more...\n\n### Reproduction\n\nIn `config.ts`:\r\n```ts\r\nexport default defineConfig({\r\n vite: {\r\n css: {\r\n postcss: {\r\n plugins: [\r\n postcssIsolateStyles({\r\n includeFiles: [/vp-doc\\.css/]\r\n }),\r\n ],\r\n },\r\n }\r\n})\r\n```\r\n\r\nI would write one if required, but since my above example is pretty easy to reproduce, I'll leave it blank here.\n\n### Expected behavior\n\nStyle not messed up\r\n\r\n (NOTE: it's working properly if I use `postcss-prefix-selector` straight away instead of using the one from vitepress package)\n\n### System Info\n\n```sh\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (16) x64 11th Gen Intel(R) Core(TM) i9-11900K @ 3.50GHz\r\n Memory: 38.35 GB / 63.84 GB\r\n Binaries:\r\n Node: 18.16.0 - C:\\NodeJS\\node.EXE\r\n Yarn: 1.22.19 - C:\\NodeJS\\yarn.CMD\r\n npm: 9.8.1 - C:\\NodeJS\\npm.CMD\r\n pnpm: 8.7.0 - C:\\NodeJS\\pnpm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (116.0.1938.62)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.9 => 1.0.0-rc.9\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.",[3238],{"name":3160,"color":3161},2868,"`postcssIsolateStyles` mess up original styles","2023-09-05T00:04:08Z","https://github.com/vuejs/vitepress/issues/2868",0.7440167,{"description":3245,"labels":3246,"number":3247,"owner":3149,"repository":3150,"state":3188,"title":3248,"updated_at":3249,"url":3250,"score":3251},"### Describe the bug\n\ncontent 部分没有 overflow:hidden 导致很长的滚动条(也有可能是我的图片太大?)\r\n\r\n[github here](https://github.com/Mt-Youya/DeepLearning-500-questions)\r\n\r\n[site here](https://deeplearning-500-questions.pages.dev/zh-cn/ch02_%E6%9C%BA%E5%99%A8%E5%AD%A6%E4%B9%A0%E5%9F%BA%E7%A1%80/%E7%AC%AC%E4%BA%8C%E7%AB%A0_%E6%9C%BA%E5%99%A8%E5%AD%A6%E4%B9%A0%E5%9F%BA%E7%A1%80.html)\n\n### Reproduction\n\n我fork 别人的仓库,不是我自己写的, 它原本用的是 docsify 我想提个pr用vitepress 试试,然后就出现了这个bug\n\n### Expected behavior\n\n没有滚动条\n\n### System Info\n\n```Text\nVersion 122.0.6261.112 (Official Build) (64-bit)\r\nwin11\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.",[],3644,"CSS bug","2024-03-19T00:07:30Z","https://github.com/vuejs/vitepress/issues/3644",0.7502742,["Reactive",3253],{},["Set"],["ShallowReactive",3256],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fPqBBHy3nD9_kfPGSoZgUR418IQ-QnYGqsd7YoKc-5b0":-1},"/vuejs/vitepress/2246"]