\r\n```\r\n\r\nAlternatively, use the `desc` defined in the `container` to write Markdown syntax.\r\n\r\n```md\r\n::: demo src=\"../demo.vue\" title=\"Demo block\"\r\n\r\nThis is a `description` that can be written using Markdown.\r\n\r\n:::\r\n```\r\n\r\n### Describe the solution you'd like\r\n\r\nTo address this, I have created the [markdown-it-vitepress-demo](https://github.com/hairyf/markdown-it-vitepress-demo) plugin. I'm not sure if it can be helpful.\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- https://github.com/vuejs/vitepress/issues/987\r\n- https://github.com/vuejs/vitepress/issues/1349\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.",[2881],{"name":2868,"color":2869},2432,"feat(demo): built-in markdown plugin provides support for showcasing demo capabilities.","2024-07-17T14:37:26Z","https://github.com/vuejs/vitepress/issues/2432",0.7444388,{"description":2888,"labels":2889,"number":2894,"owner":2871,"repository":2872,"state":2873,"title":2895,"updated_at":2896,"url":2897,"score":2898},"As mentioned in #253, we probably should add a community examples page. Here are the things that we can add:\r\n\r\n- Markdown Extensions\r\n * Code Groups\r\n * Footnotes\r\n * Task Lists\r\n * Maths, Diagrams, Charts\r\n\r\n- SEO Improvement\r\n * Sitemaps\r\n * Meta Tags\r\n\r\n- Image Extensions\r\n * Zoom on Click\r\n * Image Gallary\r\n * Figures and Captions\r\n\r\n- Complex Use-Cases\r\n * Building PWA\r\n * CSS Isolation\r\n * Dynamic Sidebar\r\n * Multiple Bases\r\n * Offline Search\r\n * Writing Blogs\r\n * Versioning\r\n\r\n- Integration with other libraries:\r\n * TailwindCSS\r\n * Styleguidist (might be tricky)\r\n * Pinia\r\n\r\nI created this list based on popular VuePress plugins and VitePress issues. Having such a page before v1 will significantly ease up migration. If you think the list is missing something common then please comment.\r\n\r\nSome of these can be officially supported too, especially the markdown extensions.",[2890,2893],{"name":2891,"color":2892},"docs","0075ca",{"name":2868,"color":2869},883,"Add examples","2024-03-07T11:20:19Z","https://github.com/vuejs/vitepress/issues/883",0.7451683,{"description":2900,"labels":2901,"number":2903,"owner":2871,"repository":2872,"state":2873,"title":2904,"updated_at":2905,"url":2906,"score":2907},"### Is your feature request related to a problem? Please describe.\n\nMy CMS stores markdown values in frontmatter data. For example, an intro section `intro` with a markdown string value. Currently, trying to access it in the page with `{{ $frontmatter.intro }}` just renders it as a string (a direct result of the markdown -> Vue -> HTML pipeline). What is the recommended way to call the markdown parser on it?\n\n### Describe the solution you'd like\n\nIt would be nice to see this exposed somehow (getting the built-in markdown-it instance, for example).\n\n### Describe alternatives you've considered\n\nI could install markdown-it separately and use it that way?\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.",[2902],{"name":2868,"color":2869},2410,"Expose the built-in markdown parser to render markdown-valued variables with","2024-02-02T09:23:30Z","https://github.com/vuejs/vitepress/issues/2410",0.75095797,{"description":2909,"labels":2910,"number":217,"owner":2871,"repository":2872,"state":2911,"title":2912,"updated_at":2913,"url":2914,"score":2915},"**Describe the bug/feature**\r\n\r\nIn both **Vitepress** and **Vuepress** the way in which the Markdown-it rule `htmlBlock` is implemented is highly subpar. This is particularly true because the primary use-case for both is documentation but currently adding in a VueJS component which takes advantage of slot content tends to break rather quickly. This is because -- by default web-components are considered _inline_ components by Markdown (as per the spec). When Markdown encounters inline components it treats the interior scope of the web-component as Markdown content and therefore tends to wreck havoc on slot content.\r\n\r\nLooking at the `src/node/markdown/plugins/component.ts` file you can start to see the problem when looking at the `HTML_SEQUENCES` symbol (some lines removed for brevity):\r\n\r\n```ts\r\n// An array of opening and corresponding closing sequences for html tags,\r\n// last argument defines whether it can terminate a paragraph or not\r\nconst HTML_SEQUENCES: [RegExp, RegExp, boolean][] = [\r\n // PascalCase Components\r\n [/^\u003C[A-Z]/, />/, true],\r\n // custom elements with hyphens\r\n [/^\u003C\\w+\\-/, />/, true],\r\n]\r\n```\r\n\r\nThe intent here is to mark the opening and closing of scope for a component but as you can see from the RegEx it is only looking for inline components not block components!\r\n\r\nFor example, the component `p-table` has several named slots which help it to render the way the user intends:\r\n\r\n```html\r\n\u003Cp-table>\r\n \r\n \u003Ctemplate #name=\"{ row }\">\r\n {{ row.name }}\r\n \u003C/template>\r\n\r\n \u003Ctemplate #age=\"{ row }\">\r\n {{ row.age }}\r\n \u003C/template>\r\n\r\n\u003C/p-table>\r\n```\r\n\r\nPut this into the template section of a Vue CLI app and it works just fine. Put it into Vuepress or Vitepress and watch the cloud of smoke start to rise as it fumbles around; particularly failing on the `#` symbols used as shorthand for named slots. This is particularly troublesome for a documentation site that is trying to document a set of VueJS components! There should be a way to ensure that this VueJS component's interior scope is left untouched by **Markdown-it** ... at least when that's what you want. \r\n\r\nThere is a second use-case that I would expect Vitepress to just handle and that is _kind of_ what it's doing today but in a hit and miss fashion currently. Let's say that I just have a default slot in my component and therefore I want my component to be seen by the Markdown engine as being an \"inline\" component and process the interior as markdown. Great, then the following should work:\r\n\r\n```md\r\n\u003Csuper-sexy>\r\n# some heading\r\n## some sub heading\r\n\u003C/super-sexy>\r\n```\r\n\r\nThis would just provide some HTML wrapper elements that would in this case make this very dull markdown sexy.\r\n\r\nFinally there is a third use-case that really should be considered required too ... this is the hybrid but it will allow for all sorts of simple but useful documentation components. The use-case presents as a component that exposes named slots -- and therefore is seen by Markdown as a block component -- but these named slots _are_ processed by markdown. An obvious example might be a `\u003Ctwo-columns>` component which provides a `left` and `right` slot and allows authors to more readily leverage their horizontal space.\r\n\r\nImagine the following:\r\n\r\n```html\r\n\u003Ctwo-columns>\r\n\r\n \u003Ctemplate #left>\r\n I'm a lumberjack and I'm ok\r\n \u003C/template>\r\n \u003Ctemplate #right>\r\n I sleep all night and I work all day\r\n \u003C/template>\r\n\r\n\u003C/two-columns>\r\n```\r\n \r\nThis will fail miserably today but it _could_ be grand!\r\n\r\n** Proposed Solution **\r\n\r\nRework the `src/node/markdown/plugins/components.ts` file in Vitepress (same change can be applied to Vuepress) to:\r\n\r\n- use more sophisticated RegEx patterns to actually capture BLOCK content not just inline components\r\n- support two modes of processing for BLOCK VueJS components: \r\n\r\n 1. Isolated - the interior scope is _not_ processed as markdown and all registered VueJS components can operate exactly like they would normally do\r\n 2. Parsed - the interior scope is processed as markdown; this will work well for default slots where the interior content is Markdown content\r\n\r\n- the Isolated mode should be seen as the _default_ as it is more powerful and allows components that work outside the context of Vitepress/Vuepress to just work here as well\r\n- the parsed mode may be popular for components designed strictly for Vitepress and Vuepress and it could be opted into in the HTML template like so:\r\n\r\n ```html\r\n \u003Cmy-crazy-idea parsed>There I was, _there I was_, in the Congo\u003C/my-crazy-idea>\r\n ```\r\n\r\nThis solution so far could pretty easily support the first two use cases which is a big step forward. The third use-case would certainly be nice but would need a bit more thought. I could imagine something as simple as adding the `md` prop to the parent component being used as a means to pass in the Markdownit object into the top-level component so it could chain the rendering into the various named slots:\r\n\r\n ```html\r\n \u003Cmy-crazy-idea md>\r\n \u003Ctemplate #left>\r\n There I was, _there I was_, \r\n \u003Ctemplate #right>\r\n I sleep all night and I work all day\r\n \u003C/template>\r\n \u003C/my-crazy-idea>\r\n ```\r\n\r\nIn all likelihood this last option should be done as an optional second step.\r\n",[],"closed","Proper processing of Vue Component slot content","2023-01-21T14:28:50Z","https://github.com/vuejs/vitepress/issues/135",0.73539364,{"description":2917,"labels":2918,"number":2919,"owner":2871,"repository":2872,"state":2911,"title":2920,"updated_at":2921,"url":2922,"score":2923},"I'm new to vue and vitepress so I'm a little confused.\r\n\r\nI'm looking into adding markdown to my existing vue app. The way I imagined it would be some markdown element which would take the markdown text and render it. I'm also interested in embedding vue components inside the markdown. Something like\r\n```\r\n\u003CMarkdown>\r\n## abc\r\nefg\r\n### hij\r\nHi {{name}},\r\n\u003C/Markdown>\r\n```\r\nI was hoping vitepress would do it, but it seems like vitepress sets everything up as a standalone app. I can't simply add vitepress to my package.json and start using it's elements.\r\n\r\nAny examples of using vitepress in an existing vue as a library? Or any alternative?",[],315,"Use vitepress in an existing vue app","2023-01-21T16:22:21Z","https://github.com/vuejs/vitepress/issues/315",0.73575234,{"description":2925,"labels":2926,"number":2927,"owner":2871,"repository":2872,"state":2911,"title":2928,"updated_at":2929,"url":2930,"score":2931},"### Is your feature request related to a problem? Please describe.\n\nFeature and/or problem (in the latter case is just a lacking documentation).\n\n### Describe the solution you'd like\n\nSince VP already uses Iconify, I'd like to be able to use inline iconify icons in markdown, is it possible somehow maybe like dropping a tag like if it was template? Eg:\r\n\r\n```\r\n## Sample text\r\nHere's an inline icon: \u003CIcon icon=\"mdi-light:home\" />\r\n```\r\nI think this is pretty reasonable to have.\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.",[],3068,"Use Iconify icons in inline markdown","2023-10-20T00:04:33Z","https://github.com/vuejs/vitepress/issues/3068",0.73582816,{"description":2933,"labels":2934,"number":2938,"owner":2871,"repository":2872,"state":2911,"title":2939,"updated_at":2940,"url":2941,"score":2942},"### Is your feature request related to a problem? Please describe.\r\n\r\nMy issue is related to pre-building the SVGs of Mermaid diagrams upon build using [mermaid-cli](https://github.com/mermaid-js/mermaid-cli).\r\n\r\nIn development mode, I use the normal version of Mermaid:\r\n```vue\r\n// .vitepress/components/Mermaid.vue\r\n\u003Ctemplate>\r\n \u003Cdiv>\r\n \u003Cdiv v-if=\"isDark\" v-html=\"svgDark\">\u003C/div>\r\n \u003Cdiv v-else v-html=\"svgLight\">\u003C/div>\r\n \u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport {ref, watch} from 'vue';\r\nimport {useData} from 'vitepress'\r\nimport {type MermaidConfig} from 'mermaid'\r\nimport mermaid from 'mermaid'\r\n\r\nconst render = async (id: string, code: string, config: MermaidConfig): Promise\u003Cstring> => {\r\n mermaid.initialize(config)\r\n const {svg} = await mermaid.render(id, code)\r\n return svg\r\n}\r\n\r\nconst {isDark} = useData()\r\n\r\nconst props = defineProps({\r\n graph: {\r\n type: String,\r\n required: true,\r\n },\r\n id: {\r\n type: String,\r\n required: true,\r\n },\r\n});\r\n\r\nconst svgLight = ref\u003Cstring>('');\r\nconst svgDark = ref\u003Cstring>('');\r\n\r\nconst renderChart = async () => {\r\n console.log('rendering chart' + props.id + props.graph);\r\n const mermaidConfig = {\r\n securityLevel: 'loose',\r\n startOnLoad: false,\r\n };\r\n\r\n\r\n svgLight.value = await render(props.id, decodeURIComponent(props.graph), {\r\n ...mermaidConfig,\r\n theme: 'default'\r\n })\r\n svgDark.value = await render(props.id, decodeURIComponent(props.graph), {\r\n ...mermaidConfig,\r\n theme: 'dark'\r\n })\r\n}\r\n\r\nwatch([() => props.graph], () => {\r\n renderChart()\r\n}, {immediate: true})\r\n\u003C/script>\r\n```\r\n\r\nAnd I adapted the markdown-it instance to replace the mermaid code fences with that component:\r\n```ts\r\n// .vitepress/config.ts\r\nimport {defineConfig} from 'vitepress'\r\n\r\nexport default defineConfig({\r\n // ...\r\n markdown: {\r\n config: md => {\r\n md.renderer.rules.fence = (tokens, index, options, env, slf) => {\r\n const token = tokens[index]\r\n if (token.info.trim() === 'mermaid') {\r\n const key = index\r\n return `\r\n \u003CSuspense>\r\n \u003Ctemplate #default>\r\n \u003CMermaid id=\"mermaid-${key}\" graph=\"${encodeURIComponent(token.content)}\">\u003C/Mermaid>\r\n \u003C/template>\r\n \u003Ctemplate #fallback>\r\n Loading...\r\n \u003C/template>\r\n \u003C/Suspense>\r\n`\r\n }\r\n }\r\n }\r\n }\r\n})\r\n```\r\nThe code is heavily inspired by what has been done by Mermaid in their VitePress.\r\n\r\nIt works fine, but since most pages of my documentation contain a lot of graphs, I wanted to prebuild them. However, Mermaid is not compatible with SSR (https://github.com/mermaid-js/mermaid/issues/3650).\r\n\r\n### Describe the solution you'd like\r\n\r\nI would like to have access to the env mode in the Markdown-it context (in the env variable for example) so that I can conditionally add either the Mermaid component or a VPImage component with the path to the SVG I'd pre-generate in the buildEnd hook.\r\n\r\n### Describe alternatives you've considered\r\n\r\nI tried to naively use mermaid-cli in Mermaid.vue instead of Mermaid when import.meta.env.SSR is truthy, but it fails as in SSR I apparently don't have access to Node.js modules.\r\n\r\nI tried to use a `v-if=\"import.meta.env.SSR\"` in the Mermaid component, but it gets sanitized with a work break between `i` and `mport` before being replaced by its value by Vite.\r\n\r\nI considered spawning synchronously a node process that would generate the SVG upon parsing the markdown, but that would drastically slow down the build process.\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.",[2935],{"name":2936,"color":2937},"build","377ba8",2538,"Add build mode in markdown-it env","2023-08-12T00:04:17Z","https://github.com/vuejs/vitepress/issues/2538",0.74195504,{"description":2944,"labels":2945,"number":2947,"owner":2871,"repository":2872,"state":2911,"title":2948,"updated_at":2949,"url":2950,"score":2951},"I am looking into porting the using vue in Markdown from vuepress: \r\nhttps://vuepress.vuejs.org/guide/using-vue.html\r\n\r\nIf I understand correctly, vitepress doesn't want to auto register components by convention as Vuepress does. Is this the case? I actually liked this feature, but I understand that vitepress wants to keep the moving parts as small as possible.\r\n\r\nWhat is the recommended way to register the components? I see that in vue-router-next docs they are registered globally inside `enhanceApp`: https://github.com/vuejs/vue-router-next/search?q=HomeSponsors.\r\nSame as with this comment: https://github.com/vuejs/vitepress/issues/92#issuecomment-724645482\r\n\r\nShould we document this way in the docs?\r\n\r\nSome thoughts about this. It would be great that users that want to use the default theme as is, do not need to learn straight away about enhanceApp to be able to use a vue component in their markdown.\r\n\r\nIf auto registering by convention in a folder like `.vitepress/components` is not an option, could we import them directly in the markdown?\r\n\r\n```markdown\r\n# Docs\r\n\r\nThis is a .md using a custom component\r\n\r\n\u003CCustomComponent />\r\n\r\n## More docs\r\n\r\n...\r\n\r\n\u003Cscript setup>\r\n import CustomComponent from '../components/CustomComponent.vue'\r\n\u003C/script>\r\n```\r\n\r\nScript & style hoisting is working in vitepress: https://vuepress.vuejs.org/guide/using-vue.html#script-style-hoisting, but I tried this example to import a Component and it is not at this point.\r\n",[2946],{"name":2891,"color":2892},157,"Recommended way to use Custom Vue components in .md","2023-01-21T16:04:10Z","https://github.com/vuejs/vitepress/issues/157",0.74215764,{"description":2953,"labels":2954,"number":2958,"owner":2871,"repository":2872,"state":2911,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Describe the bug\r\n\r\nWhen you build the artifacts, logo images are missing.\r\n\r\n### Reproduction\r\n\r\nI followed [GitLab deploy guide](https://vitepress.vuejs.org/guide/deploying#gitlab-pages) then I read [PR 1451](https://github.com/vuejs/vitepress/pull/1451) and I configured default theme like this:\r\n\r\n```typescript\r\n outDir: '../public',\r\n base: '/group/repository/',\r\n themeConfig: {\r\n logo: {\r\n light: '/i/logo-light.png',\r\n dark: '/i/logo-dark.png',\r\n alt: 'My Alt Text',\r\n },\r\n },\r\n```\r\n\r\nFinally, I've created `docs/i/logo-light.png` and the dark one. \r\nWorks fine during development. Images get rendered, they are abt 14Kb\r\n\r\n### Expected behavior\r\n\r\nExpected to be fine also after build. But it's missing logo files. \r\nThere's only `ita.jpeg` who's embedded by using \r\n\r\n```bash\r\ntassoman@i2000014518:~/devel/GitLab/myrepo$(main) ls -alhR public/\r\npublic/:\r\ntotale 56K\r\ndrwxrwxr-x 3 tassoman tassoman 4,0K mar 3 18:25 .\r\ndrwxrwxr-x 6 tassoman tassoman 4,0K mar 3 18:25 ..\r\n-rw-rw-r-- 1 tassoman tassoman 9,7K mar 3 18:25 404.html\r\ndrwxrwxr-x 2 tassoman tassoman 4,0K mar 3 18:25 assets\r\n-rw-rw-r-- 1 tassoman tassoman 24 mar 3 18:25 hashmap.json\r\n-rw-rw-r-- 1 tassoman tassoman 27K mar 3 18:25 index.html\r\n\r\npublic/assets:\r\ntotale 716K\r\ndrwxrwxr-x 2 tassoman tassoman 4,0K mar 3 18:25 .\r\ndrwxrwxr-x 3 tassoman tassoman 4,0K mar 3 18:25 ..\r\n-rw-rw-r-- 1 tassoman tassoman 136K mar 3 18:25 app.9d50fb2d.js\r\n-rw-rw-r-- 1 tassoman tassoman 18K mar 3 18:25 index.md.2dde5316.js\r\n-rw-rw-r-- 1 tassoman tassoman 1,8K mar 3 18:25 index.md.2dde5316.lean.js\r\n-rw-rw-r-- 1 tassoman tassoman 18K mar 3 18:25 inter-italic-cyrillic.ea42a392.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 28K mar 3 18:25 inter-italic-cyrillic-ext.33bd5a8e.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 23K mar 3 18:25 inter-italic-greek.8f4463c4.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 12K mar 3 18:25 inter-italic-greek-ext.4fbe9427.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 45K mar 3 18:25 inter-italic-latin.bd3b6f56.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 63K mar 3 18:25 inter-italic-latin-ext.bd8920cc.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 8,6K mar 3 18:25 inter-italic-vietnamese.6ce511fb.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 17K mar 3 18:25 inter-roman-cyrillic.5f2c6c8c.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 26K mar 3 18:25 inter-roman-cyrillic-ext.e75737ce.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 22K mar 3 18:25 inter-roman-greek.d5a6d92a.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 12K mar 3 18:25 inter-roman-greek-ext.ab0619bc.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 42K mar 3 18:25 inter-roman-latin.2ed14f66.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 59K mar 3 18:25 inter-roman-latin-ext.0030eebd.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 8,3K mar 3 18:25 inter-roman-vietnamese.14ce25a6.woff2\r\n-rw-rw-r-- 1 tassoman tassoman 47K mar 3 18:25 ita.42a9fca8.jpeg \u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\u003C\r\n-rw-rw-r-- 1 tassoman tassoman 90K mar 3 18:25 style.4da33c5a.css\r\n\r\n```\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)\r\n CPU: (8) x64 Intel(R) Core(TM) i7-4702MQ CPU @ 2.20GHz\r\n Memory: 3.75 GB / 7.46 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 16.14.0 - ~/.nvm/versions/node/v16.14.0/bin/node\r\n Yarn: 1.22.19 - ~/.yarn/bin/yarn\r\n npm: 9.6.0 - ~/.nvm/versions/node/v16.14.0/bin/npm\r\n Browsers:\r\n Chromium: 110.0.5481.100\r\n Firefox: 110.0.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.49 => 1.0.0-alpha.49\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.",[2955],{"name":2956,"color":2957},"bug: pending triage","e99695",2031,"Missing assets logo light/dark after build","2023-03-11T00:04:09Z","https://github.com/vuejs/vitepress/issues/2031",0.74264663,["Reactive",2964],{},["Set"],["ShallowReactive",2967],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f54K6o1JkqZjva1sP9xHeRr_kkkWukYG7hh9_AOabAyU":-1},"/vuejs/vitepress/2036"]