\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.6885995,{"description":2876,"labels":2877,"number":2881,"owner":2868,"repository":2869,"state":2870,"title":2882,"updated_at":2883,"url":2884,"score":2885},"### Describe the bug\n\n选择一个侧边栏所包含的链接\n刷新后,侧边栏定位不会自动移动到相应位置。\n\n### Reproduction\n\njust like this doc website, https://vitepress.dev/zh/reference/default-theme-carbon-ads\nthe sidebar not auto locate the url responding sidebar_item\n\n### Expected behavior\n\nsidebar auto locate\n\n### System Info\n\n```Text\nthe lastest\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.",[2878],{"name":2879,"color":2880},"bug: pending triage","e99695",4579,"侧边栏不会自动定位到当前页面所对应的链接主题。","2025-02-25T11:45:05Z","https://github.com/vuejs/vitepress/issues/4579",0.71089417,{"description":2887,"labels":2888,"number":2889,"owner":2868,"repository":2869,"state":2890,"title":2891,"updated_at":2892,"url":2893,"score":2894},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\nUsing sidebar auto doesn't produce sidebar at all, even it is considered to be a valid option in https://github.com/vuejs/vitepress/blob/master/src/client/theme-default/config.ts.\r\n\r\n**To Reproduce**\r\n1. Create a new project\r\n2. Configure vitepress to use sidebar: 'auto' in .vitepress/config.js\r\n3. Create some pages with headings\r\n4. Start dev server\r\n\r\n**Expected behavior**\r\nA sidebar should be auto generated using the headings provided in the markdown files\r\n\r\n**System Info**\r\n- vitepress version: v0.9.1\r\n- vite version: v1.0.0-rc.13\r\n- Node version: v15.3.0\r\n- OS version: macOS 10.15.7 (19H2)\r\n",[],178,"closed","sidebar: 'auto' doesn't create sidebar","2023-01-21T14:20:42Z","https://github.com/vuejs/vitepress/issues/178",0.6931471,{"description":2896,"labels":2897,"number":377,"owner":2868,"repository":2869,"state":2890,"title":2901,"updated_at":2902,"url":2903,"score":2904},"### Is your feature request related to a problem? Please describe.\n\nCurrently sidebar depth can be specified per page in the frontmatter section. It would be convenient to set a global default sidebar depth in themeConfig. In situations where pages are auto-generated, adding the frontmatter block may not be so easy. \n\n### Describe the solution you'd like\n\nAdd support for `sidebarDepth` in `themeConfig`.\r\n\r\nSidebar depth specified in the frontmatter block should take priority over what's defined in `themeConfig`. If `sidebarDepth` is not defined, either in the page or in `themeConfig`, `Infinity` should be used to avoid breaking changes.\r\n\n\n### Describe alternatives you've considered\n\nThe default theme in vuepress supports setting sidebarDepth in sidebar groups as well, which could be nice, but I guess the most important is to have a global default available.\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] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/master/.github/contributing.md).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2898],{"name":2899,"color":2900},"theme","0754FB","Support setting sidebar depth in themeConfig for default theme","2023-01-21T14:32:50Z","https://github.com/vuejs/vitepress/issues/482",0.7021955,{"description":2906,"labels":2907,"number":2909,"owner":2868,"repository":2869,"state":2890,"title":2910,"updated_at":2911,"url":2912,"score":2913},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\nThe SideBar.js and NavBar.js components still reference `__DEV__` and should be replaced with `import.meta.env.DEV` to work with 0.4.0\r\n\r\n**To Reproduce**\r\nUse the default theme with 0.4.0\r\n\r\n**Expected behavior**\r\nNavBar and SideBar should not throw __DEV__ not defined errors\r\n\r\n**System Info**\r\n- vitepress version: 0.4.0\r\n- vite version: v1.0.0-beta.2\r\n- Node version:\r\n- OS version:\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2908],{"name":2879,"color":2880},28,"Sidebar Navbar break on 0.4.0","2023-01-21T16:25:39Z","https://github.com/vuejs/vitepress/issues/28",0.7044068,{"description":2915,"labels":2916,"number":2918,"owner":2868,"repository":2869,"state":2890,"title":2919,"updated_at":2920,"url":2921,"score":2922},"### Is your feature request related to a problem? Please describe.\n\nI've made a custom `Footer` component, but it doesn't show up very well with a sidebar.\r\nI see a sidebar conditional judgment in the 'VPFooter' component of the default theme.\r\n\r\n\n\n### Describe the solution you'd like\n\nIt would be nice to open it up.\r\n\r\n```\r\nimport { useSidebar } from 'vitepress'\r\n\r\nconst { hasSidebar } = useSidebar()\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.",[2917],{"name":2899,"color":2900},1176,"Provide useSidebar from vitepress","2023-06-29T00:04:28Z","https://github.com/vuejs/vitepress/issues/1176",0.7083653,{"description":2924,"labels":2925,"number":2926,"owner":2868,"repository":2869,"state":2890,"title":2927,"updated_at":2928,"url":2929,"score":2930},"### Is your feature request related to a problem? Please describe.\n\nGenerally, a lengthy docs page require \"on this page\" and most docs framework including gridsome docs, nuxt docs, docus, etc provide a third column \"on this page\" for navigating between the different section on the page.\r\n\r\nVuePress & VitePress provides the same \"on this page\" section in the left sidebar for that page when that page is opened but I guess making the left sidebar consistent across different pages will be a good choice.\n\n### Describe the solution you'd like\n\nAdding thrid column on right for on this page section instead of showing it in left sidebar.third\n\n### Describe alternatives you've considered\n\nI created my own theme.\r\n\r\nAnother alternative can be providing another three-column layout theme just like the default theme.\n\n### Additional context\n\nI know this is a big change so this is just thought as VitePress is still in its early stage.\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] Read the [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/master/.github/contributing.md).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],436,"Introducing three column column layout for \"on this page\" section","2023-01-21T16:04:16Z","https://github.com/vuejs/vitepress/issues/436",0.7099992,{"description":2932,"labels":2933,"number":2935,"owner":2868,"repository":2869,"state":2890,"title":2936,"updated_at":2937,"url":2938,"score":2939},"### 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.",[2934],{"name":2879,"color":2880},3485,"Using vue to report errors in markdown","2024-01-29T00:04:28Z","https://github.com/vuejs/vitepress/issues/3485",0.7138458,{"description":2941,"labels":2942,"number":2944,"owner":2868,"repository":2869,"state":2890,"title":2945,"updated_at":2946,"url":2947,"score":2948},"### Describe the bug\r\n\r\nWhile scrolling long pages with disabled sidebar, the header shows just a border with the color of --vp-c-gutter.\r\n\r\nOther pages with sidebar uses a curtain to smoothly soft the edge.\r\n\r\nThis inkonsistent usage of scrolling directly feels strange. Maybe not notices so far, because Vitepress site does not seem to have page without sidebar.\r\n\r\n### Reproduction\r\n\r\nJust use a long page and add the following frontmatter to it\r\n\r\n---\r\naside: false\r\noutline: false\r\n---\r\n\r\nand start scrolling\r\n\r\n### Expected behavior\r\n\r\nScrolling should behave konsistent on sidebar less page\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Windows 10 10.0.22621\r\n CPU: (12) x64 AMD Ryzen 5 3600 6-Core Processor\r\n Memory: 7.84 GB / 15.95 GB\r\n Binaries:\r\n Node: 18.16.1 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 9.5.1 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 116.0.5845.111\r\n Edge: Spartan (44.22621.2215.0), Chromium (116.0.1938.54)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.8 => 1.0.0-rc.8\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nMy current workaround inside custom.css:\r\n\r\nThese are the vp rules, but without ` .VPNavBar.has-sidebar` prefix.\r\n\r\n```css\r\n@media (min-width: 960px) {\r\n/* .VPNavBar.has-sidebar .curtain { */\r\n .VPNavBar .curtain {\r\n position: absolute;\r\n right: 0;\r\n bottom: -31px;\r\n /*width: calc(100% - var(--vp-sidebar-width));*/\r\n width: 100%;\r\n height: 32px;\r\n }\r\n}\r\n@media (min-width: 960px) {\r\n/* .VPNavBar.has-sidebar .curtain::before { */\r\n .VPNavBar .curtain::before {\r\n display: block;\r\n width: 100%;\r\n height: 32px;\r\n background: linear-gradient(var(--vp-c-bg), transparent 70%);\r\n content: \"\";\r\n }\r\n}\r\n```\r\nMaybe the final solution simply can be to remove `.has-sidebar` from code.\r\n\r\nAlso the default 'hard' gutter of #000000 disturbs a little bit the harmonic design.\r\n\r\nMy workaround solution is to use\r\n\r\n`--vp-c-gutter: transparent; `\r\n\r\nsince it is also used for the footer separation, and the visual separation is not nessassary for me.\r\n\r\nLive example usage on \r\n[btp.udina.de](https://btp.udina.de/about.html)\r\n\r\nBest regards\r\nHolger\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.",[2943],{"name":2899,"color":2900},2864,"Theme does not use header curtain on pages without sidebar","2023-09-05T00:04:11Z","https://github.com/vuejs/vitepress/issues/2864",0.71656466,{"description":2950,"labels":2951,"number":2952,"owner":2868,"repository":2869,"state":2890,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Is your feature request related to a problem? Please describe.\r\n\r\nThis is the translated issue for your convenience in reading!!!\r\n1. When scrolling the page content page anchors are not calibrated. I'm not sure if this is by design or if it's a problem. I found this problem when I was developing a custom theme.\r\n\r\n2. For example, when I enter the website, https://vitepress.dev/guide/what-is-vitepress I click on the anchor to successfully scroll to https://vitepress.dev/guide/what-is-vitepress#use-cases and then I scroll down when I want to. and then I scroll down when I want. The #use-cases here does not change. I press enter at the url to refresh, and scroll to my original #use-cases anchor, which causes the page to scroll to the anchor it's on, and then there's a return to the anchor that was at the start of the refresh If you don't understand what I'm saying,  \r\nPress enter and you see that the page will jump from the correct #use-cases anchor to the abnormal position.\r\n\r\nHere's the problem I'm seeing in comparison to vuepressX2.\r\n\r\n(3. Is there a good solution to this problem, when I use the new scrollbar to develop custom themes, I see the export function scrollTo scrollTo method used in router.js. It's all solved by using window.scrollTo(xxx,xxx). When I use a custom theme, for example, I use the component overlayscrollbars-vue. It has its own encapsulated scrollTo method instead of the dead window.scrollTo(xx,xxx,xx), what should I do with this, just rewrite the router-like method in layout.vue file to override it? I think it's a bit too much of a hassle and affects performance.\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\n1 2 I'm not sure if this is a bug, but I'd like to know. I'd also like to know if there's a good solution for issue 3. Currently in development, when you click on an anchor, you can write a window.addEventListener('click', (e) => { xxx scrollTo(xxx,xxx) }) and then encapsulate a scrollTo method. But #router is on the write side. It's a bit of a pain in the arse . Is there any possibility that vitepress can pass the parameter difference in config and then when developing a custom theme that involves scrollTo, it can be encapsulated and thrown to the developer to write the scrolling logic. That's a wild guess, and it might be a bit tricky. Or is there another way to improve this?\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.",[],2926,"the anchor may be a bug and a development issue with Custom Theme in scrollbar","2023-09-09T07:05:26Z","https://github.com/vuejs/vitepress/issues/2926",0.7191301,["Reactive",2958],{},["Set"],["ShallowReactive",2961],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fjcMrtqqpy-Ni-4tzGkcXAePJwFfOYe6oK26P3ieRzU4":-1},"/vuejs/vitepress/3426"]