\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.",[2867],{"name":2868,"color":2869},"stale","ededed",2432,"vuejs","vitepress","open","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.7310359,{"description":2879,"labels":2880,"number":2882,"owner":2871,"repository":2872,"state":2873,"title":2883,"updated_at":2884,"url":2885,"score":2886},"### Is your feature request related to a problem? Please describe.\n\nDocs will often use terms or abbreviations that may be unfamiliar to someone just discovering the project, and I'd like [VP](## \"Vitepress\") to support showing the definition on hover (as I did on the VP using github's markdown). Ideally with a dashed line and not being an actual link.\r\n\r\nFurthermore, I'd like to be able to write each definition just once, and the term be hoverable across the entire project. Keeps the source DRY.\n\n### Describe the solution you'd like\n\nI'm a fan of Material for MkDocs' [solution](https://squidfunk.github.io/mkdocs-material/reference/tooltips/#adding-a-glossary-includesabbreviationsmd), where you create a glossary file and it appends the correct markdown to each page and the markdown parser then handles generating the tooltips. However, I have not found a markdown-it plugin for tooltips, so I'm not sure it'll necessarily carry over easily.\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.",[2881],{"name":2868,"color":2869},3130,"Automatic definition tooltips","2024-03-07T11:19:36Z","https://github.com/vuejs/vitepress/issues/3130",0.73452896,{"description":2888,"labels":2889,"number":2891,"owner":2871,"repository":2872,"state":2873,"title":2892,"updated_at":2893,"url":2894,"score":2895},"### Is your feature request related to a problem? Please describe.\r\n\r\nsuch as a vue components library site……\r\nA common problem for a documentation page is to show how to use a component, both in code and with demo of live component.\r\n\r\n### Describe the solution you'd like\r\n\r\nlike this [https://github.com/flingyp/vitepress-demo-preview](https://github.com/flingyp/vitepress-demo-preview)\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.",[2890],{"name":2868,"color":2869},3270,"Feature request: Vue component source code demo","2024-01-18T18:48:08Z","https://github.com/vuejs/vitepress/issues/3270",0.7370438,{"description":2897,"labels":2898,"number":2903,"owner":2871,"repository":2872,"state":2873,"title":2904,"updated_at":2905,"url":2906,"score":2907},"### Describe the bug\n\nCustom theme is a npm package, layout of the theme is following: \r\n```ts\r\n// myTheme/src/index.ts\r\nimport type { Theme } from \"vitepress\";\r\nimport { configProvider } from \"./compositions/configProvider\";\r\nimport Layout from \"./components/layout/index.vue\";\r\n\r\nconst pureTheme: Theme = {\r\n Layout: configProvider(Layout),\r\n};\r\n\r\nexport default pureTheme;\r\n```\r\nconfigProvider's source is following: \r\n```ts\r\n// myTheme/src/compositions/configProvider.ts\r\nexport const themeConfig: InjectionKey\u003CPureThemeConfig> = Symbol(\"themeConfig\");\r\n\r\nexport const configProvider = (component: Component) => {\r\n return defineComponent(() => {\r\n const { theme } = useData();\r\n provide(themeConfig, theme.value); // Notice this line\r\n return () => h(component, null, {});\r\n });\r\n};\r\n```\r\nthemeConfig is a ***Symbol*** in configProvider.\r\n\r\nwhen i setup vitepress and use custom theme in development \"vitepress dev\", i get an error.\r\n```ts\r\n// doc/.vitepress/theme/index.ts\r\nimport pureTheme from \"vitepress-pure-theme-zyco\";\r\nexport default pureTheme;\r\n```\r\nIn .vitepress/cache/deps, myTheme.js has a duplicated ***themeConfig*** variable.\r\n\u003Cimg src=\"https://github.com/vuejs/vitepress/assets/27729870/0768b1f8-0891-4f93-90e7-67932e6bf4eb\" width=“340” height=\"340\" />\r\n\r\nbut in Layout.vue it uses Header and Header uses themeConfig that is a Symbol: \r\n```vue\r\n// Layout.vue\r\n\u003Ctemplate>\r\n \u003CHeader :nav=\"Navlist\">\u003C/Header>\r\n\u003C/template>\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport Header from \"../header/index.vue\";\r\n\u003C/script>\r\n// Header.vue\r\n\u003Cscript setup lang=\"ts\">\r\nimport { inject, computed } from \"vue\";\r\nimport { themeConfig } from \"../../compositions/configProvider\"; // Notice this line\r\n\r\nconst theme = inject(themeConfig)!; // Notice this line\r\n```\r\nIn Header.vue, themeConfig exists in myTheme/src/compositions/configProvider.ts, \r\nbut in .vitepress/cache/deps/myTheme.js, it also exits a themeConfig.\r\ntwo themeConfig, two Symbol.\r\n***In the result***, provide/inject is fail.\r\n\r\n\r\nIn development this is bad, in production, the configProvider module is not extracted, the themeConfig variable is unique.\n\n### Reproduction\n\nas mentioned earlier\n\n### Expected behavior\n\nIn development, some es module that come from node_modules ain't extracted, the variable don't be duplicated.\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 11 10.0.22000\r\n Binaries:\r\n Node: 18.16.0\r\n pnpm: 8.6.0\r\n npmPackages:\r\n vitepress: 1.0.0-rc.31\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.",[2899,2902],{"name":2900,"color":2901},"need more info","bdbefc",{"name":2868,"color":2869},3292,"Theme is made into npm package, if use the theme, Symbol is duplicated in dev.","2024-03-07T11:19:22Z","https://github.com/vuejs/vitepress/issues/3292",0.74483436,{"description":2909,"labels":2910,"number":2911,"owner":2871,"repository":2872,"state":2912,"title":2913,"updated_at":2914,"url":2915,"score":2916},"**Is your feature request related to a problem? Please describe.**\r\n\r\nCurrently a VuePress user and excited to move to VitePress (primarily because I've written my own VP themes from scratch, and this seems to be the main design goal for v3) but:\r\n\r\n- there are various key differences between the frameworks (bundler, plugins, config)\r\n- there are significant intentional omissions in v3 (rather large list in the docs)\r\n- it's still in development\r\n\r\nAs a new / migrating user, it's a bit of a minefield and difficult to know where to start when something is omitted.\r\n\r\n**Describe the solution you'd like**\r\n\r\nRather than clogging up the issues with questions, it would be cool to get an Awesome VitePress list going, so users could find alternative plugins, or dig through the code of known solutions (i.e. the Vue Blog) and see how it's been solved before.\r\n\r\n**Describe alternatives you've considered**\r\n\r\nClog up the issues with questions, bug @kiaking on Twitter, Google solutions, etc.\r\n\r\n**Additional context**\r\n\r\nHappy to help search and review resources to get it started.\r\n\r\n",[],253,"closed","List of examples or some kind of Awesome VitePress repo","2023-01-28T15:54:22Z","https://github.com/vuejs/vitepress/issues/253",0.68983096,{"description":2918,"labels":2919,"number":2920,"owner":2871,"repository":2872,"state":2912,"title":2921,"updated_at":2922,"url":2923,"score":2924},"### Is your feature request related to a problem? Please describe.\n\nI'm using VitePress to document our coding standards and our design system. I want to show examples of the code we would use (HTML and Vue components) *and* how that code would render.\r\n\r\nI can import and use Vue components in the markdown (and HTML) without issue. But to show both the \"live\" and \"source\" views of that code, I have to copy my live code into a separate markdown code block, which means now I have *two* blocks of code to manage and synchronize for each example.\n\n### Describe the solution you'd like\n\nI'd like a new directive for \"```\" code blocks that, when viewed in VitePress, shows up as a tabbed interface with two tabs: (1) the rendered version of that code (using the normal rendering done by VitePress, supporting Vue and HTML), and (2) the normal way the code block would be otherwise rendered.\r\n\r\nI *believe* this would simply require detecting this directive, duplicating the code within the block as non-fenced code, and wrapping the pair in a simple tabbed Vue component.\r\n\r\nObviously for more complex examples, the VitePress version of the live code will differ from what needs to be shown to the user, so that is a challenge (the Vue docs themselves have this challenge). But for simple examples of using Vue components and HTML with no additional script involved, it would really help.\r\n\r\nMy suggestion would be something like \"```html:live\", where the \":live\" bit either comes before or after any row number highlights (I don't think it would matter).\n\n### Describe alternatives you've considered\n\nCopying and pasting between markdown code blocks to markdown live code, keeping them synchronized as the code is updated.\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.",[],554,"\"Live\" Code Blocks","2023-01-21T14:20:27Z","https://github.com/vuejs/vitepress/issues/554",0.695227,{"description":2926,"labels":2927,"number":2928,"owner":2871,"repository":2872,"state":2912,"title":2929,"updated_at":2930,"url":2931,"score":2932},"Might be a great idea to curate docs powered by vitepress for inspiration or examples.\r\nA few I can think of besides vite, vue and vitest\r\n- [stackblitz](https://developer.stackblitz.com/)\r\n- [adocs](https://adocs.vercel.app)\r\n- [dicebear](https://www.dicebear.com/)\r\n- [fakerjs](https://fakerjs.dev/)",[],2201,"docs: make a list of docs powered by vitepress ","2023-04-24T00:04:06Z","https://github.com/vuejs/vitepress/issues/2201",0.7085087,{"description":2934,"labels":2935,"number":2940,"owner":2871,"repository":2872,"state":2912,"title":2941,"updated_at":2942,"url":2943,"score":2944},"Currently there are lot of repeated icons in generated dist/**/*.html files. Those can be avoided by these.",[2936,2937],{"name":2868,"color":2869},{"name":2938,"color":2939},"perf","378A61",3399,"Switch to CSS icons or SVG sprites","2024-02-25T00:05:04Z","https://github.com/vuejs/vitepress/issues/3399",0.7222145,{"description":2946,"labels":2947,"number":2948,"owner":2871,"repository":2872,"state":2912,"title":2949,"updated_at":2950,"url":2951,"score":2952},"**Is your feature request related to a problem? Please describe.**\r\nI would like the ability to configure markdown options similar to what is availiable in `vuepress`.\r\n\r\n**Describe the solution you'd like**\r\nIn the `config.js` file would like to be able to toggle markdown options added by `vitepress` and add my own markdown plugins. It seems that most of this was already scaffolded out and the markdown options just need to be exposed to the user config.\r\n\r\n**Describe alternatives you've considered**\r\nN/a\r\n\r\n**Additional context**\r\nN/a",[],127,"Configure markdown options","2023-01-21T16:24:15Z","https://github.com/vuejs/vitepress/issues/127",0.7234794,{"description":2954,"labels":2955,"number":2962,"owner":2871,"repository":2872,"state":2912,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Is your feature request related to a problem? Please describe.\n\nrepresenting the steps in a very clear way.\n\n### Describe the solution you'd like\n\nproviding a \"Steps\" markdown extension\n\n### Describe alternatives you've considered\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] 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.",[2956,2959],{"name":2957,"color":2958},"build","377ba8",{"name":2960,"color":2961},"theme","0754FB",3159,"feat: adding the \"Steps\" markdown extension","2023-12-27T00:04:27Z","https://github.com/vuejs/vitepress/issues/3159",0.72741336,["Reactive",2968],{},["Set"],["ShallowReactive",2971],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fa-ftIQgTe2drhYSbzcFyj55FGhnq0PadGOpWQUh-qBE":-1},"/vuejs/vitepress/883"]