\n```\n\ndocs/AComponent.vue\n\n```vue\n\u003Ctemplate>\n \u003Ch2 id=\"bar\">bar\u003C/h2>\n \u003Ch2 id=\"baz\">baz\u003C/h2>\n\u003C/template>\n```\n\nResult: `## bar` and `## baz` appear in the outline and are linkable, but they have no header‑anchor element, so users cannot easily copy a permalink, and the UI feels a bit inconsistent when hovering the mouse over headings added by the component and the ones written in Markdown.\n\n\n### Describe the solution you'd like\n\nDuring the same client‑side pass that builds the outline, scan for any `\u003Ch1‑h6>` with an `id` but lacking `.header-anchor`, and inject an anchor with the same markup VitePress generates for Markdown headings.\n\n\n### Describe alternatives you've considered\n\nManually adding the anchor works...\n\n```html\n\u003Ch2 id=\"qux\">\n qux\n \u003Ca class=\"header-anchor\" href=\"#qux\" aria-label='Permalink to \"qux {#qux}\"'>​\u003C/a>\n\u003C/h2>\n```\n\n...but is somewhat boilerplate and is brittle. It must be manually added to each place where `\u003Ch1‑h6>` is used and will break if the theme changes.\n\n### Additional context\n\nScreencast of how the repro example looks:\n\n\nhttps://github.com/user-attachments/assets/28deb3dc-47d4-4c16-9d30-f491cfb58fda\n\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.",[],4867,"Auto‑insert `\u003Ca.header‑anchor>` for headings rendered by Vue components","2025-07-30T19:09:15Z","https://github.com/vuejs/vitepress/issues/4867",0.8198641,{"description":3062,"labels":3063,"number":3065,"owner":3033,"repository":3034,"state":3035,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Is your feature request related to a problem? Please describe.\n\nFirst of all, I would like to say thank you to all authors and contributers of the vitepress.\r\n\r\nWe are trying to migrate from hugo to vitepress and while vitepress has its benefits I do believe its lacking from one crutial functionality: Taxonomies Meaning, use label pages and create custom relations between them using front matter. Which allows simple yet powerfull way to work with complex websites. \n\n### Describe the solution you'd like\n\nI'll use example from [hugo documentation](https://gohugo.io/content-management/taxonomies/):\r\n\r\n### movie website\r\nLet’s assume you are making a website about movies. You may want to include the following taxonomies:\r\n\r\n- Actors\r\n- Directors\r\n- Studios\r\n- Genre\r\n- Year\r\n- Awards\r\n\r\nThen, in each of the movies, you would specify terms for each of these taxonomies of each of your movie content files). From these terms, platform would automatically create pages for each Actor, Director, Studio, Genre, Year, and Award, with each listing all of the Movies that matched that specific Actor, Director, Studio, Genre, Year, and Award.\r\n\r\n### Movie taxonomy organization \r\nTo continue with the example of a movie site, the following demonstrates content relationships from the perspective of the taxonomy:\r\n\r\n```\r\nActor \u003C- Taxonomy\r\n Bruce Willis \u003C- Term\r\n The Sixth Sense \u003C- Value\r\n Unbreakable \u003C- Value\r\n Moonrise Kingdom \u003C- Value\r\n Samuel L. Jackson \u003C- Term\r\n Unbreakable \u003C- Value\r\n The Avengers \u003C- Value\r\n xXx \u003C- Value\r\n```\r\n \r\nFrom the perspective of the content, the relationships would appear differently, although the data and labels used are the same:\r\n\r\n```\r\nUnbreakable \u003C- Value\r\n Actors \u003C- Taxonomy\r\n Bruce Willis \u003C- Term\r\n Samuel L. Jackson \u003C- Term\r\n Director \u003C- Taxonomy\r\n M. Night Shyamalan \u003C- Term\r\n ...\r\nMoonrise Kingdom \u003C- Value\r\n Actors \u003C- Taxonomy\r\n Bruce Willis \u003C- Term\r\n Bill Murray \u003C- Term\r\n Director \u003C- Taxonomy\r\n Wes Anderson \u003C- Term\r\n ...\r\n```\r\n\r\nThis will be very helpfull for any platform which has categories/subcateries content (I guess almost any platform)\n\n### Describe alternatives you've considered\n\nSince we are in migration process, I might be bias toward hugo realization but I'm sure this will be step in a right direction\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.",[3064],{"name":3030,"color":3031},4234,"Add Taxonomies","2025-03-02T18:08:29Z","https://github.com/vuejs/vitepress/issues/4234",0.8296258,{"description":3071,"labels":3072,"number":3079,"owner":3033,"repository":3034,"state":3080,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### Is your feature request related to a problem? Please describe.\n\ndefault directory is /docs/.vitepress/dist\r\n\r\nI hope I can customize the directory of the compilation package\n\n### Describe the solution you'd like\n\n```js\r\n//config.js\r\n\r\n\r\nexport default{\r\n// add output options config\r\n output:{\r\n path:'/dist/' ,//default value is /docs/.vitepress/dist/\r\n }\r\n\r\n}\r\n\r\n```\n\n### Describe alternatives you've considered\n\n_No response_\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] 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.",[3073,3076],{"name":3074,"color":3075},"docs","0075ca",{"name":3077,"color":3078},"question","5D5FAE",1111,"closed","how to Custom compilation result directory","2023-01-21T14:28:52Z","https://github.com/vuejs/vitepress/issues/1111",0.7666812,{"description":3086,"labels":3087,"number":3089,"owner":3033,"repository":3034,"state":3080,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### Is your feature request related to a problem? Please describe.\n\nWhen a sidebar group is collapsed, it will not auto open even if the user enter a doc inside it. This doesn't match the user's expectation in most cases. \n\n### Describe the solution you'd like\n\nAuto opening the collapsed sidebar when user enter any doc of the group.\r\n\r\neg.\r\n\r\nlet's assume there is a group named \"Collection A\" with a doc \"Doc A\" inside it. By default it's collapsed.\r\n```\r\nCollection A +\r\n```\r\n\r\nUser visit \"Doc A\" from somewhere. The \"Collection A\" is auto opened, and \"Doc A\" is activated.\r\n```\r\nCollection A -\r\nDoc A\r\nDoc B\r\n...\r\n```\n\n### Describe alternatives you've considered\n\n_No response_\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] 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.",[3088],{"name":3045,"color":3046},952,"Add support for auto opening the collapsed sidebar group when user enter any doc inside it","2023-01-21T14:28:58Z","https://github.com/vuejs/vitepress/issues/952",0.784835,{"description":3095,"labels":3096,"number":3098,"owner":3033,"repository":3034,"state":3080,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Describe the bug\n\n\r\n\r\nLook this. How bad is this? Ctrl+K placeholder is becoming ugly.\r\n\r\nWhen I see its code. It was an SVG code. When I refresh and then see there was no any SVG code.\n\n### Reproduction\n\nChanging some styles and doing fixes. \n\n### Expected behavior\n\n\r\n\r\nIt should look like this.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.22621 | Note: this is wrong. I use Windows 11.\r\n CPU: (12) x64 Intel(R) Core(TM) i5-10400F CPU @ 2.90GHz\r\n Memory: 7.50 GB / 15.90 GB\r\n Binaries:\r\n Node: 16.14.2 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.18 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.5.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22621.160.0), Chromium (103.0.1264.44)\r\n Internet Explorer: 11.0.22621.1\r\n\r\nNote: I don't believe this `envinfo` tool. Some of the above information may be incorrect.\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.",[3097],{"name":3045,"color":3046},909,"Searchbar placeholder style is becoming distorted.","2023-01-21T14:30:23Z","https://github.com/vuejs/vitepress/issues/909",0.79699934,{"description":3104,"labels":3105,"number":3106,"owner":3033,"repository":3034,"state":3080,"title":3107,"updated_at":3108,"url":3109,"score":3110},"\r\n\r\n\r\n[vitepress/guide/markdown/line-highlighting-in-code-blocks](https://vitepress.vuejs.org/guide/markdown#line-highlighting-in-code-blocks)\r\n\r\nI don't know if it is a mistake in doc, the space between 'code' and 'hl' is different. And I test the second one, it can't word actually.\r\nShould I make a PR? ",[],1549,"different space in doc ","2023-01-21T14:22:56Z","https://github.com/vuejs/vitepress/issues/1549",0.797317,{"description":3112,"labels":3113,"number":3115,"owner":3033,"repository":3034,"state":3080,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Describe the bug\r\n\r\nThe title bar can not completely cover sidebar texts.\r\n\u003Cimg width=\"271\" alt=\"81e7ba36bd7d0197428bcf36a31e0308\" src=\"https://user-images.githubusercontent.com/54239670/178223637-e59cb463-5d62-4a1f-bd46-643ed4096a16.png\">\r\n\r\n\r\n### Reproduction\r\n\r\n1. clone this repo\r\n2. run `pnpm install`\r\n3. run `pnpm build`\r\n4. run `pnpm docs-dev`\r\n5. open the page and then click `Guide`\r\n6. scroll the sidebar\r\n\u003Cimg width=\"271\" alt=\"81e7ba36bd7d0197428bcf36a31e0308\" src=\"https://user-images.githubusercontent.com/54239670/178223637-e59cb463-5d62-4a1f-bd46-643ed4096a16.png\">\r\n\r\n### Expected behavior\r\n\r\nThe title bar can completely cover the sidebar text.\r\n\u003Cimg width=\"276\" alt=\"dedb7f092bdd71196d7005e160b6b408\" src=\"https://user-images.githubusercontent.com/54239670/178226135-7ee1ac44-362a-45fa-8959-da037b0ad039.png\">\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 12.4\r\n CPU: (4) x64 Intel(R) Core(TM) i5-7360U CPU @ 2.30GHz\r\n Memory: 92.30 MB / 8.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 18.3.0 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 8.11.0 - /usr/local/bin/npm\r\n Browsers:\r\n Chrome: 103.0.5060.114\r\n Firefox: 91.4.1\r\n Safari: 15.5\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.",[3114],{"name":3045,"color":3046},962,"The title bar does not completely cover sidebar texts","2023-01-21T14:32:32Z","https://github.com/vuejs/vitepress/issues/962",0.80475825,{"description":3121,"labels":3122,"number":3126,"owner":3033,"repository":3034,"state":3080,"title":3127,"updated_at":3128,"url":3129,"score":3130},"### Describe the bug\r\n\r\nThe dev mode doesn't work/serve a working website.\r\n\r\nFirefox v105:\r\n\r\n````txt\r\nUncaught TypeError: import_meta.hot is undefined\r\n \u003Canonymous> http://localhost:5173/@fs/~/faker/node_modules/.pnpm/vitepress@1.0.0-alpha.17_w6dk4dwpgdxdglls4cxrxtpqg4/node_modules/vitepress/dist/client/theme-default/components/VPSkipLink.vue?v=341ae09c:51\r\n````\r\n\r\nChrome v105:\r\n\r\n```txt\r\nUncaught TypeError: Cannot read properties of undefined (reading 'accept')\r\n at VPSkipLink.vue:37:3\r\n```\r\n\r\nBuilding and serving (prod) works fine.\r\n\r\n### Reproduction\r\n\r\n````sh\r\ngit clone git@github.com:faker-js/faker.git\r\npnpm install\r\npnpm run build\r\npnpm run docs:dev\r\n# Open Browser\r\n````\r\n\r\n### Expected behavior\r\n\r\nA working website is shown.\r\n\r\n### System Info\r\n\r\n```shell\r\n System:\r\n OS: Windows 10 10.0.22621\r\n CPU: (16) x64 Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz\r\n Memory: 53.71 GB / 63.69 GB\r\n Binaries:\r\n Node: 16.17.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 8.16.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22621.521.0), Chromium (105.0.1343.53)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.17 => 1.0.0-alpha.17 \r\n```\r\n\r\n\r\n### Additional context\r\n\r\nFails with:\r\n- 1.0.0-alpha.17\r\n- 1.0.0-alpha.16\r\n- 1.0.0-alpha.15\r\n- 1.0.0-alpha.10\r\n- No more versions tested\r\n\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.",[3123],{"name":3124,"color":3125},"bug: pending triage","e99695",1422,"Dev mode not working","2023-01-21T14:25:17Z","https://github.com/vuejs/vitepress/issues/1422",0.8134851,["Reactive",3132],{},["Set"],["ShallowReactive",3135],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f402GfN4oWtbd5wE9DPTmYzAXAeuYP27f-2TAusGMPoc":-1},"/vuejs/vitepress/1483"]