\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.7550278,{"description":3062,"labels":3063,"number":3065,"owner":3023,"repository":3024,"state":3037,"title":3066,"updated_at":3067,"url":3068,"score":3069},"### 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.",[3064],{"name":3046,"color":3047},1084,"ignoreDeadLinks doesn't work","2023-01-21T14:30:01Z","https://github.com/vuejs/vitepress/issues/1084",0.7558018,{"description":3071,"labels":3072,"number":3076,"owner":3023,"repository":3024,"state":3037,"title":3077,"updated_at":3078,"url":3079,"score":3080},"### Discussed in https://github.com/vuejs/vitepress/discussions/1255\r\n\r\n\u003Cdiv type='discussions-op-text'>\r\n\r\n\u003Csup>Originally posted by **akil-rails** August 30, 2022\u003C/sup>\r\nCurrently there is a global configuration to display Line numbers in all code blocks: https://vitepress.vuejs.org/guide/markdown#line-numbers\r\n\r\nIt will be great to have line numbers only for some code blocks, and not for all. \r\n\r\nIn certain cases (like for [example](https://docs.apigee.com/api-platform/troubleshoot/runtime/500-badformdata)) the code block is showing a sample message; which doesn't need line numbers. \u003C/div>",[3073],{"name":3074,"color":3075},"build","377ba8",1256,"Line Numbers Only for some Code Blocks","2023-01-21T14:17:05Z","https://github.com/vuejs/vitepress/issues/1256",0.7622753,{"description":3082,"labels":3083,"number":3085,"owner":3023,"repository":3024,"state":3037,"title":3086,"updated_at":3087,"url":3088,"score":3089},"### Is your feature request related to a problem? Please describe.\n\nI would like to format sidebar items' text content as inline code blocks\r\n\r\nHere we can see I attempted providing markdown, and also edited the first three items in the browser to be `code` tags\r\n\u003Cimg width=\"266\" alt=\"image\" src=\"https://user-images.githubusercontent.com/5033303/195881206-206b8123-5c67-43ed-a2ab-221f82fe2e5c.png\">\r\n\n\n### Describe the solution you'd like\n\n- allow markdown in SidebarItem's `text` property\r\n- allow HTML strings in SidebarItem's `text` property\n\n### Describe alternatives you've considered\n\njust using the default display\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.",[3084],{"name":3034,"color":3035},1486,"allow HTML strings in SidebarItem `text`","2023-01-21T14:22:59Z","https://github.com/vuejs/vitepress/issues/1486",0.76298505,{"description":3091,"labels":3092,"number":3094,"owner":3023,"repository":3024,"state":3037,"title":3095,"updated_at":3096,"url":3097,"score":3098},"### Describe the bug\r\n\r\nHero image don't bind after deployment If place logo.png to /images it does not work.\r\nThis image does not compile to the assets and on real site can't get image.Please fix\r\n\r\n### Reproduction\r\n\r\nSet hero section\r\nSet image:\r\n src: logo.png\r\n\r\n### Expected behavior\r\n\r\nShould can place logo(any images) to images directory\r\n\r\n### System Info\r\n\r\n```Text\r\nafter deploy\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] Check if you're on the [latest VitePress version](https://github.com/vuejs/vitepress/releases/latest).\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3093],{"name":3046,"color":3047},3813,"Hero section image error","2024-04-28T12:24:41Z","https://github.com/vuejs/vitepress/issues/3813",0.76413214,{"description":3100,"labels":3101,"number":3106,"owner":3023,"repository":3024,"state":3037,"title":3107,"updated_at":3108,"url":3109,"score":3110},"### Describe the bug\n\nIn alpha 3, when using code block language aliases, I receive this error: `The language 'my-lang-alias' is not loaded, falling back to 'txt' for syntax highlighting.`\n\nAliases worked correctly in alpha 2.\n\n### Reproduction\n\nStackBlitz repro here (code block is on the **Get Started** page):\n\n[https://stackblitz.com/edit/vite-eswufd7t?file=docs%2Fexample.md](https://stackblitz.com/edit/vite-eswufd7t?file=docs%2Fexample.md)\n\n### Expected behavior\n\nLanguage aliased added to **defineConfig** > **markdown** > **languageAlias** are available as code block languages.\n\n### System Info\n\n```Text\nSystem:\n OS: Linux 5.15 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)\n CPU: (20) x64 12th Gen Intel(R) Core(TM) i7-12700T\n Memory: 23.13 GB / 31.19 GB\n Container: Yes\n Shell: 5.2.21 - /bin/bash\n Binaries:\n Node: 22.13.0 - /usr/bin/node\n npm: 10.9.2 - /usr/bin/npm\n pnpm: 9.6.0 - /usr/bin/pnpm\n npmPackages:\n vitepress: ^2.0.0-alpha.3 => 2.0.0-alpha.3\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.",[3102,3103],{"name":3074,"color":3075},{"name":3104,"color":3105},"upstream","BF29ED",4581,"languageAlias broken in 2.0.0-alpha.3","2025-03-06T04:44:32Z","https://github.com/vuejs/vitepress/issues/4581",0.7641592,{"description":3112,"labels":3113,"number":3115,"owner":3023,"repository":3024,"state":3037,"title":3116,"updated_at":3117,"url":3118,"score":3119},"### Describe the bug\n\nI created a monorepo containing 2 packages:\n1. the package i'm building (flyonui-vue)\n2. the docs about it\n\nthe docs use the published version of the package.\n\nwhen i build the docs in my local environment everything works fine. but then when i build them through the github action i get\n\n```\nRun yarn build:docs\n\n vitepress v1.5.0\n\n- building client + server bundles...\nx Build failed in [6](https://github.com/michaelcozzolino/flyonui-vue/actions/runs/12852703212/job/35835005640#step:7:7)[7](https://github.com/michaelcozzolino/flyonui-vue/actions/runs/12852703212/job/35835005640#step:7:8)7ms\n✖ building client + server bundles...\nbuild error:\n[commonjs--resolver] Failed to resolve entry for package \"flyonui-vue\". The package may have incorrect main/module/exports specified in its package.json.\n[commonjs--resolver] Failed to resolve entry for package \"flyonui-vue\". The package may have incorrect main/module/exports specified in its package.json.\n at packageEntryFailure (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:46637:15)\n at resolvePackageEntry (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:46634:3)\n at tryNodeResolve (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:46450:16)\n at Object.resolveId (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:46200:19)\n at file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/rollup/dist/es/shared/node-entry.js:20936:40\n at async PluginDriver.hookFirstAndGetPlugin (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/rollup/dist/es/shared/node-entry.js:20[8](https://github.com/michaelcozzolino/flyonui-vue/actions/runs/12852703212/job/35835005640#step:7:9)36:28)\n at async resolveId (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/rollup/dist/es/shared/node-entry.js:1[9](https://github.com/michaelcozzolino/flyonui-vue/actions/runs/12852703212/job/35835005640#step:7:10)440:26)\n at async ModuleLoader.resolveId (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/rollup/dist/es/shared/node-entry.js:19869:15)\n at async Object.resolveId (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/vitepress/node_modules/vite/dist/node/chunks/dep-CB_7IfJ-.js:12833:[10](https://github.com/michaelcozzolino/flyonui-vue/actions/runs/12852703212/job/35835005640#step:7:11))\n at async PluginDriver.hookFirstAndGetPlugin (file:///home/runner/work/flyonui-vue/flyonui-vue/node_modules/rollup/dist/es/shared/node-entry.js:20836:28)\nError: Process completed with exit code 1.\n\n```\n\neven though the package.json seems to be completely right.\n\nthe workflow outcome can be seen here\nhttps://github.com/michaelcozzolino/flyonui-vue/actions/runs/12852703212/job/35835005640\n\n\n\n### Reproduction\n\nonly through the github action (deploy.yml workflow) as it's for github pages.\n\nto deploy the docs on local:\n```\ngit clone https://github.com/michaelcozzolino/flyonui-vue.git\n\nin the root of the project run:\nyarn install\nyarn build\n```\n`yarn build` will automatically build the package and the docs, alternatively if you want to build only the docs you can run `yarn build:docs` as the github workflow does.\n\n### Expected behavior\n\nthe action should be successful as it is on local.\n\n### System Info\n\n```Text\nSystem:\n OS: Linux 6.8 Ubuntu 24.04.1 LTS 24.04.1 LTS (Noble Numbat)\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz\n Memory: 16.29 GB / 30.23 GB\n Container: Yes\n Shell: 5.2.21 - /bin/bash\n Binaries:\n Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node\n Yarn: 4.6.0 - ~/.yarn/bin/yarn\n npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm\n Browsers:\n Brave Browser: 132.1.74.48\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.",[3114],{"name":3046,"color":3047},4497,"[commonjs--resolver] Failed to resolve entry for package during vitepress build on github pages","2025-01-27T04:43:01Z","https://github.com/vuejs/vitepress/issues/4497",0.7665841,["Reactive",3121],{},["Set"],["ShallowReactive",3124],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2MyJ8ZeIS5LWeJMye1i4Rla5hV6wQo7WiB425BV-TlI":-1},"/vuejs/vitepress/1669"]