\r\n \u003CEmpty />\r\n \u003C/div>\r\n\u003C/template>\r\n\u003Cscript lang=\"ts\" setup>\r\nimport { Empty } from 'ant-design-vue';\r\nimport { ref } from \"vue\"\r\nconst visible = ref(true)\r\n\r\nconst handleClick = () => {\r\n visible.value = !visible.value\r\n\r\n}\r\n\u003C/script>\r\n\r\n```\r\n\n\n### Reproduction\n\n# Steps\r\n1. build. \r\nvitepress build docs.\r\n2. serve.\r\nvitepress serve docs. \r\n3. Click Button in the page.\r\n\r\n\r\n# Problem I face \r\nEverything is normal at the first.But when I click the button to change the element in the page, 'Empty' component cannot be rendered.\r\n\u003Cimg width=\"1672\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/43191187/00a0982a-5c11-47bc-adad-8e887380493a\">\r\n\n\n### Expected behavior\n\n# Expected. \r\nNo matter re-render times, I hope it can be rendered normal.\r\n\r\n\u003Cimg width=\"1676\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/43191187/74275c38-190d-49b5-a53a-4f23e2d123c7\">\r\n\n\n### System Info\n\n```Text\nThere's no any extra info.\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.",[3074],{"name":3075,"color":3076},"bug: pending triage","e99695",3718,"closed","ant-design-vue some components cannot render twice under vitepress build.","2024-04-28T12:25:19Z","https://github.com/vuejs/vitepress/issues/3718",0.79800636,{"description":3084,"labels":3085,"number":3091,"owner":3033,"repository":3034,"state":3078,"title":3092,"updated_at":3093,"url":3094,"score":3095},"### Describe the bug\r\n\r\nI am trying to use vite [alias overwrite component](https://vitepress.dev/guide/extending-default-theme#overriding-internal-components). Such as `VPNavbar`. Works fine in the page display\r\n\r\nBut after building I found that the `dist/assets/style.css` file still retains the styles in the component that origin component style.\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-vfhomn?file=docs%2F.vitepress%2Fconfig.ts\r\n\r\n`npm run build` and check style file `dist/assets/style.css`\r\n\r\n\u003Cimg width=\"1624\" alt=\"image\" src=\"https://github.com/vuejs/vitepress/assets/40693636/85469507-fa9b-4e8f-b76a-a2ee2fc86bbb\">\r\n\r\n\r\n### Expected behavior\r\n\r\nRemove origin component's style\r\n\r\n### System Info\r\n\r\n```Text\r\nSystem:\r\n OS: macOS 13.4.1\r\n CPU: (8) arm64 Apple M1 Pro\r\n Memory: 115.05 MB / 16.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 16.20.1 - /opt/homebrew/opt/node@16/bin/node\r\n Yarn: 1.22.19 - /opt/homebrew/bin/yarn\r\n npm: 8.19.4 - /opt/homebrew/opt/node@16/bin/npm\r\n Browsers:\r\n Chrome: 116.0.5845.179\r\n Safari: 16.5.2\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI'm not sure if this is a bug or the vite alias design, but it's look like not a perfect overwrite. I want to get a css asset as small as possible.\r\n\r\nIf there is a configuration that can be removed, welcome share with me. 🙌\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.",[3086,3087,3090],{"name":3075,"color":3076},{"name":3088,"color":3089},"has-workaround","1B4515",{"name":3030,"color":3031},2945,"Vite alias overwrite component. The origin component css save in bundler assert.","2024-05-05T04:41:48Z","https://github.com/vuejs/vitepress/issues/2945",0.80027753,{"description":3097,"labels":3098,"number":3101,"owner":3033,"repository":3034,"state":3078,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Is your feature request related to a problem? Please describe.\n\nWithout auto-wrap, I have to drag horizontally to view the text in the code block, which is a pain in the ass!\n\n### Describe the solution you'd like\n\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.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.",[3099,3100],{"name":3044,"color":3045},{"name":3030,"color":3031},3307,"How to set auto-warp column in code blocks like docusaurus?","2024-02-23T00:05:11Z","https://github.com/vuejs/vitepress/issues/3307",0.8063068,{"description":3107,"labels":3108,"number":3109,"owner":3033,"repository":3034,"state":3078,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### Is your feature request related to a problem? Please describe.\n\nI don't know if there's an already existing solution, but I try to rename a file according to the parent's folder\n\n### Describe the solution you'd like\n\nHere is an example:\r\n`/foo/bar/bar.md -> /foo/bar/index.md`\n\n### Describe alternatives you've considered\n\nI tried to create rewrite rules, something like that:\r\n`\":dir/:dir.md\": \":dir/index.md\"`\r\n\r\nBut it's not working\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.",[],3453,"Rename file that match parent folder name","2024-01-23T00:04:55Z","https://github.com/vuejs/vitepress/issues/3453",0.80885446,{"description":3115,"labels":3116,"number":3121,"owner":3033,"repository":3034,"state":3078,"title":3122,"updated_at":3123,"url":3124,"score":3125},"### Is your feature request related to a problem? Please describe.\n\nFind myself wanting to use VPButton and VPSponsors on a few places throughout my site. Right now, I exported them through a patch, but would great if they were exported by default.\n\n### Describe the solution you'd like\n\nVPButton and VPSponsors exported.\n\n### Describe alternatives you've considered\n\nCurrently use the following patch:\r\n\r\n```diff\r\ndiff --git a/dist/client/theme-default/without-fonts.js b/dist/client/theme-default/without-fonts.js\r\nindex 2b760aa398b7ac1881551ab146d7d308ef2277a3..a2940ca0b99b7673d8914e4bf332f57c588e8f46 100644\r\n--- a/dist/client/theme-default/without-fonts.js\r\n+++ b/dist/client/theme-default/without-fonts.js\r\n@@ -11,10 +11,12 @@ import Layout from './Layout.vue';\r\n // Note: if we add more optional components here, i.e. components that are not\r\n // used in the theme by default unless the user imports them, make sure to update\r\n // the `lazyDefaultThemeComponentsRE` regex in src/node/build/bundle.ts.\r\n+export { default as VPButton } from './components/VPButton.vue';\r\n export { default as VPHomeHero } from './components/VPHomeHero.vue';\r\n export { default as VPHomeFeatures } from './components/VPHomeFeatures.vue';\r\n export { default as VPHomeSponsors } from './components/VPHomeSponsors.vue';\r\n export { default as VPDocAsideSponsors } from './components/VPDocAsideSponsors.vue';\r\n+export { default as VPSponsors } from './components/VPSponsors.vue';\r\n export { default as VPTeamPage } from './components/VPTeamPage.vue';\r\n export { default as VPTeamPageTitle } from './components/VPTeamPageTitle.vue';\r\n export { default as VPTeamPageSection } from './components/VPTeamPageSection.vue';\r\ndiff --git a/theme.d.ts b/theme.d.ts\r\nindex 4b1076b5fbda893eb6f4a5df6a40c15d1bb379ba..177f5a6aa9602e0eeae954137bcce1ac0080ddef 100644\r\n--- a/theme.d.ts\r\n+++ b/theme.d.ts\r\n@@ -3,10 +3,12 @@ import type { DefineComponent } from 'vue'\r\n import { EnhanceAppContext } from './dist/client/index.js'\r\n \r\n // TODO: add props for these\r\n+export const VPButton: DefineComponent\r\n export const VPHomeHero: DefineComponent\r\n export const VPHomeFeatures: DefineComponent\r\n export const VPHomeSponsors: DefineComponent\r\n export const VPDocAsideSponsors: DefineComponent\r\n+export const VPSponsors: DefineComponent\r\n export const VPTeamPage: DefineComponent\r\n export const VPTeamPageTitle: DefineComponent\r\n export const VPTeamPageSection: DefineComponent\r\n```\n\n### Additional context\n\nHappy to open a PR for this!\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.",[3117,3118],{"name":3044,"color":3045},{"name":3119,"color":3120},"contribution welcome","11E4B8",2765,"Export VPButton + VPSponsors","2023-08-23T00:04:06Z","https://github.com/vuejs/vitepress/issues/2765",0.8172537,{"description":3127,"labels":3128,"number":3129,"owner":3033,"repository":3034,"state":3078,"title":3130,"updated_at":3131,"url":3132,"score":3133},"### Is your feature request related to a problem? Please describe.\n\n`Sidebar` define in code:\n\n```ts\nexport type Sidebar = SidebarItem[] | SidebarMulti;\n\nexport interface SidebarMulti {\n [path: string]: SidebarItem[] | { items: SidebarItem[]; base: string };\n}\n\nexport type SidebarItem = {\n text?: string;\n link?: string;\n items?: SidebarItem[];\n collapsed?: boolean;\n base?: string;\n docFooterText?: string;\n rel?: string;\n target?: string;\n};\n```\n\nThis is a direcotry structure:\n\n```text\n└── misc\n ├── cap1.md\n ├── cap2\n │ ├── cap2-1.md\n │ └── index.md\n ├── index.md\n └── intro.md\n```\n\nI config `sidebar` in `config.mts`:\n\n```ts\nsidebar: {\n '/misc': {\n base: '/misc',\n items: [\n { text: 'Intro', link: '/intro' },\n { text: 'Cap1', link: '/cap1' },\n {\n text: 'Cap2',\n base: '/cap2',\n items: [{ text: 'Cap2.1', link: '/cap2-1' }],\n },\n ],\n },\n}\n```\n\nActual routes:\n\n```text\n/misc/intro.html\n/misc/cap1.html\n/cap2/cap2-1.html\n```\n\n### Describe the solution you'd like\n\nIn this setup, it looks like `SidebarItem.base` completely replaces the `SidebarMulti.base`, instead of working relative to it — which feels a bit unexpected.\n\nWould it be possible for VitePress to support making nested base values inherit from the parent?\n\nSomething like this:\n\n```text\n/misc/intro.html\n/misc/cap1.html\n/misc/cap2/cap2-1.html\n```\n\nThat’d make things way more intuitive, especially when building out deeper folder structures.\n\n\n### Describe alternatives you've considered\n\n_No response_\n\n### Additional context\n\nVitepress version: `2.0.0-alpha.7`\n\nHere is a minimal reproduction: [https://stackblitz.com/edit/vite-yrm66kkm?file=docs%2F.vitepress%2Fconfig.ts](https://stackblitz.com/edit/vite-yrm66kkm?file=docs%2F.vitepress%2Fconfig.ts)\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.",[],4821,"`SidebarItem.base` overrides parent `SidebarMulti.base` instead of inheriting","2025-07-02T09:09:15Z","https://github.com/vuejs/vitepress/issues/4821",0.8173325,["Reactive",3135],{},["Set"],["ShallowReactive",3138],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f-mmM7QVaAwmJ9l8znc5nt4tSYJ115ZFFUoR2fZfpkEY":-1},"/vuejs/vitepress/4256"]