\r\n\u003CB />\r\n\r\n\u003Cscript setup>\r\n import A from './sections/a.md'\r\n import B from './sections/b.md'\r\n\u003C/script>\r\n```\r\n\r\n`a.md`:\r\n```\r\n## Title\r\n\r\ntest\r\n```\r\n\r\n`b.md`:\r\n```\r\n## Title2\r\n\r\ntest2\r\n```\r\n\r\n`[[toc]]` won't show anything because it doesn't parse the sub .md files\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior: Just use the code that I pasted\r\n\r\n**Expected behavior**\r\nI expect `[[toc]]` to take into account the markdown that is imported so that we can organise our text into different files\r\n\r\n**System Info**\r\n- vitepress version: latest\r\n- vite version: latest\r\n- Node version: latest\r\n- OS version: Mac OS M1 latest\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2897],{"name":2879,"color":2880},266,"TOC won't parse imported markdown files","2023-01-21T14:35:41Z","https://github.com/vuejs/vitepress/issues/266",0.7360708,{"description":2904,"labels":2905,"number":2909,"owner":2868,"repository":2869,"state":2870,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Describe the bug\n\nthere are no sub-directories after run build when set config to \"cheanUrls: true\". \r\nthese pages seem to work after deployed on static host server. I saw a \"404 page\" flash by.\n\n### Reproduction\n\n## config.ts\r\n```js\r\nconst config = async () => {\r\n return {\r\n title: 'Zhaoqiu-Blog',\r\n \r\n // head: [\r\n // ['link', { rel: \"icon\", type: \"image/x-icon\", href: \"/favicon.ico\"}],\r\n // ['link', { rel: \"shortcut icon\", type: \"image/x-icon\", href: \"/favicon.ico\"}]\r\n // ],\r\n description: 'zhaoqiu blog',\r\n lang: 'zh',\r\n lastUpdated: true,\r\n cleanUrls: true,\r\n appearance: 'dark',\r\n markdown: {\r\n // anchor: {\r\n // level: anchor.level,\r\n // permalink: anchor.permalink.headerLink()\r\n // },\r\n // toc: {level: [2, 3]},\r\n lineNumbers: true,\r\n config: (md) => {\r\n md.use(mathjax3)\r\n },\r\n },\r\n themeConfig: {\r\n posts: await getPosts(),\r\n pageSize: 5,\r\n postsLength: await getPostLength(),\r\n logo: '/logo.svg',\r\n siteTitle: 'zhaoqiu blog',\r\n nav: [\r\n {text: '🏡Home', link: '/'},\r\n {text: '📁Archives', link: '/archives'},\r\n {text: '🚀Product', link: '/product'},\r\n {text: '🔖Tags', link: '/tags'},\r\n {text: '👀About Me', link: '/me'}\r\n \r\n ],\r\n socialLinks: [\r\n {icon: 'github', link: 'https://github.com/zhaoqiu-china'}\r\n ],\r\n footer: {\r\n message: \"\u003Ca href='https://beian.miit.gov.cn/#/Integrated/index'>鲁ICP备2022036350号-1\u003C/a>\",\r\n copyright: 'Copyright © 2019-present Zhaoqiu'\r\n },\r\n darkModeSwitchLabel: 'Appearance'\r\n },\r\n vue: {\r\n template: {\r\n compilerOptions: {\r\n isCustomElement: (tag: string) => customElements.includes(tag),\r\n \r\n },\r\n },\r\n },\r\n }\r\n}\r\n\r\nexport default config()\r\n```\r\n\r\n## yarn docs:build\r\n\r\n\r\n\n\n### Expected behavior\n\na.md --> /a/index.html\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 Intel(R) Core(TM) i7-10510U CPU @ 1.80GHz\r\n Memory: 4.94 GB / 15.87 GB\r\nBinaries:\r\n Node: 19.7.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 9.5.0 - C:\\Program Files\\nodejs\\npm.CMD\r\nBrowsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (110.0.1587.69)\r\n Internet Explorer: 11.0.19041.1566\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2906],{"name":2907,"color":2908},"bug: pending triage","e99695",2078,"cleanUrls doesn't seem to wrok","2023-03-21T00:04:10Z","https://github.com/vuejs/vitepress/issues/2078",0.7379828,{"description":2915,"labels":2916,"number":2920,"owner":2868,"repository":2869,"state":2870,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### Describe the bug\n\nSince the the theme update in [1.0.0-alpha.37](https://github.com/vuejs/vitepress/blob/main/CHANGELOG.md#100-alpha37-2023-01-17) the text to background contrast ration of [Custom Containers](https://vitepress.vuejs.org/guide/markdown#custom-containers) got worse. The text became much more difficult to read.\r\n\r\nHere's a side-by-side comparison image:\r\n\r\n\r\n\n\n### Reproduction\n\n1. Go to https://vitepress.vuejs.org/guide/markdown#custom-containers\r\n2. Switch to light theme\r\n\n\n### Expected behavior\n\n`--vp-custom-block-*-text` variables on light theme should be either set to `--vp-c-*-dark` or `--vp-c-*-darker` instead of `--vp-c-*`.\r\n\r\nFor Example: \r\n\r\n```css\r\n:root {\r\n --vp-custom-block-warning-text: var(--vp-c-yellow-darker);\r\n}\r\n\r\n.custom-block.warning {\r\n color: var(--vp-custom-block-warning-text);\r\n}\r\n```\n\n### System Info\n\n```shell\n-\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2917],{"name":2918,"color":2919},"theme","0754FB",1824,"Bad contrast for Custom Containers on light theme","2023-03-07T00:04:57Z","https://github.com/vuejs/vitepress/issues/1824",0.74092686,{"description":2926,"labels":2927,"number":2928,"owner":2868,"repository":2869,"state":2870,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Describe the bug\r\n\r\nWhen working on fakerjs's Vitepress docs we noticed that all content entered after the last header on a page would be removed. I noticed the same behavior within Vitepress's own docs. \r\n\r\nWe opened up the console and saw there was a hydration mismatch. At first, we thought the issue was that we were using a `[[toc]]` element at the top of our document https://github.com/vuejs/vitepress/issues/388 but that was not the case.\r\n\r\nAfter we removed the TOC, there was no change and all content after the last `### tag` header would still be removed when refreshing the page.\r\n\r\n### Reproduction\r\n\r\nVisit https://vitepress.vuejs.org/guide/markdown.html#advanced-configuration and see that all content underneath the \"Advanced Configuration\" header does not exist.\r\n\r\n### Expected behavior\r\n\r\nAll content should render with no hydration mismatch.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: macOS 11.4\r\n CPU: (16) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 393.57 MB / 32.00 GB\r\n Shell: 5.8 - /bin/zsh\r\n Binaries:\r\n Node: 14.17.0 - ~/.nvm/versions/node/v14.17.0/bin/node\r\n Yarn: 1.22.10 - /usr/local/bin/yarn\r\n npm: 6.14.13 - ~/.nvm/versions/node/v14.17.0/bin/npm\r\n Browsers:\r\n Chrome Canary: 100.0.4868.0\r\n Firefox: 95.0\r\n Safari: 14.1.1\r\n npmPackages:\r\n vitepress: ^0.21.6 => 0.21.6\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] Follow our [Code of Conduct](https://vuejs.org/coc)\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.",[],521,"Vitepress's own docs have hydration mismatch and the last header's content in a section is not rendered","2023-01-21T14:34:01Z","https://github.com/vuejs/vitepress/issues/521",0.7467494,{"description":2934,"labels":2935,"number":2936,"owner":2868,"repository":2869,"state":2870,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Describe the bug\r\n\r\ncontent inside [] should not be parsed as html \r\n\r\n\r\n### Reproduction\r\n\r\njust use \r\n```\r\n[SimpleLink\u003CT>] (\"somewhere\")\r\n```\r\nin any md file\r\n\r\n### Expected behavior\r\n\r\nThe page should render even with \"Element is missing end tag\" when inside [ ]\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.19042\r\n CPU: (8) x64 Intel(R) Core(TM) i5-8350U CPU @ 1.70GHz \r\n Memory: 16.55 GB / 31.88 GB\r\n Binaries:\r\n Node: 14.17.6 - C:\\Program Files\\nodejs\\node.EXE \r\n Yarn: 1.22.10 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 7.24.2 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 98.0.4758.102\r\n Edge: Spartan (44.19041.1266.0), Chromium (99.0.1150.30)\r\n Internet Explorer: 11.0.19041.1202\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] 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.",[],576,"Element is missing end tag Error when used inside a link like [SimpleLink\u003CT>] (\"somewhere\")","2023-01-21T14:32:33Z","https://github.com/vuejs/vitepress/issues/576",0.74714404,{"description":2942,"labels":2943,"number":2947,"owner":2868,"repository":2869,"state":2870,"title":2948,"updated_at":2949,"url":2950,"score":2951},"### Describe the bug\n\nGreetings:\r\n\r\nI'm building a `story` for a custom element, imported in the `config.js` file as global component. \r\n\r\nWhen I nest the component more than **twice**, I get the `template` content rendered as plain text. Is as if vue is not picking it up to render the actually template, but instead using it as plain text content.\r\n\r\nSo, picture a component who's `\u003Ctemplate>` simply renders a `\u003Cdiv class=\"spacer\">\u003Cslot />\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.",[2944],{"name":2945,"color":2946},"build","377ba8",519,"nested templates not being compiled","2023-01-21T14:32:54Z","https://github.com/vuejs/vitepress/issues/519",0.7481534,{"description":2953,"labels":2954,"number":2956,"owner":2868,"repository":2869,"state":2870,"title":2957,"updated_at":2958,"url":2959,"score":2960},"### Describe the bug\n\nI'm not sure if this is a bug, but when a table is in a custom container, the color of the header doesn't follow the color of the container, and it is always black.\r\n\r\nIt looks very incongruous and strange.\r\n\r\n\n\n### Reproduction\n\nFor example:\r\n\r\n```markdown\r\n::: danger\r\nThis is a dangerous warning.\r\n\r\n| colhead1 | colhead2 |\r\n| -- | -- |\r\n| test | test |\r\n:::\r\n```\n\n### Expected behavior\n\nThe header row color of the table to be the same as the body of the table, and the color to follow the custom container\n\n### System Info\n\n```shell\n1.0.0 alpha 51,52\n```\n\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2955],{"name":2918,"color":2919},2077,"Color of Table head row in Custom Containers is always black","2023-04-06T00:04:11Z","https://github.com/vuejs/vitepress/issues/2077",0.7490685,["Reactive",2962],{},["Set"],["ShallowReactive",2965],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$feePeE7jRMDU977jxIS_Zq9VohaB-K-dLKPMFAPOfZcg":-1},"/vuejs/vitepress/1093"]