\n```\n\n> 可以解析:\n\n```md\n\u003Cimg src=\"./img/gmzyjx-a.png\" style=\"zoom:60%;\" />\n\n\n```\n\n### Reproduction\n\n\n\n### Expected behavior\n\n\u003Cimg src=\"img/gmzyjx-a.png\" style=\"zoom:60%;\" /> 这种写法正常应该能解析才对,这是符合html标准的\n\n### System Info\n\n```Text\nnpm warn Unknown user config \"home\". This will stop working in the next major version of npm.\nNeed to install the following packages:\nenvinfo@7.14.0\nOk to proceed? (y) y\n\n\n System:\n OS: Windows 10 10.0.19045\n CPU: (8) x64 Intel(R) Core(TM) i7-3770 CPU @ 3.40GHz\n Memory: 4.10 GB / 15.96 GB\n Binaries:\n Node: 22.11.0 - C:\\Program Files\\nodejs\\node.EXE \n Yarn: 1.22.22 - ~\\AppData\\Roaming\\npm\\yarn.CMD \n npm: 11.2.0 - C:\\Program Files\\nodejs\\npm.CMD \n pnpm: 10.6.2 - ~\\AppData\\Roaming\\npm\\pnpm.CMD \n Browsers: {}\n npmPackages:\n vitepress: ^1.6.3 => 1.6.3\n```\n\n### Additional context\n\n\n\n> package.json\n\n```json\n{\n \"devDependencies\": {\n \"vitepress\": \"^1.6.3\",\n \"vue\": \"^3.5.13\"\n },\n \"scripts\": {\n \"dev\": \"vitepress dev\",\n \"build\": \"vitepress build\",\n \"preview\": \"vitepress preview\"\n }\n}\n```\n\n\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.",[2867],{"name":2868,"color":2869},"upstream","BF29ED",4618,"vuejs","vitepress","open","部分图片写法无法解析","2025-03-12T06:17:09Z","https://github.com/vuejs/vitepress/issues/4618",0.78496885,{"description":2879,"labels":2880,"number":2887,"owner":2871,"repository":2872,"state":2873,"title":2888,"updated_at":2889,"url":2890,"score":2891},"### Is your feature request related to a problem? Please describe.\n\nGitHub-flavored Alerts features 5 colors while the custom containers only feature 4. I would like to avoid mixing the syntaxes to create colored containers.\n\n### Describe the solution you'd like\n\nAdd `important` custom containers that feature the same color as their github counterpart.\n\n### Describe alternatives you've considered\n\nMixing syntaxes.\r\nUsing the `tip` custom container.\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,2884],{"name":2882,"color":2883},"build","377ba8",{"name":2885,"color":2886},"stale","ededed",3928,"Add `important` to custom containers","2025-03-02T18:09:03Z","https://github.com/vuejs/vitepress/issues/3928",0.8151324,{"description":2893,"labels":2894,"number":2897,"owner":2871,"repository":2872,"state":2873,"title":2898,"updated_at":2899,"url":2900,"score":2901},"### Is your feature request related to a problem? Please describe.\r\n\r\nTo inject HTML tags in a page's `\u003Chead>`, as far as I understand the solution is to use the `head` or `transformHead` options.\r\n\r\nMy issue is that I’d like to reference assets in the `\u003Chead>`, for instance to link to a SVG favicon (same image for all pages) or to an opengraph image (different image for each page).\r\n\r\nCurrently I’m handling this by using absolute paths from the root of the domain, and put those images in the `public/img` folder. So the config might look like:\r\n\r\n```js\r\nexport default {\r\n head: [\r\n ['meta', { rel: 'icon', type: 'image/svg+xml', href: `/img/theme/favicon.svg` }]\r\n ],\r\n transformHead({ pageData }) {\r\n const { og_image } = pageData.frontmatter;\r\n if (og_image) {\r\n return [['meta', {property: 'og:image', content: `/img/og/${og_image}` }]];\r\n }\r\n }\r\n}\r\n```\r\n\r\nHere the downsides are:\r\n\r\n- If we change the `base` URL and need to serve all assets under the base path, e.g. `/{base}/img/…`, we have to go back to this config and chose those hardcoded URLs.\r\n- Those assets won't have a cache-busting hash in their file name.\r\n- Missing assets are not caught at build time.\r\n\r\n\r\n### Describe the solution you'd like\r\n\r\nIt would be great if we could use Vite to handle those assets.\r\n\r\nCurrently that's not possible in `.vitepress/config.js`, since this is executed in a Node.js context and special bundler imports like `import svgFaviconUrl from './img/favicon.svg';` won't work.\r\n\r\nI wonder if that's something that could be done in the `transformHead` hook or in a different hook. If not, that's fine, I can live with the workarounds; but I just thought I'd ask.\r\n\r\n### Describe alternatives you've considered\r\n\r\nOne possible workaround would be to load those assets *somewhere*, maybe in a custom layout component, to register those assets in the Vite assets.\r\n\r\nThen in the `transformHead` hook, you actually have access to a `context.assets` array, which can look like:\r\n\r\n```js\r\n[\r\n '/assets/abcd.77593610.png',\r\n '/assets/efgh.2984b36b.gif',\r\n '/assets/ijkl.5e11e538.gif',\r\n '/assets/mnop.afe27ee2.png',\r\n // …\r\n]\r\n```\r\n\r\nThat's *almost* usable, but because it's not a manifest which also shows the original paths, it's hard to resolve the correct paths. If I’m looking for `.vitepress/theme/img/favicon.svg`, and there is another `favicon.svg` somewhere else in the assets, how do I know if I should use `/assets/favicon.2e0fc5e5.svg` or `/assets/favicon.c7ab5b73.svg`?\r\n\r\nSo I’m wondering, if the Vite manifest available at this point, and could it be exposed in the `context` for the `transformHead` hook?\r\n\r\nOr is that something that is too low-level for `transformHead`, and it should be a custom Vite plugin instead?\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.",[2895,2896],{"name":2882,"color":2883},{"name":2885,"color":2886},3161,"Accessing Vite asset URLs in head config","2025-03-02T18:10:24Z","https://github.com/vuejs/vitepress/issues/3161",0.8179752,{"description":2903,"labels":2904,"number":2909,"owner":2871,"repository":2872,"state":2873,"title":2910,"updated_at":2911,"url":2912,"score":2913},"### Is your feature request related to a problem? Please describe.\n\nIn the monorepo development mode, sometimes the rendering in docs depends on the code in another repository, so when the code in another repository changes, it is expected to trigger a hot reload of docs\n\n### Describe the solution you'd like\n\nSupport configuration to watch specified folders to trigger hot reload\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.",[2905,2908],{"name":2906,"color":2907},"need more info","bdbefc",{"name":2885,"color":2886},4221,"Support hot reload by watching files not under docs","2024-12-03T17:27:50Z","https://github.com/vuejs/vitepress/issues/4221",0.82046133,{"description":2915,"labels":2916,"number":2921,"owner":2871,"repository":2872,"state":2873,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### Is your feature request related to a problem? Please describe.\n\nI would like to have option to set separator/delimiter between nav links, the same that is created between nav links, theme selectorr, social links, etc.\n\n### Describe the solution you'd like\n\nIt could be smth like this:\r\n\r\n```js\r\n nav: [\r\n { text: 'Guide', link: '/guide' },\r\n { text: 'Config', link: '/config' },\r\n { type: 'separator' },\r\n { text: 'Something', link: '/something' },\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.",[2917,2920],{"name":2918,"color":2919},"theme","0754FB",{"name":2885,"color":2886},3407,"Add separator/delimiter between nav links","2025-03-02T18:09:58Z","https://github.com/vuejs/vitepress/issues/3407",0.8271821,{"description":2927,"labels":2928,"number":2932,"owner":2871,"repository":2872,"state":2933,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Describe the bug\n\nWhen using `markdown-it-footnote`, I manage to get footnotes on the page.\r\nHowever, when the footnote is on a header \r\n\r\nthe \"On this page\" section shows it in an undesired way\r\n\r\n\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vitepress-footnote-bug\r\n\r\n\u003Cimg width=\"995\" alt=\"image\" src=\"https://github.com/user-attachments/assets/bd1b6ba2-29cb-469d-8819-c4d7ee410a2a\">\r\n\n\n### Expected behavior\n\nThe footnote should be removed from the \"On This Page\" area\n\n### System Info\n\n```Text\nreproduced on stackblitz.\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.",[2929],{"name":2930,"color":2931},"bug: pending triage","e99695",4402,"closed","Footnote integration with \"On This Page\"","2024-12-12T04:45:58Z","https://github.com/vuejs/vitepress/issues/4402",0.78691715,{"description":2939,"labels":2940,"number":2942,"owner":2871,"repository":2872,"state":2933,"title":2943,"updated_at":2944,"url":2945,"score":2946},"### Describe the bug\r\n\r\nStep 1\r\n\r\n```vue\r\n\u003Cscript lang=\"jsx\">\r\nimport { CustomLink } from 'my-lib/dist/customLink';\r\nimport { defineComponent } from \"vue\";\r\nexport default defineComponent({\r\n render() {\r\n return (\r\n \u003CCustomLink />\r\n );\r\n },\r\n});\r\n\r\n\u003C/script>\r\n```\r\n\r\nStep 2\r\n\r\nPage md\r\n```\r\n\u003CTest />\r\n\u003Cscript setup>\r\n import Test from '../components/Test.vue'\r\n\u003C/script>\r\n\r\n````\r\n\r\n\r\nResult\r\n\r\n\r\n\r\nBut\r\n\r\nI change for example\r\n\r\n```vue\r\n\r\n\u003Cscript lang=\"jsx\">\r\nimport { defineComponent } from \"vue\";\r\nexport default defineComponent({\r\n render() {\r\n return (\r\n \u003Cdiv>\r\n Hello World :defineConfig\r\n \u003C/div>\r\n );\r\n },\r\n});\r\n\r\n\u003C/script>\r\n\r\n```\r\n\r\nworks\r\n\r\n\r\n\r\nHELP PLEASE\r\n\r\n### Reproduction\r\n\r\nno\r\n\r\n### Expected behavior\r\n\r\nI would expect the component to be seen\r\n\r\n### System Info\r\n\r\n```sh\r\n$ npx envinfo --system --npmPackages vitepress --binaries --browsers\r\nnpx: installed 1 in 2.22s\r\n\r\n System:\r\n OS: Windows 10 10.0.19045\r\n CPU: (8) x64 Intel(R) Core(TM) i7-7700HQ CPU @ 2.80GHz \r\n Memory: 5.52 GB / 15.82 GB\r\n Binaries:\r\n Node: 14.19.0 - D:\\nodejs\\node.EXE\r\n Yarn: 1.22.17 - D:\\nodejs\\yarn.CMD\r\n npm: 6.14.16 - D:\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (113.0.1774.50)\r\n Internet Explorer: 11.0.19041.1566\r\n npmPackages:\r\n vitepress: ^1.0.0-beta.1 => 1.0.0-beta.1\r\n```\r\n\r\n\r\n### Additional context\r\n\r\nI want to document my component library in react with vitepress; It might sound crazy but I had a leap of faith says Toretto hehe\r\n\r\nVite config\r\n```ts\r\nimport { defineConfig } from \"vite\";\r\nimport vueJsx from \"@vitejs/plugin-vue-jsx\";\r\nexport default defineConfig({\r\n plugins: [\r\n vueJsx(),\r\n ],\r\n});\r\n\r\n```\r\n\r\n@antfu do you know jeje?\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.",[2941],{"name":2930,"color":2931},2427,"I try to render React component from library with @vitejs/plugin-vue-jsx and failed. But i render simple div works :(","2023-06-07T00:04:34Z","https://github.com/vuejs/vitepress/issues/2427",0.7923257,{"description":2948,"labels":2949,"number":2950,"owner":2871,"repository":2872,"state":2933,"title":2951,"updated_at":2952,"url":2953,"score":2954},"\u003Cimg width=\"774\" alt=\"image\" src=\"https://user-images.githubusercontent.com/49258868/220234326-c41845d3-fb60-4f10-98f8-41b998106080.png\">\r\n\r\nCould you please tell me how to add such an outer box style to the code section in the theme",[],1965,"How to achieve the effect","2023-02-21T06:03:05Z","https://github.com/vuejs/vitepress/issues/1965",0.79489166,{"description":2956,"labels":2957,"number":2958,"owner":2871,"repository":2872,"state":2933,"title":2959,"updated_at":2960,"url":2961,"score":2962},"### Is your feature request related to a problem? Please describe.\n\nIt is recommended to support Hong Kong Holidays\n\n### Describe the solution you'd like\n\nIt is recommended to support Hong Kong Holidays\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.",[],3753,"It is recommended to support Hong Kong Holidays","2024-04-28T12:25:07Z","https://github.com/vuejs/vitepress/issues/3753",0.8059346,{"description":2964,"labels":2965,"number":2967,"owner":2871,"repository":2872,"state":2933,"title":2968,"updated_at":2969,"url":2970,"score":2971},"### Describe the bug\n\n#### I used `HTML string` content in Footer-message config, but the result of `npm run dev` was normal (the result I wanted), but after I `build` it, it was different. My HTML string was overwritten as null, and after my attempts, I found that it couldn't render the `div` tag. I want to know why this is??, Thanks\n\n### Reproduction\n\n-\n\n### Expected behavior\n\n-\n\n### System Info\n\n```Text\n-\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.",[2966],{"name":2930,"color":2931},4085,"Why 'footer' config no support 'div' tag?","2024-08-06T04:42:43Z","https://github.com/vuejs/vitepress/issues/4085",0.80875367,["Reactive",2973],{},["Set"],["ShallowReactive",2976],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f6-3hMY-ekLq9yv7V_IRwewUt9gGdxZepUVUsIt-vZro":-1},"/vuejs/vitepress/4176"]