\n\n\u003Cimg width=\"308\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/0e1beb6b-d06b-436c-b106-c924fead87ab\" />\n\n\u003Cimg width=\"931\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/aef6f71a-fa28-4b7c-b512-e6386e18159a\" />\n\n### Describe the solution you'd like\n\nIn my [pull request](https://github.com/vuejs/vitepress/pull/4630), I've introduced custom components that can be overridden in the `enhanceApp` function. In these custom components, I can add custom logic for rendering text, such as using the Vue compile function. \n\nAdditionally, I added a flag to skip the title update, allowing for custom logic implementation. \n\nPlease also see my PR: [https://github.com/vuejs/vitepress/pull/4630](https://github.com/vuejs/vitepress/pull/4630).\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.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.",[],4637,"vuejs","vitepress","open","Sidenav Components / Skip title update","2025-03-20T12:17:14Z","https://github.com/vuejs/vitepress/issues/4637",0.6915772,{"description":2876,"labels":2877,"number":2881,"owner":2868,"repository":2869,"state":2870,"title":2882,"updated_at":2883,"url":2884,"score":2885},"### Is your feature request related to a problem? Please describe.\n\n1. sometimes need use vue dynamic render highlight content like json list or some thing . if can provide component or function to do that, that will be great.\r\n2. tryed use the vue dynamic component it's not woking , can we use it ? how.\r\n1.有时候需要动态输出 markdown ,能不能加一个从vue 动态输出的功能 。 2. 动态组件用不了,怎么才能用vue 的动态组件\n\n### Describe the solution you'd like\n\n1. sometimes need use vue dynamic render highlight content like json list or some thing . if can provide component or function to do that, that will be great.\r\n2. tryed use the vue dynamic component it's not woking , can we use it ? how.\r\n1.有时候需要动态输出 markdown ,能不能加一个从vue 动态输出的功能 。 2. 动态组件用不了,怎么才能用vue 的动态组件\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.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.",[2878],{"name":2879,"color":2880},"stale","ededed",4253,"[Feature request] use vue render highlight section","2024-12-03T17:27:43Z","https://github.com/vuejs/vitepress/issues/4253",0.71441627,{"description":2887,"labels":2888,"number":2893,"owner":2868,"repository":2869,"state":2870,"title":2894,"updated_at":2895,"url":2896,"score":2897},"When clicking on a page, the sidebar on the left cannot automatically scroll to the current page and needs to scroll some more on its own.\r\nIf there are many things on the sidebar, it may take a long time to scroll. I checked some official documents related to the Vue series and found that many of them use vitepress, and similar things happen.\r\nAt first, I thought it was a matter of the version, but later I tried it myself and found that the new version didn't work either.\r\n\r\nSo is this a feature that can be considered for addition? I think it would be very helpful.\r\n\r\n### at first\r\n\u003Cimg width=\"1232\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/103993866/744ed1b9-157a-4692-9152-d4f3e4dd725c\">\r\n\r\n### after scrolling in the left area\r\n\u003Cimg width=\"1262\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/103993866/4b7622fe-49dd-4862-8d47-b9a954210d86\">\r\n\r\n### Describe the solution you'd like\r\n\r\nIn the sidebar area on the left, make it automatically display the title of the current page.\r\n\r\n### Describe alternatives you've considered\r\n\r\nIf given the opportunity, I hope to contribute to this feature together.\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.",[2889,2892],{"name":2890,"color":2891},"theme","0754FB",{"name":2879,"color":2880},3426,"feat: cannot automatically top the current page","2025-03-02T18:09:56Z","https://github.com/vuejs/vitepress/issues/3426",0.7250975,{"description":2899,"labels":2900,"number":2902,"owner":2868,"repository":2869,"state":2870,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### Is your feature request related to a problem? Please describe.\n\nMy CMS stores markdown values in frontmatter data. For example, an intro section `intro` with a markdown string value. Currently, trying to access it in the page with `{{ $frontmatter.intro }}` just renders it as a string (a direct result of the markdown -> Vue -> HTML pipeline). What is the recommended way to call the markdown parser on it?\n\n### Describe the solution you'd like\n\nIt would be nice to see this exposed somehow (getting the built-in markdown-it instance, for example).\n\n### Describe alternatives you've considered\n\nI could install markdown-it separately and use it that way?\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.",[2901],{"name":2879,"color":2880},2410,"Expose the built-in markdown parser to render markdown-valued variables with","2024-02-02T09:23:30Z","https://github.com/vuejs/vitepress/issues/2410",0.73114073,{"description":2908,"labels":2909,"number":2910,"owner":2868,"repository":2869,"state":2911,"title":2912,"updated_at":2913,"url":2914,"score":2915},"### Is your feature request related to a problem? Please describe.\n\nI'm using Vue components that generate headers dynamically, and (of course) the headers I create in Vue components don't appear in the outline.\n\n### Describe the solution you'd like\n\nI'd like to be able to add headers to `page.headers` in my component.\n\n### Describe alternatives you've considered\n\nI tried manipulating `page.headers` in my component from `useData()`, but the headers are read-only at that point.\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.",[],1145,"closed","Dynamic Outline","2023-01-21T14:26:54Z","https://github.com/vuejs/vitepress/issues/1145",0.68551695,{"description":2917,"labels":2918,"number":2922,"owner":2868,"repository":2869,"state":2911,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Describe the bug\n\nI want to use the vue component in vitepress. I have read the documentation on the official website, but when I do it, I encounter an error like this.\r\n```bash\r\n[plugin:vite:vue] Tags with side effect (\u003Cscript> and \u003Cstyle>) are ignored in client component templates.\r\n```\r\n\r\nI don't understand what I'm encountering, I just want to achieve the effect here in this vue document\r\n\r\n> https://cn.vuejs.org/guide/reusability/composables.html#vs-react-hooks\r\n\r\n\r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-dn63jg?file=docs%2Fhooks%2FuseMouse.js,docs%2Fexample.md\n\n### Expected behavior\n\nThe documentation on the official website makes me understand the difficulty or the need for a better demo?\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 11 10.0.22631\r\n CPU: (20) x64 13th Gen Intel(R) CoreT i7-13800H\r\n Memory: 17.07 GB / 31.74 GB\r\n Binaries:\r\n Node: 20.11.0 - ~\\AppData\\Local\\pnpm\\node.EXE\r\n npm: 10.2.4 - ~\\AppData\\Local\\pnpm\\npm.CMD\r\n pnpm: 8.14.1 - ~\\AppData\\Local\\pnpm\\pnpm.EXE\r\n Browsers:\r\n Edge: Chromium (120.0.2210.133)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: 1.0.0-rc.39 => 1.0.0-rc.39\n```\n\n\n### Additional context\n\nPlease tell me the correct way to write it, thank you\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.",[2919],{"name":2920,"color":2921},"bug: pending triage","e99695",3485,"Using vue to report errors in markdown","2024-01-29T00:04:28Z","https://github.com/vuejs/vitepress/issues/3485",0.7008417,{"description":2928,"labels":2929,"number":2931,"owner":2868,"repository":2869,"state":2911,"title":2932,"updated_at":2933,"url":2934,"score":2935},"### Describe the bug\r\n\r\nMarkdown on the home page does not have the correct article style\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\n```md\r\n---\r\nlayout: home\r\n\r\nhero:\r\n name: VuePress\r\n text: Vite & Vue powered static site generator.\r\n tagline: Lorem ipsum...\r\n actions:\r\n - theme: brand\r\n text: Get Started\r\n link: /guide/what-is-vitepress\r\n - theme: alt\r\n text: View on GitHub\r\n link: https://github.com/vuejs/vitepress\r\n\r\nfeatures:\r\n - icon: ⚡️\r\n title: Vite, The DX that can't be beat\r\n details: Lorem ipsum...\r\n - icon: 🖖\r\n title: Power of Vue meets Markdown\r\n details: Lorem ipsum...\r\n - icon: 🛠️\r\n title: Simple and minimal, always\r\n details: Lorem ipsum...\r\n---\r\n\r\n# H1\r\nhello world\r\n## H2\r\nhello world\r\n### H3\r\nhello world\r\n\r\n```sh\r\nnpm i -g vitepress\r\n\\```\r\n```\r\n\r\n\r\n### Expected behavior\r\n\r\nHomePage markdown have the right Style Like docs\r\n\r\n\r\n\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 11.2.3\r\n CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz\r\n Memory: 716.61 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 14.19.1 - ~/.nvm/versions/node/v14.19.1/bin/node\r\n Yarn: 1.22.18 - ~/.nvm/versions/node/v14.19.1/bin/yarn\r\n npm: 6.14.16 - ~/.nvm/versions/node/v14.19.1/bin/npm\r\n Watchman: 2021.06.07.00 - /usr/local/bin/watchman\r\n Browsers:\r\n Chrome: 102.0.5005.115\r\n Edge: 102.0.1245.41\r\n Safari: 14.0.3\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.2 => 1.0.0-alpha.2\r\n```\r\n\r\n\r\n### Additional context\r\n\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.",[2930],{"name":2890,"color":2891},800,"Markdown Style on the Homepage does not work properly","2024-02-25T00:05:03Z","https://github.com/vuejs/vitepress/issues/800",0.70296407,{"description":2937,"labels":2938,"number":2939,"owner":2868,"repository":2869,"state":2911,"title":2940,"updated_at":2941,"url":2942,"score":2943},"### Is your feature request related to a problem? Please describe.\n\nH2, H3 headings currently written in vue cannot be shown in outline,\n\n### Describe the solution you'd like\n\nor can we get a useData add header provided\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.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.",[],3103,"Can you identify the H tag in the outline display using vue file in md?","2023-10-27T00:04:15Z","https://github.com/vuejs/vitepress/issues/3103",0.70441055,{"description":2945,"labels":2946,"number":2950,"owner":2868,"repository":2869,"state":2911,"title":2951,"updated_at":2952,"url":2953,"score":2954},"### Describe the bug\r\n\r\nSome of the code markdown extensions do not work when the language is `vue`.\r\n\r\nIn particular, `[!code ++]`, `[!code --]`, `[!code warning]`, `[!code error]` and `[!code focus]` just show the comments at the end of the line.\r\n\r\nChanging the language to something else fixes this, e.g. `htmx` or `ts`.\r\n\r\nThis only seems to happen in the template tags of a `vue` code block. The highlighting works absolutely fine in the script part. Please see reproduction for code examples, I can't figure out how to escape the triple backtick code blocks here! ☹️ \r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-arupmh?file=docs%2Fexample.md\r\n\r\n### Expected behavior\r\n\r\nThe markdown extensions should work correctly and highlight the lines as per [the docs](https://vitepress.dev/guide/markdown#focus-in-code-blocks).\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 14.1.2\r\n CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 488.47 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\nBinaries:\r\n Node: 18.12.1 - ~/.nvm/versions/node/v18.12.1/bin/node\r\n Yarn: 1.22.10 - /usr/local/bin/yarn\r\n npm: 8.19.2 - ~/.nvm/versions/node/v18.12.1/bin/npm\r\nBrowsers:\r\n Chrome: 120.0.6099.234\r\n Firefox: 112.0.2\r\n Firefox Developer Edition: 107.0\r\n Safari: 17.1.2\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.",[2947],{"name":2948,"color":2949},"upstream","BF29ED",3503,"Markdown code extensions don't work in some situations","2025-02-01T04:42:47Z","https://github.com/vuejs/vitepress/issues/3503",0.71060646,{"description":2956,"labels":2957,"number":2961,"owner":2868,"repository":2869,"state":2911,"title":2962,"updated_at":2963,"url":2964,"score":2965},"### Is your feature request related to a problem? Please describe.\n\nImagine the use case:\r\n\r\nThere are some settings on the left side (just like `vuejs.org`'s API style switch), but I want it to show/hide some `h2` or `h3`, or say, those heading elements which will be in the aside.\r\n\r\nBy wrapping entire `h2` or `h3` parts by a `\u003Cdiv>` and using classes on the root element to control their visibility based on the value of settings. However, currently, the aside content won't update in this case.\r\n\r\n---\r\n\r\nIf you don't want this to be part of the default theme, please inform me and close this issue, Thanks.\n\n### Describe the solution you'd like\n\nI'm here to gather whether you want this to be a feature in the default theme, as I already implemented it by overriding internal files (that's a bit frustrating honestly) and it's working well for me, so I can raise the MR if you would like to accept this feature as part of the default theme.\r\n\r\nMy implementation in high-level:\r\n1. In those aside components (i.e. `VPDocAsideOutline.vue`, `VPDocOutlineDropdown.vue` and `VPLocalNav.vue`\r\n2. Using `IntersectionObserver` to observe the visibility against root (`\u003Chtml>`)\r\n3. Once change is detected, regenerate the headers and cleanup + apply step 2 again.\r\n\r\nPlease feel free to advise if you have a better approach.\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.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.",[2958],{"name":2959,"color":2960},"need more info","bdbefc",2686,"✨Feature: Re-generate aside content when visbility of anchor headings change","2023-08-11T00:04:06Z","https://github.com/vuejs/vitepress/issues/2686",0.71194565,["Reactive",2967],{},["Set"],["ShallowReactive",2970],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$frUx5nmj8lTrXhha_wZdLlDhn4V2FppQ_L4_gJ2i728M":-1},"/vuejs/vitepress/785"]