\u003C/div>`. If I would style said `div` with a `padding: 8px`, it is expected that by nesting it 3 levels deep, I would end up with 3 div html elements, each pushing its child `8px` in. \r\n\r\nThe result is basically:\r\n\r\n```html\r\n\u003Cdiv class=\"spacer\">\r\n \u003Cdiv class=\"spacer\">\r\n \u003Cdiv class=\"spacer\">\u003Cslot />\u003C/div>\r\n \u003C/div>\r\n\u003C/div>\r\n```\r\n\r\n> **notice** how on line 5, I get back the actual, non-compiled template.\r\n\r\n\n\n### Reproduction\n\n- create a custom component, say a \u003CTest> component with a `\u003Cslot />`\r\n- import it to vitepress\r\n- write a `md` story and nest the component three times:\r\n\r\n```md\r\n\u003Ctest>\r\n \u003Ctest>\u003C/test>\r\n \u003Ctest>\r\n \u003Ctest>I get rendered as text, even if I contain an HTML element, such as a `\u003Cbutton>`\u003C/test>\r\n \u003C/test>\r\n\u003C/test>\r\n```\n\n### Expected behavior\n\ntemplate compiler should keep going through deeper levels of components and render them as HTML elements.\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 12.2\r\n CPU: (8) arm64 Apple M1\r\n Memory: 119.95 MB / 16.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 16.13.0 - ~/.nvm/versions/node/v16.13.0/bin/node\r\n Yarn: 1.22.17 - /opt/homebrew/bin/yarn\r\n npm: 8.1.0 - ~/.nvm/versions/node/v16.13.0/bin/npm\r\n Browsers:\r\n Chrome: 97.0.4692.99\r\n Safari: 15.3\r\n npmPackages:\r\n vitepress: ^0.21.6 => 0.21.6\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.",[2920],{"name":2921,"color":2922},"build","377ba8",519,"nested templates not being compiled","2023-01-21T14:32:54Z","https://github.com/vuejs/vitepress/issues/519",0.7030001,{"description":2929,"labels":2930,"number":2932,"owner":2871,"repository":2872,"state":2873,"title":2933,"updated_at":2934,"url":2935,"score":2936},"### Describe the bug\n\nIt is passed as `build.base` instead of root level `base` option\r\n\r\n```log\r\n\"build.base\" option is deprecated. \"base\" is now a root-level config option.\r\n```\n\n### Reproduction\n\nN/A\n\n### Expected behavior\n\nNo warning and work\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 13.0\r\n CPU: (10) arm64 Apple M1 Max\r\n Memory: 3.91 GB / 64.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.15.1 - ~/Library/Caches/fnm_multishells/985_1655820447617/bin/node\r\n Yarn: 1.22.19 - ~/Library/Caches/fnm_multishells/985_1655820447617/bin/yarn\r\n npm: 8.12.1 - ~/Library/Caches/fnm_multishells/985_1655820447617/bin/npm\r\n Browsers:\r\n Chrome: 102.0.5005.115\r\n Firefox: 101.0.1\r\n Safari: 16.0\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.2 => 1.0.0-alpha.2\n```\n\n\n### Additional context\n\nWorking on a fix.\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.",[2931],{"name":2868,"color":2869},835,"`vitepress build docs --base /xxx/` does not work as expected","2023-01-21T14:34:00Z","https://github.com/vuejs/vitepress/issues/835",0.70501935,{"description":2938,"labels":2939,"number":2940,"owner":2871,"repository":2872,"state":2873,"title":2941,"updated_at":2942,"url":2943,"score":2944},"\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\nCopying the configuration of vuepress to vitepress, the sidebar is not displayed as a result.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\r\nClone Repo: [https://github.com/misitebao/template-vitepress.git](https://github.com/misitebao/template-vitepress.git)\r\nRun: npm i && npm run dosc:dev\r\n\r\n**Expected behavior**\r\nDisplay the sidebar normally\r\n\r\n**System Info**\r\n- vitepress version: v0.12.2\r\n- vite version: \r\n- Node version: v14.8.0\r\n- OS version: Win10\r\n\r\n**Additional context**\r\nI want to implement a template template as the basis for subsequent vitepress projects\r\n",[],260,"Copying the configuration of vuepress to vitepress, the sidebar is not displayed as a result.","2023-01-21T16:22:24Z","https://github.com/vuejs/vitepress/issues/260",0.70787156,{"description":2946,"labels":2947,"number":2949,"owner":2871,"repository":2872,"state":2873,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Describe the bug\n\n\r\n\r\n\r\nsame happens when there's another `base: '/section2/',` in sidebar\n\n### Reproduction\n\nconfig:\r\n```ts\r\nexport default defineConfig({\r\n\r\n...\r\n\r\n sidebar: [\r\n {\r\n base: '/section/',\r\n items: [\r\n { text: 'First', link: '/first' },\r\n { text: 'Second', link: '/second' },\r\n { text: 'Third', link: '/third' },\r\n ]\r\n },\r\n ],\r\n\r\n...\r\n```\r\n\r\nfolder structure:\r\n\r\n\r\n\n\n### Expected behavior\n\n\r\n\r\n(like without the base link and md files stored in parent folder)\n\n### System Info\n\n```Text\nrc20, windows\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.",[2948],{"name":2868,"color":2869},3010,"bottom page navigation link always directs to first page when using base URLs for sidebar","2023-10-02T00:04:34Z","https://github.com/vuejs/vitepress/issues/3010",0.7090333,{"description":2955,"labels":2956,"number":2957,"owner":2871,"repository":2872,"state":2873,"title":2958,"updated_at":2959,"url":2960,"score":2961},"**Is your feature request related to a problem? Please describe.**\r\nCurrently, importing Vue components (whether they are VitePress components, or components from a library for example) are influenced by VitePress's somewhat sub-optimal styles.\r\n\r\nFor example, all headings are styled, so as soon as a component uses an `h1`/`h2`/etc, it will inherit those styles, making VitePress virtually unusable for component libraries that ship their own CSS.\r\n\r\nThe only I can think of mitigating this, is to use a web component as a base for Vue components to be mounted in, as styles are local to web components if I remember correctly.\r\n\r\n**Describe the solution you'd like**\r\nSome way to render components with their own styles, and not inherit styles from the docs.\r\n\r\n**Describe alternatives you've considered**\r\nI tries unsetting all styles `* { all: unset; }` inside our demo component (the wrapper for all other components), but that also removes some of the Tailwind related styling unfortunately.\r\n\r\nI couldn't get web components to work, as the vue plugin seems to be for Vue 2 (https://github.com/vuejs/vue-web-component-wrapper).",[],248,"[Feature] - Allow local styling of components","2023-01-21T16:04:20Z","https://github.com/vuejs/vitepress/issues/248",0.70920426,["Reactive",2963],{},["Set"],["ShallowReactive",2966],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fxOnw8ty2xquWr_-YQXc1-113y8hkIfC0JyvWenfzxAc":-1},"/vuejs/vitepress/231"]