\r\n```\r\nIt works fine with the localhost via the command ` yarn docs:dev`\r\nbut when `yarn docs:build`, I got an error.\r\nHow can I do?\n\n### Describe the solution you'd like\n\nSupport the video control.\r\n\r\nI set up the site in LAN and won't expose to the WAN, the storage is no problem.\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.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.",[],1477,"embed video in markdown with vitepress","2023-01-21T14:25:05Z","https://github.com/vuejs/vitepress/issues/1477",0.7629976,{"description":3101,"labels":3102,"number":3106,"owner":3043,"repository":3044,"state":3087,"title":3107,"updated_at":3108,"url":3109,"score":3110},"Currently one needs to do this:\r\n\r\n```yaml\r\n---\r\nlayout: home\r\nhero:\r\n image:\r\n light:\r\n src: /light.svg\r\n alt: logo\r\n dark:\r\n src: /dark.svg\r\n alt: logo\r\n---\r\n```\r\n\r\nThis can be simplified to:\r\n\r\n```yaml\r\n---\r\nlayout: home\r\nhero:\r\n image:\r\n light: /light.svg\r\n dark: /dark.svg\r\n alt: logo\r\n---\r\n```",[3103],{"name":3104,"color":3105},"theme","0754FB",1436,"allow specifying common alt for logo","2023-01-21T14:25:07Z","https://github.com/vuejs/vitepress/issues/1436",0.764935,{"description":3112,"labels":3113,"number":3114,"owner":3043,"repository":3044,"state":3087,"title":3115,"updated_at":3116,"url":3117,"score":3118},"I noticed that `VitePress` imports `@vue/shared`, but it appears to only use one of its methods. However, there are more methods available in `@vue/shared`. Should `VitePress` directly import these additional methods from `@vue/shared` to reduce redundancy in the code?\r\n\r\nHere is one case of what I mentioned:\r\n\r\n`vitepress`:\r\nhttps://github.com/vuejs/vitepress/blob/a6a7645e942cc63c57ca5d79da4b76dee76d8a96/src/node/config.ts#L229\r\n\r\n`@vue/shared`:\r\nhttps://github.com/vuejs/core/blob/db374e54c9f5e07324728b85c74eca84e28dd352/packages/shared/src/general.ts#L52\r\n\r\nSeems that can directly use `import { isObject } from '@vue/shared`.",[],3720,"Reuse some of the existing methods in `@vue/shared`","2024-04-28T12:24:53Z","https://github.com/vuejs/vitepress/issues/3720",0.7673714,{"description":3120,"labels":3121,"number":3123,"owner":3043,"repository":3044,"state":3087,"title":3124,"updated_at":3125,"url":3126,"score":3127},"### 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.",[3122],{"name":3084,"color":3085},3813,"Hero section image error","2024-04-28T12:24:41Z","https://github.com/vuejs/vitepress/issues/3813",0.7682467,{"description":3129,"labels":3130,"number":3131,"owner":3043,"repository":3044,"state":3087,"title":3132,"updated_at":3133,"url":3134,"score":3135},"\nHello\n\nI've developed a VitePress plugin for diagram generation - https://github.com/vuesence/vitepress-plugin-diagrams\n\nThe plugin uses the Kroki service to convert text-based diagram definitions into SVG files.\n\nI've redefined `md.renderer.rules.fence` to handle this.\n\nSince diagram generation is asynchronous, I return a `\u003Cfigure>` element immediately while saving the SVG file after receiving the response from Kroki. This works fine in general.\n\nHowever, VitePress throws an error because it cannot find the referenced SVG files during the build.\n\nTo work around this, I tried creating placeholder SVG files before returning from `md.renderer.rules.fence`, but this didn't help. It appears that VitePress scans the directory contents before processing the build.\n\nAny suggestions on how to prevent this error?",[],4560,"VitePress cannot locate files that are generated during the build process","2025-02-23T04:43:38Z","https://github.com/vuejs/vitepress/issues/4560",0.77081484,["Reactive",3137],{},["Set"],["ShallowReactive",3140],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fEN59InQW6BXzKPaAdAgeXbPRgBDEJQ4yV_cErE1l_nA":-1},"/vuejs/vitepress/2182"]