\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,"Sidenav Components / Skip title update","2025-03-20T12:17:14Z","https://github.com/vuejs/vitepress/issues/4637",0.7186888,{"description":2890,"labels":2891,"number":2893,"owner":2874,"repository":2875,"state":2876,"title":2894,"updated_at":2895,"url":2896,"score":2897},"### Is your feature request related to a problem? Please describe.\r\n\r\nsuch as a vue components library site……\r\nA common problem for a documentation page is to show how to use a component, both in code and with demo of live component.\r\n\r\n### Describe the solution you'd like\r\n\r\nlike this [https://github.com/flingyp/vitepress-demo-preview](https://github.com/flingyp/vitepress-demo-preview)\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\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.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.",[2892],{"name":2871,"color":2872},3270,"Feature request: Vue component source code demo","2024-01-18T18:48:08Z","https://github.com/vuejs/vitepress/issues/3270",0.7261323,{"description":2899,"labels":2900,"number":2902,"owner":2874,"repository":2875,"state":2876,"title":2903,"updated_at":2904,"url":2905,"score":2906},"### 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.",[2901],{"name":2871,"color":2872},4253,"[Feature request] use vue render highlight section","2024-12-03T17:27:43Z","https://github.com/vuejs/vitepress/issues/4253",0.7374342,{"description":2908,"labels":2909,"number":2914,"owner":2874,"repository":2875,"state":2876,"title":2915,"updated_at":2916,"url":2917,"score":2918},"### Describe the bug\n\nI have a `/guide` path redirecting to one of first pages like `guide/product` and it works if I click action button, feature button or just change the route.\r\n\r\nHowever it doesn't work if I click a nav button\n\n### Reproduction\n\n```\r\nimport { defineConfig } from 'vitepress'\r\n\r\n// https://vitepress.dev/reference/site-config\r\nexport default defineConfig({ \r\n rewrites: {\r\n '/guide': \"guide/intro\"\r\n },\r\n themeConfig: {\r\n // https://vitepress.dev/reference/default-theme-config\r\n nav: [\r\n { text: 'Home', link: '/' },\r\n { text: 'Guide', link: '/guide' }\r\n ],\r\n\r\n sidebar: {\r\n\r\n \"/guide\": [\r\n {\r\n text: 'Introduction',\r\n items: [\r\n { text: 'Intro?', link: '/guide/intro/' },\r\n ]\r\n },\r\n]\r\n\r\n }\r\n }\r\n\r\n)\r\n```\n\n### Expected behavior\n\nI expect that clicking a link in the nav would handle it same way as it handles it everywhere else on the site\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 5.15 Debian GNU/Linux 12 (bookworm) 12 (bookworm)\r\n CPU: (2) x64 12th Gen Intel(R) Core(TM) i7-1265U\r\n Memory: 7.76 GB / 11.69 GB\r\n Container: Yes\r\n Shell: 5.2.15 - /bin/bash\r\n Binaries:\r\n Node: 22.9.0 - /usr/local/bin/node\r\n Yarn: 1.22.22 - /usr/local/bin/yarn\r\n npm: 10.8.3 - /usr/local/bin/npm\r\n pnpm: 9.12.1 - /usr/local/share/npm-global/bin/pnpm\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.",[2910,2913],{"name":2911,"color":2912},"bug: pending triage","e99695",{"name":2871,"color":2872},4364,"Links in the Nav bar do not support rewrites","2024-12-27T13:10:18Z","https://github.com/vuejs/vitepress/issues/4364",0.7451512,{"description":2920,"labels":2921,"number":2923,"owner":2874,"repository":2875,"state":2876,"title":2924,"updated_at":2925,"url":2926,"score":2927},"### Is your feature request related to a problem? Please describe.\r\n\r\nWe would like to have a way to easy navigate between home page and subpages.\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\nNow, when we press on [Nav](https://vitepress.dev/reference/default-theme-nav) element it points to the home page. It would be useful to have a way to set a link to that element\r\n - Add `nav-link` to be used when you are on home page\r\n - Add `nav-sub-link` to be used when you are on subpage, and if not defined is equal to `nav-link`\r\n\r\nIn that way, we can easy navigate between home and subpages by press on same element. For example\r\n```javascript\r\nexport default {\r\n themeConfig: {\r\n nav: [\r\n { nav-link: '/markdown-examples'},\r\n { nav-sub-link: '/'},\r\n { text: 'Markdown Examples', link: '/markdown-examples' }\r\n ]\r\n }\r\n}\r\n```\r\n\r\n### Describe alternatives you've considered\r\n\r\nNo alternatives right now?\r\n\r\n### Additional context\r\n\r\nAnd example about how it works now\r\n\r\nhttps://github.com/user-attachments/assets/df4e051b-242c-4cbe-a3bd-8fa39ba25848\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.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.",[2922],{"name":2871,"color":2872},4232,"Make Nav URL customisable for home page and subpages","2024-12-03T17:27:48Z","https://github.com/vuejs/vitepress/issues/4232",0.74637717,{"description":2929,"labels":2930,"number":2937,"owner":2874,"repository":2875,"state":2938,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Describe the bug\n\nHi there,\r\n\r\nI want to extend the default theme layout by using '#nav-screen-content-after' slot, but if the screen size is between [768,1280) px, '#nav-screen-content-after' slot does not work.\r\nI suppose all nav slots don't work when the window resize to [768,1280) px.\r\nPlease help fix the issue.\r\n\r\nThanks\n\n### Reproduction\n\n1.Add '#nav-screen-content-after' layout slot according to https://vitepress.dev/guide/extending-default-theme#layout-slots.\r\n2.Resize screen to [768,1280) px.\r\n3.Nav layout slot component will disappear.\n\n### Expected behavior\n\nResize screen to [768,1280) px and the added layout slot component should be still exist.\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 14.3.1\r\n Binaries:\r\n Node: 21.7.1 - ~/.nvm/versions/node/v21.7.1/bin/node\r\n npm: 10.5.0 - ~/.nvm/versions/node/v21.7.1/bin/npm\r\n pnpm: 8.15.5 - ~/.nvm/versions/node/v21.7.1/bin/pnpm\r\n Browsers:\r\n Chrome: 123.0.6312.107\r\n Safari: 17.3.1\r\n npmPackages:\r\n vitepress: ^1.1.0 => 1.1.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.",[2931,2934],{"name":2932,"color":2933},"need more info","bdbefc",{"name":2935,"color":2936},"has-workaround","1B4515",3773,"closed","'#nav-screen-content-after' does not work when screen width between [768,1280)","2024-05-08T04:41:54Z","https://github.com/vuejs/vitepress/issues/3773",0.69791156,{"description":2944,"labels":2945,"number":2947,"owner":2874,"repository":2875,"state":2938,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Describe the bug\n\nExecute command npm run docs:build and throw an exception: build error:\r\nTypeError: Intl.Segmenter is not a constructor\r\n\n\n### Reproduction\n\n.vitepress config.ts\r\n```\r\nimport { defineConfig } from 'vitepress'\r\n\r\nexport default defineConfig({\r\n lang: 'en-US',\r\n lastUpdated: true,\r\n cleanUrls: true,\r\n\r\n themeConfig: {\r\n\r\n nav: nav(),\r\n\r\n sidebar: {\r\n '/rest-api/': sidebarRestApi(),\r\n }\r\n }\r\n})\r\n```\r\n\r\npackage.json\r\n```\r\n\"scripts\": {\r\n \"dev:docs\": \"npx vitepress dev docs\",\r\n \"build:docs\": \"npx vitepress build docs\",\r\n \"serve:docs\": \"npx vitepress serve docs\"\r\n },\r\n \"dependencies\": {\r\n \"vue\": \"^3.3.4\"\r\n },\r\n \"devDependencies\": {\r\n \"vitepress\": \"^1.0.0-rc.4\"\r\n }\r\n```\n\n### Expected behavior\n\nnpm run build:docs\n\n### System Info\n\n```sh\nnpx vitepress build docs\r\n\r\nvitepress v1.0.0-rc.4\r\n\r\nbuild error:\r\nTypeError: Intl.Segmenter is not a constructor\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.",[2946],{"name":2932,"color":2933},2817,"Vitepress build error","2023-08-27T00:06:17Z","https://github.com/vuejs/vitepress/issues/2817",0.707078,{"description":2953,"labels":2954,"number":2955,"owner":2874,"repository":2875,"state":2938,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Is your feature request related to a problem? Please describe.\r\n\r\nRight now (unless I'm not understanding the correct method) it seems difficult to override core theme componentry. Say I want to edit the NavBar template; I have to either write a completely new implementation from scratch (sacrificing a lot of features built in to the framework like the hamburger menu, and the configurable data expressed to navbar links, logo image, site title, etc. This seems to be because those components are part of the core library and not exported anywhere to be reused, so there's a big block of reused components like\r\n```\r\n\u003CVPNavBarSearch class=\"search\" />\r\n\u003CVPNavBarMenu class=\"menu\" />\r\n\u003CVPNavBarTranslations class=\"translations\" />\r\n\u003CVPNavBarAppearance class=\"appearance\" />\r\n\u003CVPNavBarSocialLinks class=\"social-links\" />\r\n\u003CVPNavBarExtra class=\"extra\" />\r\n\u003Cslot name=\"nav-bar-content-after\" />\r\n\u003CVPNavBarHamburger class=\"hamburger\" :active=\"isScreenOpen\" @click=\"$emit('toggle-screen')\" />\r\n```\r\nand those would either have to be copied and/or reimplemented inside my project if all I wanted to do, for example, was put the site title/logo in the middle of the navbar instead of the left side.\r\n\r\n### Describe the solution you'd like\r\n\r\nI'm still learning Vue, but it seems like if these core theme components could be exported from the vitepress library, they could be imported instead of reimplemented if all I wanted to do was copy the NavBar template and edit it a bit.\r\n\r\n### Describe alternatives you've considered\r\n\r\nThe alternative right now seems to be either copying all these theme files into my project, reimplementing them, or not using them and sacrificing their utility.\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.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.",[],2976,"Easier Overriding of Internal Components","2023-10-03T00:04:19Z","https://github.com/vuejs/vitepress/issues/2976",0.7189539,{"description":2961,"labels":2962,"number":2966,"owner":2874,"repository":2875,"state":2938,"title":2967,"updated_at":2968,"url":2969,"score":2970},"### Is your feature request related to a problem? Please describe.\n\nI would like to have to collapsible navigation sidebar since I organize my documents by using multiple layers of folders, which is frustrating to browse or lookup the content/page I want.\r\n\r\nVitePress only supports the top-level folders to be collapsible in the navigation sidebar currently.\n\n### Describe the solution you'd like\n\nThe default theme that VitePress provided could support multi-level sidebar to be collapsible since many of the people may also face such kind of the problem while using VitePress.\n\n### Describe alternatives you've considered\n\nI have tried to override the `VPSidebarNav` component from default theme that VitePress provided, however, the theme configuration overridding is not supported currently (related issue is still open, ref: #235 ), or I would have to duplicate the default theme as a single repository and publish it as a npm package after the development is done by myself. Anyways, I may think this kind of the feature is general for most of the users, it should be provided by VitePress, nor by users.\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.",[2963],{"name":2964,"color":2965},"theme","0754FB",1360,"Add support for collapsible multi-level sidebar","2023-02-01T00:04:34Z","https://github.com/vuejs/vitepress/issues/1360",0.73069555,["Reactive",2972],{},["Set"],["ShallowReactive",2975],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fL58ZSc8SRseGALCzBIE361kJh6r-Vw-VJL72vIxDLns":-1},"/vuejs/vitepress/3714"]