\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.7058201,{"description":2879,"labels":2880,"number":2884,"owner":2871,"repository":2872,"state":2885,"title":2886,"updated_at":2887,"url":2888,"score":2889},"**Describe the bug**\r\nThe typing for `UserConfig` includes a `markdown` property which gives you access to the **mardown-it** options. This is an incredibly useful feature but sadly even though I put this into the `.vitepress/config.js` and it is indeed picked up and placed into the UserConfig that property is then ignored and not processed by the `createVitePressPlugin()`. \r\n\r\nI can create a PR for this if that of any help.\r\n\r\n**To Reproduce**\r\nadd a `.vitepress/config.js` which includes:\r\n\r\n```js\r\nmodules.exports = {\r\n // ...\r\n markdown: {\r\n config: md => { console.log(\"made it\") }\r\n }\r\n}\r\n```\r\n\r\n**Expected behavior**\r\nit should report \"made it\" when running `vitepress dev`\r\n\r\n**System Info**\r\n- vitepress version: 0.7.4\r\n- vite version: v1.0.0-rc.9\r\n- Node version: 12.19.0\r\n- OS version: macOS\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[2881],{"name":2882,"color":2883},"question","5D5FAE",133,"closed","UserConfig allows `markdown` prop but it is then ignored","2023-01-21T16:24:14Z","https://github.com/vuejs/vitepress/issues/133",0.6233395,{"description":2891,"labels":2892,"number":2893,"owner":2871,"repository":2872,"state":2885,"title":2894,"updated_at":2895,"url":2896,"score":2897},"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.66868293,{"description":2899,"labels":2900,"number":2901,"owner":2871,"repository":2872,"state":2885,"title":2902,"updated_at":2903,"url":2904,"score":2905},"**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,"List of examples or some kind of Awesome VitePress repo","2023-01-28T15:54:22Z","https://github.com/vuejs/vitepress/issues/253",0.669633,{"description":2907,"labels":2908,"number":2909,"owner":2871,"repository":2872,"state":2885,"title":2910,"updated_at":2911,"url":2912,"score":2913},"**Is your feature request related to a problem? Please describe.**\r\n\r\nin VuePress we can pass `configureWebpack` to the vuepress config to modify webpack behaviour. useful to add module resolve and aliases, plugins etc.\r\n\r\nhttps://vuepress.vuejs.org/config/#configurewebpack\r\n\r\n**Describe the solution you'd like**\r\n\r\nAllow to do the same (or similar) with vitepress\r\n\r\n**Describe alternatives you've considered**\r\n\r\nanything that'll result in the same behavior\r\n\r\n",[],179,"configureWebpack in vitepress config","2023-01-21T16:24:09Z","https://github.com/vuejs/vitepress/issues/179",0.6708597,{"description":2915,"labels":2916,"number":2917,"owner":2871,"repository":2872,"state":2885,"title":2918,"updated_at":2919,"url":2920,"score":2921},"Is Vitepress's config.js the same as Vuepress's? How do I configure nav and sidebar for vitepress",[],213,"About the config. Js !","2023-01-21T16:24:02Z","https://github.com/vuejs/vitepress/issues/213",0.6725042,{"description":2923,"labels":2924,"number":2925,"owner":2871,"repository":2872,"state":2885,"title":2926,"updated_at":2927,"url":2928,"score":2929},"**Is your feature request related to a problem? Please describe.**\r\nCurrently there seems to be no way to extend the Vite config used by vitepress (or at least it's not clear how to do it).\r\nIt would be great to have that ability to specify aliases that are used inside of components that are not part of VitePress.\r\n\r\nIn our case we have a component library in `src`, and the docs in `docs`, but components imported in VitePress use `#components/button` imports (for example) and VitePress can't resolve those as there's no way to set up aliases for it.\r\n\r\n**Describe the solution you'd like**\r\nA way to extend vite config and/or specify aliases.\r\n\r\n**Describe alternatives you've considered**\r\nI tried creating a vite config in the root, but that prevents TS based SFC's from compiling properly (I think it overwrites the internal config).\r\n\r\n**Additional context**\r\nA quick screenshot of our setup:\r\n\r\n\r\n`docs/.vitepress` hosts VitePress, but the root is Vite itself (library mode).",[],241,"Ability to extend vite config","2023-01-21T14:20:28Z","https://github.com/vuejs/vitepress/issues/241",0.6963975,{"description":2931,"labels":2932,"number":2933,"owner":2871,"repository":2872,"state":2885,"title":2934,"updated_at":2935,"url":2936,"score":2937},"**Is your feature request related to a problem? Please describe.**\r\nI am looking for a way to pass some configuration to `@vitejs/plugin-vue`, specifically `template.compilerOptions.isCustomElement`). ([code](https://github.com/vuejs/vitepress/blob/c11055c5fb31ff31502400de3e5f6f05011edd1d/src/node/plugin.ts#L33)). \r\n\r\n**Describe the solution you'd like**\r\nI was think that extracting these options from `.vitepress/config.js` shouldn't be too much work. Are there any other options besides `isCustomElement` that would be worth adding?\r\n\r\n**Describe alternatives you've considered**\r\n\r\n**Additional context**\r\n",[],214,"Expose configuration for @vitejs/plugin-vue","2023-01-21T16:23:57Z","https://github.com/vuejs/vitepress/issues/214",0.69908017,{"description":2939,"labels":2940,"number":2941,"owner":2871,"repository":2872,"state":2885,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Is your feature request related to a problem? Please describe.\n\nI have a lot of md files (10K+) that want to serve with vitepress, which contains something made vitepress unhappy (e.g. un closed tags, or `{{ xxx }}`), all I want to do is simply serve them as html pages, without any vue-parsing stuff, but vitepress keep complain about the those things while building. There're too many files for me to fix them one by one, it's nearly impossible.\n\n### Describe the solution you'd like\n\nprovide an option to completely op-out the vue related processing stuff, just parse and display markdowns\n\n### Describe alternatives you've considered\n\nother alternatives are also welcome as long as it solved this kind of problem.\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.",[],3452,"Can we provide an option to completely op-out the vue related processing stuff?","2024-01-25T00:04:47Z","https://github.com/vuejs/vitepress/issues/3452",0.6996094,{"description":2947,"labels":2948,"number":2949,"owner":2871,"repository":2872,"state":2885,"title":2950,"updated_at":2951,"url":2952,"score":2953},"### Is your feature request related to a problem? Please describe.\n\nUsers can customize the set of plugins for markdown\n\n### Describe the solution you'd like\n\nMarkdown provides plugin configuration options or plugin installation hook functions\r\n```js\r\nmarkdown:{\r\n ....\r\n \r\n plugins:[\r\n [plugin1,options],\r\n ....\r\n ]\r\n\r\n}\r\n\r\n```\r\n\r\nor\r\n\r\n```js\r\n\r\nmarkdown:{\r\n ....\r\n \r\n pluginHook(md){\r\n md .use(plugin1)\r\n }\r\n\r\n}\r\n\r\n\r\n\r\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.",[],2789,"Open Markdown plugin mechanism","2023-08-23T00:04:08Z","https://github.com/vuejs/vitepress/issues/2789",0.7031426,["Reactive",2955],{},["Set"],["ShallowReactive",2958],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fbxWnhFJkmIikxUvgm8nM33GGoA37hBfZ-eaIHh9wovM":-1},"/vuejs/vitepress/127"]