\r\n\u003C/div>\r\n```\r\n但显然`# 标题一 `可以被成功渲染为标题,而`## {{item[0].title}}`却只能是纯文本,因为这部分根本不会经过`markdown`渲染器的渲染。\n\n### Describe the solution you'd like\n\n我理解是否可以添加一个标识,比如:\r\n```js\r\n\u003Cdiv v-for='item in beijing'>\r\n ## {{item[0].title}}\r\n ::: markdown-block\r\n ## title\r\n // content\r\n ::: \r\n \u003Cmany-pictures :srcImgs='item' :lazy='true' />\r\n\u003C/div>\r\n\r\n```\r\n然后预期中这个块会被`markdown`渲染器渲染之后再交给`vue`相关的编译器去解析。\r\n如果可以支持这个功能,结合`vue`中的`v-if/v-for`等条件控制语句,可以帮助我实现许多页面的快速编写\n\n### Describe alternatives you've considered\n\n目前我只能直接在`v-for`语句中编写纯`html`语法的内容,这对于我来说有一定的心智负担,还是以上述的例子来说,这是我目前的替代方案:\r\n```html\r\n---\r\nsidebar: false\r\n---\r\n\u003Cscript setup>\r\nimport { beijing } from '../const/imgLink.ts'\r\n\u003C/script>\r\n# 标题一\r\n\u003Cdiv v-for='item in beijing'>\r\n \u003Ch2 :id=\"item[0].title\" tabindex=\"-1\">\r\n {{item[0].title}}\r\n \u003Ca class=\"header-anchor\" :href=\"`#${item[0].title}`\" aria-hidden=\"true\">#\u003C/a>\r\n \u003C/h2>\r\n \u003Cmany-pictures :srcImgs='item' :lazy='true' />\r\n\u003C/div>\r\n```\n\n### Additional context\n\n我也许可以尝试实现该功能\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.",[],1570,"在模板语法或标签语法中,是否可以增加一个类似块一样的标识,以至于块中的内容可以被`markdown`解析器识别并渲染为`html`","2023-01-21T14:20:46Z","https://github.com/vuejs/vitepress/issues/1570",0.71968365,{"description":2925,"labels":2926,"number":2928,"owner":2877,"repository":2878,"state":2889,"title":2929,"updated_at":2930,"url":2931,"score":2932},"### Describe the bug\n\n\r\n\r\n\r\n\r\n\r\n### video\r\n[see event video](https://warmthsea.github.io/test.mp4)\n\n### Reproduction\n\n1、open [Vite](https://vitejs.dev/) or [me self ](https://warmthsea.github.io/vitepress-starter/) in **Phone | IOS version > 15.1**\r\n2、click menu open Popper\r\n3、click menu close Popper\r\n4、click left logo and name\n\n### Expected behavior\n\nnormal display\n\n### System Info\n\n```shell\nPhone 13\r\nIOS Version > 15.1\r\nSafari、Firefox、QQ、WeChat\r\nHorizontal screen, vertical screen\n```\n\n\n### Additional context\n\nMultiple Apple 13 appear\r\nIOS Version 14.1 normal display\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.",[2927],{"name":2898,"color":2899},1029,"Phone Style:ios version > 15.1, click header logo / menu button,Abnormal white blocks appear","2023-01-21T14:30:12Z","https://github.com/vuejs/vitepress/issues/1029",0.7202548,{"description":2934,"labels":2935,"number":2936,"owner":2877,"repository":2878,"state":2889,"title":2937,"updated_at":2938,"url":2939,"score":2940},"### Is your feature request related to a problem? Please describe.\n\nWhile Vue is a fantastic rendering engine, some people are more used to working with others. Or sometimes, companies decide on a specific engine for the whole company, and having one project that doesn't use it can be seen as a showstoper for using a piece of technology.\r\n\r\n\n\n### Describe the solution you'd like\n\nConsidering the name of this project is called Vitepress, I think it might be interesting to support other types of renderer (e.g. React) via official plugins like [Vite does](https://vitejs.dev/plugins/#vitejs-plugin-react).\r\n\r\nThat way, people could use the incredible features and toolset provided by Vitepress with the rendering technology of their choice. A little bit like [Astro](https://astro.build/) is going with their framework.\r\n\r\nI do understand that Vitepress is Vuepress's spiritual successor, but I have the impression that this could benefit a lot more people considering how powerful and useful Vitepress is. Even more so considering altneratives like Docusaurus are built on older and slower sets of technologies.\n\n### Describe alternatives you've considered\n\nI've seen on a twitter thread that it was possible to render react components somehow, though I'm not sure I've seen this documented anywhere.\n\n### Additional context\n\nn/a\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.",[],1532,"Support for Other Types of Renderer","2023-01-21T14:22:45Z","https://github.com/vuejs/vitepress/issues/1532",0.7287329,{"description":2942,"labels":2943,"number":2945,"owner":2877,"repository":2878,"state":2889,"title":2946,"updated_at":2947,"url":2948,"score":2949},"### Describe the bug\n\nWhen I enable the `ignoreDeadLinks` option in `/docs/.vitepress/config.js`, `yarn docs:build` still fails with the reason being `One or more pages contain dead links.`\n\n### Reproduction\n\nCreate a new vitepress project.\r\nIn `/docs/.vitepress/config.js`:\r\n```js\r\nexport default {\r\n ignoreDeadLinks: true,\r\n title: \"test\",\r\n description: \"test stuff\"\r\n}\r\n```\r\n\r\nIn `/docs/api/index.md`:\r\n```md\r\n[test](./test)\r\n```\n\n### Expected behavior\n\nIt is expected that the build process will succeed, because it should ignoreDeadLinks instead of failing because of them.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (12) x64 Intel(R) Core(TM) i7-8700K CPU @ 3.70GHz \r\n Memory: 6.63 GB / 15.93 GB\r\n Binaries:\r\n Node: 18.5.0 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - C:\\Program Files\\nodejs\\yarn.CMD\r\n npm: 8.15.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.71) \r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.4 => 1.0.0-alpha.4\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.",[2944],{"name":2909,"color":2910},1084,"ignoreDeadLinks doesn't work","2023-01-21T14:30:01Z","https://github.com/vuejs/vitepress/issues/1084",0.731487,{"description":2951,"labels":2952,"number":2955,"owner":2877,"repository":2878,"state":2889,"title":2956,"updated_at":2957,"url":2958,"score":2959},"### Describe the bug\n\n`rewrite` rule doesn't work correctly when create new markdown file.\n\n### Reproduction\n\n1, Set `rewrite`\r\n\r\n```js\r\n// vitepress/config.js\r\nrewrite: [`en/:rest*`]: ':rest*'\r\n```\r\n\r\n2, Create new markdown file `docs/en/test.md`\r\n\r\n3, Expect visit file by url `/test`, but it redirect to `/en/test`.\r\n\r\n4, Restart dev server, problem resolved.\n\n### Expected behavior\n\nExpect `rewrite` rule work correctly when create new markdown file.\n\n### System Info\n\n```Text\nvitepress: 1.5.0\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.",[2953,2954],{"name":2909,"color":2910},{"name":2871,"color":2872},4385,"Rewrite not work when create new markdown file","2025-03-08T04:41:55Z","https://github.com/vuejs/vitepress/issues/4385",0.734716,{"description":2961,"labels":2962,"number":2964,"owner":2877,"repository":2878,"state":2889,"title":2965,"updated_at":2966,"url":2967,"score":2968},"### Describe the bug\n\nInstead of italic font rendering, only regular font is displayed in Safari.\n\n### Reproduction\n\nWrite a markdown with _italic rendering_, and open in Safari.\n\n### Expected behavior\n\nExpected to render italic font.\n\n### System Info\n\n```shell\nnot important\n```\n\n\n### Additional context\n\nRelevant issue: https://github.com/vuejs/vitepress/issues/759\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.",[2963],{"name":2898,"color":2899},1558,"Italic font rendering doesn't work in Safari","2023-01-21T14:17:11Z","https://github.com/vuejs/vitepress/issues/1558",0.7376194,["Reactive",2970],{},["Set"],["ShallowReactive",2973],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fWljSDvv9hcHBLCO0a2f9vNxF3wLxK9p_pS0XEe9U2NQ":-1},"/vuejs/vitepress/1728"]