\r\n title: Feature A\r\n details: Lorem ipsum dolor sit amet, consectetur adipiscing elit\r\n```\r\n\r\nCheck the feature icon type\r\n```ts\r\ntype FeatureIcon =\r\n | string\r\n | { src: string; alt?: string; width?: string; height: string }\r\n | {\r\n light: string\r\n dark: string\r\n alt?: string\r\n width?: string\r\n height: string\r\n }\r\n```\r\n\r\nI refer to the render logic, use `v-html` render the icon.\r\nDisplay well in `dev` environment, but shows errors in `prod` environment.\r\n\r\n| dev | build |\r\n| ----------- | ----------- |\r\n|  |  |\r\n\r\n\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/github/zyyv/vitepress-unocss-issue\r\n\r\n- Display right run `pnpm dev`\r\n- Display error run `pnpm build && pnpm preview`\r\n\r\n### Expected behavior\r\n\r\nDev and build behave the same\r\n\r\n### System Info\r\n\r\n```Text\r\nlatest\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.",[2856,2859,2862],{"name":2857,"color":2858},"build","377ba8",{"name":2860,"color":2861},"has-workaround","1B4515",{"name":2863,"color":2864},"stale","ededed",4045,"vuejs","vitepress","open","SSR in dev for more consistent output in dev and prod","2025-03-02T18:08:58Z","https://github.com/vuejs/vitepress/issues/4045",0.71274894,{"description":2874,"labels":2875,"number":2884,"owner":2866,"repository":2867,"state":2885,"title":2886,"updated_at":2887,"url":2888,"score":2889},"### Describe the bug\n\nJust like the Vite docs, I use custom styles in the `index.md` file using `\u003Cstyle module>`. I also use custom components in which I use `\u003Cstyle scoped>`.\r\n\r\nSince I updated from version `1.0.0` to the latest one (the one in the StackBlitz), the built page's styles are broken. In the dev preview everything looks like expected.\n\n### Reproduction\n\nOpen the StackBlitz Demo with this [link](https://stackblitz.com/edit/vite-1qtmk8?file=docs%2Findex.md).\r\n\r\nIf it does not run automatically, run `npm install && npm run dev`. It should look something like this:\r\n\r\n\r\n\r\nThen run `npm run docs:build && npm run docs:preview` and it will look like this:\r\n\r\n\r\n\r\nAs you can see, the hero image and its background are different and the cards are different as well.\n\n### Expected behavior\n\nI expected the built version to look just like the dev preview (or at least very close).\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (12) x64 AMD Ryzen 5 5500U with Radeon Graphics\r\n Memory: 6.45 GB / 15.35 GB\r\n Binaries:\r\n Node: 21.2.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 10.5.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n pnpm: 9.1.2 - ~\\AppData\\Roaming\\npm\\pnpm.CMD\r\n Browsers:\r\n Edge: Chromium (127.0.2651.74)\r\n Internet Explorer: 11.0.19041.4355\r\n npmPackages:\r\n vitepress: ^1.3.1 => 1.3.1\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.",[2876,2879,2880,2883],{"name":2877,"color":2878},"help wanted","008672",{"name":2857,"color":2858},{"name":2881,"color":2882},"upstream","BF29ED",{"name":2863,"color":2864},4098,"closed","Styling discrepancies between dev and build","2025-01-05T04:42:47Z","https://github.com/vuejs/vitepress/issues/4098",0.6598263,{"description":2891,"labels":2892,"number":2894,"owner":2866,"repository":2867,"state":2885,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### Describe the bug\n\nwhen I bump vitepress to `1.0.0-rc.26`, I found the styles in `\u003Cstyle>` were not included in the packaged product.\r\n\r\n The style here is normal in the development environment, but it doesn't work after packing.\r\n\r\n``` vue\r\n\u003Ctemplate>\r\n \u003Cdiv class=\"box\">Preview after packing, The text color is expected to be red\u003C/div>\r\n\u003C/template>\r\n\r\n\u003Cstyle>\r\n.box {\r\n color: red;\r\n}\r\n\u003C/style>\r\n``` \r\n\r\nI try downgraded to `1.0.0-rc.25`, it was normal.\n\n### Reproduction\n\nreproduction link:\r\n[https://stackblitz.com/edit/vite-xmetfv?file=docs%2FDemo.vue](https://stackblitz.com/edit/vite-xmetfv?file=docs%2FDemo.vue)\r\n\n\n### Expected behavior\n\nPackaged for preview and styles can also take effect\r\n\r\nrelated documents:\r\n[https://vitepress.dev/guide/using-vue#script-and-style](https://vitepress.dev/guide/using-vue#script-and-style)\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 5.15 Ubuntu 22.04.2 LTS 22.04.2 LTS (Jammy Jellyfish)\r\n CPU: (16) x64 AMD Ryzen 7 4800H with Radeon Graphics\r\n Memory: 6.16 GB / 7.44 GB\r\n Container: Yes\r\n Shell: 5.1.16 - /bin/bash\r\n Binaries:\r\n Node: 18.18.2 - ~/.nvm/versions/node/v18.18.2/bin/node\r\n Yarn: 1.22.19 - /mnt/c/Program Files/nodejs/yarn\r\n npm: 9.8.1 - ~/.nvm/versions/node/v18.18.2/bin/npm\r\n pnpm: 8.10.5 - ~/.nvm/versions/node/v18.18.2/bin/pnpm\r\n bun: 1.0.12 - ~/.nvm/versions/node/v18.18.2/bin/bun\r\n npmPackages:\r\n vitepress: 1.0.0-rc.26 => 1.0.0-rc.26\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.",[2893],{"name":2857,"color":2858},3216,"Using SFC in markdown, styles in the `\u003Cstyle>` tag is not effect.","2023-11-25T00:04:34Z","https://github.com/vuejs/vitepress/issues/3216",0.68378997,{"description":2900,"labels":2901,"number":2906,"owner":2866,"repository":2867,"state":2885,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### Describe the bug\r\n\r\nIt's unclear to me how these two differ, my understanding was that vitepress also calls vite build under the hood.\r\n\r\nHowever, I have a scenario where running `npm run docs:build` (`\"docs:build\": \"vitepress build`) results in\r\n\r\n```\r\n✓ building client + server bundles...\r\nbuild error:\r\nfile:///D:/git/some/path/docs/.vitepress/.temp/app.js:10\r\nimport { v5 } from \"uuid\";\r\n ^^\r\nSyntaxError: Named export 'v5' not found. The requested module 'uuid' is a CommonJS module, which may not support all module.exports as named exports.\r\nCommonJS modules can always be imported via the default export, for example using:\r\n\r\nimport pkg from 'uuid';\r\nconst { v5 } = pkg;\r\n\r\n at ModuleJob._instantiate (node:internal/modules/esm/module_job:124:21)\r\n at async ModuleJob.run (node:internal/modules/esm/module_job:190:5)\r\n```\r\n\r\nwhile running `npm run build` (`\"build\": \"vite build\"`) works perfectly fine.\r\n\r\nThese both use the same vite config (once in `vite.config.js` and once in the `vite:` property in vitepress' `config.js`, the latter with the `vite.config.js` deleted).\r\n\r\nThe module uuid (9.0.0) is not a CommonJS module, and building without vitepress works fine, so it looks like however `vitepress build` starts the build detects that incorrectly?\r\npackage.json of the uuid package: https://github.com/uuidjs/uuid/blob/4de23a6030e65ac72b3b015680f08e7e292681ed/package.json#L25\r\n\r\nTo be honest I'm not sure if this is a vitepress bug or even lower-level, at this point I'm mostly looking for guidance as to what vitepress build does different to vite build that could result in such differences.\r\n\r\nThanks!\r\n\r\n### Reproduction\r\n\r\nhttps://stackblitz.com/edit/vite-qpoze8?file=package.json\r\n\r\nRun `npm run docs:build` if it doesn't run automatically.\r\n\r\npackage.json of the `postprocessing` package used for repro purposes here:\r\nhttps://github.com/pmndrs/postprocessing/blob/3e6ea9d8fddd2ca2d269e2182752f8199b8248af/package.json#L11\r\n\r\n### Expected behavior\r\n\r\nEither\r\n- Builds both work\r\nor\r\n- can understand the difference between the two better from the docs so I can resolve the issue myself\r\n\r\n### System Info\r\n\r\n```sh\r\nSystem:\r\n OS: Windows 10 10.0.22621\r\n CPU: (12) x64 Intel(R) Core(TM) i7-9750H CPU @ 2.60GHz\r\n Memory: 31.89 GB / 63.85 GB\r\n Binaries:\r\n Node: 18.13.0 - D:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.13.2 - D:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Chrome: 113.0.5672.127\r\n Edge: Spartan (44.22621.1702.0), Chromium (113.0.1774.35)\r\n Internet Explorer: 11.0.22621.1\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\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.",[2902,2905],{"name":2903,"color":2904},"bug: pending triage","e99695",{"name":2863,"color":2864},2421,"Different behaviour between `vite build` and `vitepress build` in same project","2023-09-02T00:04:09Z","https://github.com/vuejs/vitepress/issues/2421",0.68655324,{"description":2912,"labels":2913,"number":2916,"owner":2866,"repository":2867,"state":2885,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### Describe the bug\n\n### dependencies\r\n\r\n`pnpm add @chenwei02/qy-element`\r\n> `@chenwei02/qy-element` has svg-icon component. svg files builded by vite-plugin-svg-icons.\r\n\r\n### docs\r\n`vitepress dev docs` is ok\r\n`vitepress build docs` then deploy to gh-pages, *.svg icon was blank.\r\n\r\n### Problem\r\nvitepress build docs . something is wrong.\r\n\r\n### Help\r\nI need help\n\n### Reproduction\n\npnpm add @chenwei02/qy-element\r\n\r\n*.md\r\n\u003Cqy-icon name=\"close\">\r\n\r\nvitepress build docs.\n\n### Expected behavior\n\nevery thing is ok.\n\n### System Info\n\n```sh\nvitepress : 1.0.0-alpha.64\r\n@chenwei02/qy-element: 1.0.2-p1\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.",[2914,2915],{"name":2903,"color":2904},{"name":2863,"color":2864},2385,"Vitepress build Problem","2023-08-18T00:04:08Z","https://github.com/vuejs/vitepress/issues/2385",0.68877876,{"description":2922,"labels":2923,"number":2925,"owner":2866,"repository":2867,"state":2885,"title":2926,"updated_at":2927,"url":2928,"score":2929},"### Describe the bug\n\nWhen building my VitePress site, sometimes will got this error:\r\n\r\n```log\r\n✓ building client + server bundles...\r\n✖ rendering pages...\r\nbuild error:\r\nCannot read properties of undefined (reading 'some')\r\nTypeError: Cannot read properties of undefined (reading 'some')\r\n at isChildActive (file:///mnt/disk/MAIN/read/.vitepress/.temp/app.js:2935:28)\r\n at file:///mnt/disk/MAIN/read/.vitepress/.temp/app.js:2937:43\r\n at ReactiveEffect.fn (/mnt/disk/MAIN/read/node_modules/@vue/reactivity/dist/reactivity.cjs.prod.js:928:13)\r\n at ReactiveEffect.run (/mnt/disk/MAIN/read/node_modules/@vue/reactivity/dist/reactivity.cjs.prod.js:162:19)\r\n at get value [as value] (/mnt/disk/MAIN/read/node_modules/@vue/reactivity/dist/reactivity.cjs.prod.js:940:109)\r\n at file:///mnt/disk/MAIN/read/.vitepress/.temp/app.js:2942:127\r\n at renderComponentSubTree (/mnt/disk/MAIN/read/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:442:9)\r\n at renderComponentVNode (/mnt/disk/MAIN/read/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:386:12)\r\n at ssrRenderComponent (/mnt/disk/MAIN/read/node_modules/@vue/server-renderer/dist/server-renderer.cjs.prod.js:84:10)\r\n at file:///mnt/disk/MAIN/read/.vitepress/.temp/app.js:2974:19\r\nerror: script \"build\" exited with code 1\r\n```\r\n\r\nDidnot know how to figure it out.\n\n### Reproduction\n\nhttps://github.com/tianheg/read/tree/0a2c670076d0bec5db10500807eb4c31bb5c80da\n\n### Expected behavior\n\nbuild succeed every time\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 6.10 Arch Linux\r\n CPU: (8) x64 Intel(R) Core(TM) i5-8250U CPU @ 1.60GHz\r\n Memory: 13.31 GB / 23.36 GB\r\n Container: Yes\r\n Shell: 5.9 - /usr/bin/zsh\r\nBinaries:\r\n Node: 20.16.0 - ~/.nvm/versions/node/v20.16.0/bin/node\r\n npm: 10.8.1 - ~/.nvm/versions/node/v20.16.0/bin/npm\r\n bun: 1.1.22 - /usr/bin/bun\r\nnpmPackages:\r\n vitepress: ^1.3.2 => 1.3.2\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.",[2924],{"name":2903,"color":2904},4130,"bug: Repeated builds doesn't always succeed every time","2024-09-04T04:43:02Z","https://github.com/vuejs/vitepress/issues/4130",0.6964792,{"description":2931,"labels":2932,"number":2934,"owner":2866,"repository":2867,"state":2885,"title":2935,"updated_at":2936,"url":2937,"score":2938},"### Describe the bug\n\nI use the global variable window in component, It will cause the content below it to be rendered repeatedly.\r\n**Also, it only happens after the build.**\n\n### Reproduction\n\n```\r\n// Component.vue\r\n\r\n\u003Cscript setup>\r\n const url = `${window.location.protocol}//www.xxx.com`;\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003Ch1>{{ url }}\u003C/h1>\r\n\u003C/template>\r\n```\r\n\r\n\r\n```\r\n// index.md\r\n\r\n\u003CComponent />\r\n\r\n// Here! `- test content ...` repeat render! it shows two.\r\n- test content ...\r\n```\n\n### Expected behavior\n\nSuccessfully rendered only once.\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 12.5\r\n CPU: (8) x64 Apple M1\r\n Memory: 43.79 MB / 8.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 14.19.3 - ~/.nvm/versions/node/v14.19.3/bin/node\r\n Yarn: 1.22.19 - /opt/homebrew/bin/yarn\r\n npm: 6.14.17 - ~/.nvm/versions/node/v14.19.3/bin/npm\r\n Browsers:\r\n Chrome: 104.0.5112.101\r\n Safari: 15.6\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.13 => 1.0.0-alpha.13\n```\n\n\n### Additional context\n\n\u003Cimg width=\"1109\" alt=\"image\" src=\"https://user-images.githubusercontent.com/50652358/187465157-4ea24772-f3ef-4ec3-8717-298579837525.png\">\r\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] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[2933],{"name":2903,"color":2904},1261,"Unexpected render after the build.","2023-01-21T14:26:49Z","https://github.com/vuejs/vitepress/issues/1261",0.69756466,{"description":2940,"labels":2941,"number":2943,"owner":2866,"repository":2867,"state":2885,"title":2944,"updated_at":2945,"url":2946,"score":2947},"### Describe the bug\n\nI only configured the theme color configuration of normal mode as follows, but when I switched to dark mode, the theme color was still overwritten by the custom color. \r\n\r\n\r\n\n\n### Reproduction\n\nsee Describe the bug\n\n### Expected behavior\n\nIsn't the color of dark mode undefined and shouldn't be used by default with vitepress\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 14.2\r\n CPU: (8) arm64 Apple M1\r\n Memory: 89.67 MB / 8.00 GB\r\n Shell: 5.9 - /bin/zsh\r\n Binaries:\r\n Node: 20.10.0 - ~/.nvm/versions/node/v20.10.0/bin/node\r\n Yarn: 1.22.19 - ~/.yarn/bin/yarn\r\n npm: 10.2.3 - ~/.nvm/versions/node/v20.10.0/bin/npm\r\n pnpm: 8.6.0 - ~/Library/pnpm/pnpm\r\n bun: 1.0.0 - ~/.bun/bin/bun\r\n Browsers:\r\n Chrome: 120.0.6099.109\r\n Edge: 119.0.2151.46\r\n Safari: 17.2\r\n npmPackages:\r\n vitepress: 1.0.0-rc.31 => 1.0.0-rc.31\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.",[2942],{"name":2903,"color":2904},3341,"Dark mode display issue after setting the accent color","2023-12-23T00:04:24Z","https://github.com/vuejs/vitepress/issues/3341",0.7008135,{"description":2949,"labels":2950,"number":2952,"owner":2866,"repository":2867,"state":2885,"title":2953,"updated_at":2954,"url":2955,"score":2956},"### Describe the bug\n\nI have a custom Layout.vue to customize the hero page, I want my video tag load different mp4 file based on current theme:\r\n\r\n```vue\r\n\u003Cscript setup>\r\nimport DefaultTheme from \"vitepress/theme\";\r\nimport { withBase, useData } from 'vitepress'\r\nconst { isDark } = useData();\r\nconsole.log(`isDark ${isDark.value}`);\r\n\u003C/script>\r\n\r\n\u003Ctemplate>\r\n \u003CDefaultTheme.Layout>\r\n \u003Ctemplate #home-hero-image>\r\n \u003Cvideo autoplay loop muted :src=\"withBase(`/video/${isDark ? 'dark' : 'light'}/x.mp4`)\" class=\"video\" />\r\n \u003C/template>\r\n \u003C/DefaultTheme.Layout>\r\n\u003C/template>\r\n```\r\n\r\nthis works perfect during development, but once I build vitepress and serve, my video is always in light mode, even though isDark is true.\r\n\r\nI found out that during `npm run build`, my Layout template is pre-compiled, so at this point, isDark is always false\r\n\r\nHow can I fix this?\n\n### Reproduction\n\nas above\n\n### Expected behavior\n\nconsist behavior\n\n### System Info\n\n```Text\nSystem:\r\n OS: macOS 13.5.2\r\n CPU: (8) x64 Intel(R) Core(TM) i7-7920HQ CPU @ 3.10GHz\r\n Memory: 191.28 MB / 16.00 GB\r\n Shell: 3.2.57 - /bin/bash\r\n Binaries:\r\n Node: 21.2.0 - /usr/local/bin/node\r\n Yarn: 1.22.10 - /usr/local/bin/yarn\r\n npm: 10.2.3 - /usr/local/bin/npm\r\n Browsers:\r\n Chrome: 119.0.6045.159\r\n Edge: 119.0.2151.72\r\n Safari: 16.6\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.31 => 1.0.0-rc.31\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.",[2951],{"name":2903,"color":2904},3267,"Inconsist behavior between development & production","2023-12-22T00:04:33Z","https://github.com/vuejs/vitepress/issues/3267",0.70203704,{"description":2958,"labels":2959,"number":2961,"owner":2866,"repository":2867,"state":2885,"title":2962,"updated_at":2963,"url":2964,"score":2965},"**Describe the bug**\r\nI execute the build and it break ...\r\n\r\n\r\n\r\n**To Reproduce**\r\nFollow https://vitepress.vuejs.org/guide/getting-started.html\r\n\r\n**Expected behavior**\r\nA clear and concise description of what you expected to happen.\r\n\r\n**System Info**\r\n- vitepress version: 0.15\r\n- vite version: ?\r\n- Node version: 16\r\n- OS version: Windows 10\r\n\r\n**Additional context**\r\nIt works on my native maschine. But not in the virtual developer VM.\r\n",[2960],{"name":2903,"color":2904},323,"Could not build on different systems","2023-01-21T16:22:19Z","https://github.com/vuejs/vitepress/issues/323",0.70210946,["Reactive",2967],{},["Set"],["ShallowReactive",2970],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fe5hpDrwwIb1vX_6vBVGXGffH-6-nhr5IML_ATiYmbGY":-1},"/vuejs/vitepress/4222"]