\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,"vuejs","vitepress","open","Auto‑insert `\u003Ca.header‑anchor>` for headings rendered by Vue components","2025-07-30T19:09:15Z","https://github.com/vuejs/vitepress/issues/4867",0.75351125,{"description":3029,"labels":3030,"number":3031,"owner":3021,"repository":3022,"state":3032,"title":3033,"updated_at":3034,"url":3035,"score":3036},"### Describe the bug\n\nHello, thank you so much for vitepress — we are using it for https://observablehq.com/plot/\r\n\r\nCurrently we see that the instant search **detailed list** feature works in `docs:dev` but does not work with `docs:preview` (nor in production). \r\n\r\nWe are currently using v1.0.0-alpha.72, but I tried locally upgrading to v1.0.0-beta.1 and the issue is still here.\r\n\n\n### Reproduction\n\nClone https://github.com/observablehq/plot\r\nchange vitepress version to v1.0.0-beta.1 in package.json\r\nrun yarn; yarn docs:build; yarn docs:preview\r\nopen the site and search “color”\r\n\r\nscreenshot: left: docs:dev; right: docs:preview\r\n\r\n\r\n\n\n### Expected behavior\n\nThe detailed list should appear.\n\n### System Info\n\n```sh\nSystem:\r\n OS: macOS 13.3.1\r\n CPU: (8) arm64 Apple M1\r\n Memory: 63.64 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.1.0 - ~/.nvm/versions/node/v20.1.0/bin/node\r\n Yarn: 1.22.19 - /opt/homebrew/bin/yarn\r\n npm: 9.6.4 - ~/.nvm/versions/node/v20.1.0/bin/npm\r\n Browsers:\r\n Chrome: 114.0.5735.106\r\n Firefox: 113.0.2\r\n Safari Technology Preview: 16.4\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.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.",[],2485,"closed","Detailed list doesn't work with docs:preview (only works with docs:dev)","2023-06-15T00:04:10Z","https://github.com/vuejs/vitepress/issues/2485",0.73048836,{"description":3038,"labels":3039,"number":3046,"owner":3021,"repository":3022,"state":3032,"title":3047,"updated_at":3048,"url":3049,"score":3050},"### Describe the bug\n\n#1927 Here is the same problem, but it has not been solved yet. So, I gave an example to illustrate the issue. Particularly, all the anchors are in uppercase, and they cannot be jumped successfully, which is surprising.\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-721vib?file=docs/index.md\n\n### Expected behavior\n\nSince destination anchors are automatically converted to lowercase, it is hoped that source anchors can also be automatically converted to lowercase, so that they can match successfully\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz\r\n Memory: 3.28 GB / 15.87 GB\r\n Binaries:\r\n Node: 18.13.0 - D:\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.19.3 - D:\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (110.0.1587.63)\r\n Internet Explorer: 11.0.19041.1566\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.",[3040,3043],{"name":3041,"color":3042},"build","377ba8",{"name":3044,"color":3045},"theme","0754FB",2034,"the anchor doesn't work when source anchor is uppercase","2023-03-23T00:04:25Z","https://github.com/vuejs/vitepress/issues/2034",0.7401817,{"description":3052,"labels":3053,"number":3054,"owner":3021,"repository":3022,"state":3032,"title":3055,"updated_at":3056,"url":3057,"score":3058},"### Describe the bug\r\n\r\ncontent inside [] should not be parsed as html \r\n\r\n\r\n### Reproduction\r\n\r\njust use \r\n```\r\n[SimpleLink\u003CT>] (\"somewhere\")\r\n```\r\nin any md file\r\n\r\n### Expected behavior\r\n\r\nThe page should render even with \"Element is missing end tag\" when inside [ ]\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.19042\r\n CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz \r\n Memory: 16.55 GB / 31.88 GB\r\n Binaries:\r\n Node: 14.17.6 - C:\\Program Files\\nodejs\\node.EXE \r\n Yarn: 1.22.10 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 7.24.2 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 98.0.4758.102\r\n Edge: Spartan (44.19041.1266.0), Chromium (99.0.1150.30)\r\n Internet Explorer: 11.0.19041.1202\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.",[],576,"Element is missing end tag Error when used inside a link like [SimpleLink\u003CT>] (\"somewhere\")","2023-01-21T14:32:33Z","https://github.com/vuejs/vitepress/issues/576",0.75273573,{"description":3060,"labels":3061,"number":3065,"owner":3021,"repository":3022,"state":3032,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### Describe the bug\n\nThere are no issues in dev and build modes, but when deploy to GitHub Pages, the interface will duplicate the rendering of components, resulting in duplicate content. What could be the problem?Currently, the problem has only been found in one area of a page.\r\n\r\n\r\n\r\n\r\n\r\n\r\n\r\n\n\n### Reproduction\n\nUsing the Timeline component from Element UI.\n\n### Expected behavior\n\nNormal rendering.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (12) x64 Intel(R) Core(TM) i7-8750H CPU @ 2.20GHz \r\n Memory: 2.74 GB / 15.87 GB\r\n Binaries:\r\n Node: 18.13.0 - D:\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.19.3 - D:\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (110.0.1587.50)\r\n Internet Explorer: 11.0.19041.1566\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.",[3062],{"name":3063,"color":3064},"bug: pending triage","e99695",1973,"Deploy to GitHub Pages","2023-03-02T00:04:33Z","https://github.com/vuejs/vitepress/issues/1973",0.7569754,{"description":3071,"labels":3072,"number":3073,"owner":3021,"repository":3022,"state":3032,"title":3074,"updated_at":3075,"url":3076,"score":3077},"### Describe the bug\n\nAdding `[[toc]]` generates `div` inside `p` element and causes a hydration mismatch\n\n### Reproduction\n\n```md\r\n\r\n---\r\ntitle: Testing\r\n---\r\n\r\n[[toc]]\r\n\r\n## Test 1\r\n\r\ntest\r\n\r\n## Test 2\r\n\r\ntest\r\n\r\n```\r\nthis generates:\r\n```html\r\n...\r\n\u003Cp>\r\n\u003Cdiv class=\"table-of-contents\">\u003Cul>\u003Cli>\u003Ca href=\"#test-1\">Test 1\u003C/a>\u003C/li>\u003Cli>\u003Ca href=\"#test-2\">Test 2\u003C/a>\u003C/li>\u003C/ul>\u003C/div>\r\n\u003C/p>\r\n...\r\n```\r\nand a `div` element cannot be inside a `p` element so it causes a hydration mismatch when directly visiting the page\n\n### Expected behavior\n\nthe `div` should not be inside the `p`\n\n### System Info\n\n```shell\nSystem:\r\n OS: Linux 5.4 Alpine Linux\r\n CPU: (6) x64 Intel(R) Core(TM) i5-8400 CPU @ 2.80GHz\r\n Memory: 1.05 GB / 5.80 GB\r\n Container: Yes\r\n Shell: 1.32.1 - /bin/ash\r\n Binaries:\r\n Node: 16.8.0 - /usr/local/bin/node\r\n npm: 7.21.0 - /usr/local/bin/npm\r\n npmPackages:\r\n vitepress: ^0.16.1 => 0.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/coc)\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.",[],388,"Adding [[toc]] generates div inside p element and causes a hydration mismatch","2023-01-21T14:35:54Z","https://github.com/vuejs/vitepress/issues/388",0.7587785,{"description":3079,"labels":3080,"number":3082,"owner":3021,"repository":3022,"state":3032,"title":3083,"updated_at":3084,"url":3085,"score":3086},"### Describe the bug\n\nIf there is a plaintext file in public directory, and the file extension is unrecognized (i.e. `.txt` files are recognized, but `.ini`, or any random combination of file extensions, are not), the build system is attempting to convert the links to append `.html` to it. This causes the link to 404.\n\n### Reproduction\n\nNOTE: this reproduces a scenario in the testing environment. **docs:build doesn't even run because, as a result of the below generation, the link is being treated as dead.**\r\n\r\nAdd this to `/public/hello.ini`:\r\n```ini\r\n[helloworld]\r\n```\r\n\r\nAnd then have any page link to it like so:\r\n```md\r\n[download hello.ini](/hello.ini)\r\n```\r\n\r\nAnd it will generate:\r\n```html\r\n\u003Ca href=\"/hello.ini.html\">download hello.ini\u003C/a>\r\n```\r\n\n\n### Expected behavior\n\nThe docs seem to suggest that files in the `public` directory will be copied as-is to the output directory; the same logic should apply to links. That is to say, there should be no `.html` suffix in the `href` and either the download or the browser opening the resulting file in plaintext should proceed.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (12) x64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz\r\n Memory: 4.95 GB / 31.92 GB\r\n Binaries:\r\n Node: 20.11.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 10.2.4 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Chromium (127.0.2651.86)\r\n Internet Explorer: 11.0.19041.4355\r\n npmPackages:\r\n vitepress: ^1.3.4 => 1.3.4\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.",[3081],{"name":3063,"color":3064},4208,"Markdown absolute links to plaintext files in public directory attempts to link as HTML","2024-09-24T04:43:23Z","https://github.com/vuejs/vitepress/issues/4208",0.75882953,{"description":3088,"labels":3089,"number":3091,"owner":3021,"repository":3022,"state":3032,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Describe the bug\r\n\r\nPage outline will display any headings that has an `id` property. However, activelink only works if a heading has an `\u003Ca>` (anchor) child element.\r\n\r\nIn addition, the offset match fails if the heading is nested in a positioned (i.e. `position: relative`) parent element.\r\n\r\n\r\n### Reproduction\r\n\r\n#### [stackblitz playground](https://stackblitz.com/edit/github-zbjrsg-tsuanj)\r\n\r\n```markdown\r\n# All of the following headings are shown in outline, and can be clicked to jump.\r\n\r\n## (A) I am skipped, thanks to (C)\r\n\r\n\u003Ch2 id=\"B\">(B) I cannot be highlighted due to lack of anchor\u003C/h2>\r\n\r\n\u003Cdiv style=\"position: relative\">\r\n\r\n## (C) ActiveLink thinks my offset is 0.\r\n\r\n\u003C/div>\r\n\r\n## The last heading always works when scrolled to bottom.\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nEach of the heading above should get highlighted correctly.\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#### I've provided a fix here: #3368 \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.",[3090],{"name":3044,"color":3045},3378,"[default theme] activeAnchor inconsistent with outline when embedding html elements","2024-01-11T00:04:46Z","https://github.com/vuejs/vitepress/issues/3378",0.7604148,{"description":3097,"labels":3098,"number":3102,"owner":3021,"repository":3022,"state":3032,"title":3103,"updated_at":3104,"url":3105,"score":3106},"### Describe the bug\n\nLine breaks in Markdown source are incorrectly rendered as actual line breaks when a Markdown source line begins with an inline Vue component. Consider this component:\n```md\n\u003C!-- TestComponent.vue -->\n\u003Ctemplate>\n \u003Cspan style=\"display: inline; background-color: red\">TestComponent\u003C/span>\n\u003C/template>\n```\n...as well as the following Markdown:\n```md\n\u003CTestComponent /> This text, despite having\nline breaks in it, should still be\nrendered on a single line.\n\nBut it doesn't.\n```\nThis unexpectedly renders as follows:\n```\nTestComponent This text, despite having\n\nline breaks in it, should still be rendered on a single line.\n\nBut it doesn't.\n```\nNote that this does not happen if the Markdown line starts with a bit of text instead of with the Vue component:\n```md\nFor some reason, \u003CTestComponent /> this example\nrenders fine.\n```\n```\nFor some reason, TestComponent this example renders fine.\n```\n\n### Reproduction\n\n- Create a component with inline display style\n- Start a new Markdown paragraph with that component and continue across multiple Markdown lines\n - **There must be no text before the component**\n- The first line break within the Markdown source for that paragraph will render as an actual line break\n\nA repro is available here: https://stackblitz.com/edit/vite-xxlcwfge?file=docs%2Findex.md\n\n### Expected behavior\n\nThe line break in the Markdown source should not render as an actual line break. The example from above should render as follows:\n```\nTestComponent This text, despite having line breaks in it, should still be rendered on a single line.\n\nBut it doesn't.\n``` \n\n### System Info\n\n```Text\nSystem:\n OS: Windows 10 10.0.19045\n CPU: (8) x64 Intel(R) Core(TM) i7-9700K CPU @ 3.60GHz\n Memory: 4.86 GB / 15.94 GB\n Binaries:\n Node: 22.14.0 - C:\\Program Files\\nodejs\\node.EXE \n npm: 10.9.2 - C:\\Program Files\\nodejs\\npm.CMD \n Browsers:\n Edge: Spartan (44.19041.3636.0), Chromium (127.0.2651.74)\n Internet Explorer: 11.0.19041.3636\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\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.",[3099],{"name":3100,"color":3101},"upstream","BF29ED",4626,"Markdown lines starting with an inline Vue component are incorrectly considered to be a whole paragraph","2025-04-10T13:10:53Z","https://github.com/vuejs/vitepress/issues/4626",0.76154286,{"description":3108,"labels":3109,"number":3111,"owner":3021,"repository":3022,"state":3032,"title":3112,"updated_at":3113,"url":3114,"score":3115},"### Describe the bug\r\n\r\nThe header anchors are not accessible to screen reader users.\r\n\r\n```html\r\n\u003Ch1 id=\"what-is-vitepress\" tabindex=\"-1\">\r\n What is VitePress?\r\n \u003Ca class=\"header-anchor\" href=\"#what-is-vitepress\" aria-hidden=\"true\">#\u003C/a>\r\n\u003C/h1>\r\n```\r\n\r\nSetting `aria-hidden` on focusable elements (that are not hidden from **all** users) fails test \"[aria-hidden elements do not contain focusable elements](https://dequeuniversity.com/rules/axe/4.4/aria-hidden-focus?utm_source=lighthouse&utm_medium=devtools)\".\r\n\r\nI'm preparing a PR to fix this issue.\r\n\r\n### Reproduction\r\n\r\nNo special configuration necessary. Header anchors are enabled by default.\r\n\r\nThis issue can be tested on the official [VitePress](https://vitepress.vuejs.org/guide/what-is-vitepress) site or any other basic vitepress deployment using the default-theme.\r\n\r\n### Expected behavior\r\n\r\nProvide an accessible default configuration for `markdown-it-anchor` and update styling of header-anchors accordingly.\r\n\r\nA possible solution could look like this:\r\n\r\n```html\r\n\u003Cdiv class=\"header-wrapper\">\r\n \u003Ch1 id=\"what-is-vitepress\" tabindex=\"-1\">What is VitePress?\u003C/h1>\r\n \u003Ca class=\"header-anchor\" href=\"#what-is-vitepress\" aria-label=\"Permalink to \"What is VitePress?\"\">#\u003C/a>\r\n\u003C/div>\r\n```\r\n\r\nA viable `markdown-it-anchor` configuration could look like this.\r\n```js\r\n{\r\n anchor: {\r\n permalink: MdItAnchor.permalink.linkAfterHeader({\r\n style: \"aria-label\",\r\n assistiveText: (title) => `Permalink to \"${title}\"`,\r\n visuallyHiddenClass: \"visually-hidden\",\r\n wrapper: ['\u003Cdiv class=\"header-wrapper\">', \"\u003C/div>\"],\r\n }),\r\n },\r\n}\r\n```\r\n\r\nAdditionally, some updates for anchor styling are necessary too.\r\n```css\r\n.vp-doc .header-wrapper {\r\n position: relative;\r\n}\r\n\r\n.vp-doc .header-wrapper .header-anchor {\r\n line-height: 32px;\r\n position: absolute;\r\n top: 0;\r\n}\r\n\r\n.vp-doc .header-wrapper h1 + .header-anchor {\r\n line-height: 40px;\r\n font-size: 32px;\r\n}\r\n\r\n.vp-doc .header-wrapper h2 + .header-anchor {\r\n padding-top: 25px;\r\n line-height: 32px;\r\n font-size: 24px;\r\n}\r\n\r\n.vp-doc .header-wrapper h3 + .header-anchor {\r\n line-height: 28px;\r\n font-size: 20px;\r\n}\r\n\r\n.vp-doc .header-anchor:hover,\r\n.vp-doc .header-anchor:focus,\r\n.vp-doc h1:hover + .header-anchor,\r\n.vp-doc h2:hover + .header-anchor,\r\n.vp-doc h3:hover + .header-anchor,\r\n.vp-doc h4:hover + .header-anchor,\r\n.vp-doc h5:hover + .header-anchor,\r\n.vp-doc h6:hover + .header-anchor {\r\n opacity: 1;\r\n}\r\n```\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 20.04.5 LTS (Focal Fossa)\r\n CPU: (8) x64 Intel(R) Xeon(R) CPU E3-1505M v5 @ 2.80GHz\r\n Memory: 19.26 GB / 31.13 GB\r\n Container: Yes\r\n Shell: 5.0.17 - /bin/bash\r\nBinaries:\r\n Node: 18.14.0 - ~/.nvm/versions/node/v18.14.0/bin/node\r\n Yarn: 1.22.19 - ~/.nvm/versions/node/v18.14.0/bin/yarn\r\n npm: 9.3.1 - ~/.nvm/versions/node/v18.14.0/bin/npm\r\nBrowsers:\r\n Chrome: 110.0.5481.177\r\n Chromium: 110.0.5481.100\r\n Firefox: 110.0.1\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nMore details about test \"aria-hidden elements do not contain focusable elements\" can be found at [https://dequeuniversity.com/rules/axe/4.4/aria-hidden-focus](https://dequeuniversity.com/rules/axe/4.4/aria-hidden-focus).\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.",[3110],{"name":3044,"color":3045},2039,"Header anchors not accessible to screen reader users.","2023-03-22T00:03:24Z","https://github.com/vuejs/vitepress/issues/2039",0.7620429,["Reactive",3117],{},["Set"],["ShallowReactive",3120],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fDv4etmvRoc9SFNj94j4TMJnGwxQT16VMi4ttzLndGsY":-1},"/vuejs/vitepress/3133"]