\n\n\n```vue\n\u003Cscript setup>\nimport { FwbButton } from 'flowbite-vue'\n\u003C/script>\n\u003Ctemplate>\n \u003Cdiv>\n \u003Cfwb-button color=\"default\">Default\u003C/fwb-button>\n \u003C/div>\n\u003C/template>\n```\n\n### Reproduction\n\nhttps://github.com/jk2K/testvitepress\n\ntech stack\n1. https://flowbite-vue.com/pages/getting-started\n2. tailwindcss v4\n\n### Expected behavior\n\n\u003Cimg width=\"103\" height=\"50\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/7bffdf53-2faf-4257-87c2-4f60511b7060\" />\n\n### System Info\n\n```Text\nSystem:\n OS: macOS 15.5\n CPU: (14) arm64 Apple M4 Pro\n Memory: 218.33 MB / 48.00 GB\n Shell: 5.9 - /bin/zsh\n Binaries:\n Node: 22.16.0 - ~/.nvm/versions/node/v22.16.0/bin/node\n npm: 10.9.2 - ~/.nvm/versions/node/v22.16.0/bin/npm\n pnpm: 10.11.0 - /opt/homebrew/bin/pnpm\n Browsers:\n Chrome: 138.0.7204.159\n Safari: 18.5\n npmPackages:\n vitepress: ^1.6.3 => 1.6.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.",[3051],{"name":3020,"color":3021},4856,"vitepress not work for flowbite-vue","2025-07-25T10:13:26Z","https://github.com/vuejs/vitepress/issues/4856",0.66172135,{"description":3058,"labels":3059,"number":3063,"owner":3023,"repository":3024,"state":3025,"title":3064,"updated_at":3065,"url":3066,"score":3067},"### Describe the bug\n\n20:36:36 [vitepress] Internal server error: At least one \u003Ctemplate> or \u003Cscript> is required in a single file component.\r\n Plugin: vite:vue\r\n File: C:/Users/wingwang/Desktop/Oceanpayment-ui/node_modules/.pnpm/vitepress@1.2.2_@algolia+client-search@4.23.3_@types+node@20.14.5_async-validator@4.2.5_axios_v2np3kzxvdru2wjixovc3nnoya/node_modules/vitepress/dist/client/theme-default/components/VPTeamMembers.vue\r\n at Object.parse$2 [as parse] (C:\\Users\\wingwang\\Desktop\\Oceanpayment-ui\\node_modules\\.pnpm\\@vue+compiler-sfc@3.3.4\\node_modules\\@vue\\compiler-sfc\\dist\\compiler-sfc.cjs.js:1275:7)\r\n at createDescriptor (file:///C:/Users/wingwang/Desktop/Oceanpayment-ui/node_modules/.pnpm/@vitejs+plugin-vue@4.3.1_vite@5.2.12_@types+node@20.14.5_less@4.2.0_sass@1.77.4__vue@3.3.4/node_modules/@vitejs/plugin-vue/dist/index.mjs:70:43)\r\n at transformMain (file:///C:/Users/wingwang/Desktop/Oceanpayment-ui/node_modules/.pnpm/@vitejs+plugin-vue@4.3.1_vite@5.2.12_@types+node@20.14.5_less@4.2.0_sass@1.77.4__vue@3.3.4/node_modules/@vitejs/plugin-vue/dist/index.mjs:2261:34)\r\n at TransformContext.transform (file:///C:/Users/wingwang/Desktop/Oceanpayment-ui/node_modules/.pnpm/@vitejs+plugin-vue@4.3.1_vite@5.2.12_@types+node@20.14.5_less@4.2.0_sass@1.77.4__vue@3.3.4/node_modules/@vitejs/plugin-vue/dist/index.mjs:2782:16)\r\n at Object.transform (file:///C:/Users/wingwang/Desktop/Oceanpayment-ui/node_modules/.pnpm/vite@5.2.12_@types+node@20.14.5_less@4.2.0_sass@1.77.4/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:52312:62)\r\n at process.processTicksAndRejections (node:internal/process/task_queues:95:5)\r\n at async loadAndTransform (file:///C:/Users/wingwang/Desktop/Oceanpayment-ui/node_modules/.pnpm/vite@5.2.12_@types+node@20.14.5_less@4.2.0_sass@1.77.4/node_modules/vite/dist/node/chunks/dep-BKbDVx1T.js:55067:29)\r\n\n\n### Reproduction\n\nhttps://stackblitz.com/edit/vite-nnfopi?file=docs%2F.vitepress%2Fconfig.ts\n\n### Expected behavior\n\nnormal\n\n### System Info\n\n```Text\nSystem:\r\n OS: Linux 5.0 undefined\r\n CPU: (8) x64 Intel(R) Core(TM) i9-9880H CPU @ 2.30GHz\r\n Memory: 0 Bytes / 0 Bytes\r\n Shell: 1.0 - /bin/jsh\r\n Binaries:\r\n Node: 18.20.1 - /usr/local/bin/node\r\n Yarn: 1.22.19 - /usr/local/bin/yarn\r\n npm: 9.4.2 - /usr/local/bin/npm\r\n pnpm: 9.1.3 - /usr/local/bin/pnpm\r\n npmPackages:\r\n vitepress: 1.2.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.",[3060],{"name":3061,"color":3062},"need more info","bdbefc",3986,"[vitepress] Internal server error: At least one \u003Ctemplate> or \u003Cscript> is required in a single file component.","2024-07-03T04:41:57Z","https://github.com/vuejs/vitepress/issues/3986",0.66592556,{"description":3069,"labels":3070,"number":3072,"owner":3023,"repository":3024,"state":3025,"title":3073,"updated_at":3074,"url":3075,"score":3076},"### Describe the bug\r\n\r\nwhen I update the version to `\"vitepress\": \"^1.0.0-alpha.63\",` , and run `vitepress dev docs`, The Aside component is render nothing\r\n\r\n\r\n\r\n### Reproduction\r\n\r\nupdate the vitepress version to `\"vitepress\": \"^1.0.0-alpha.63\",`\r\n\r\nrun `vitepress dev docs`\r\n\r\n`config.js`\r\n```\r\nimport { defineConfigWithTheme } from 'vitepress';\r\nimport vueJsx from '@vitejs/plugin-vue-jsx';\r\nimport baseConfig from '@vue/theme/config';\r\nimport { demoBlockPlugin } from 'vitepress-theme-demoblock';\r\nimport path from 'path';\r\n\r\nimport { i18n, nav, sidebar } from './themeConfig/index';\r\n\r\nexport default defineConfigWithTheme({\r\n extends: baseConfig,\r\n lang: 'zh-CN',\r\n title: 'SinoGear Vue',\r\n description: '',\r\n srcDir: './src',\r\n scrollOffset: 'header',\r\n ignoreDeadLinks: true,\r\n head: [['meta', { name: 'theme-color', content: '#3c8772' }]],\r\n themeConfig: {\r\n nav,\r\n sidebar,\r\n appearance: false, // 开启 light/dark 模式\r\n // Placeholder of the i18n config for @vuejs-translations.\r\n i18n,\r\n },\r\n\r\n markdown: {\r\n config(md) {\r\n md.use(demoBlockPlugin, {\r\n cssPreprocessor: 'less',\r\n scriptImports: [\r\n \"import * as AntDesignVue from 'ant-design-vue'\",\r\n ],\r\n scriptReplaces: [\r\n {\r\n searchValue: /import ({.*}) from 'ant-design-vue'/g,\r\n replaceValue: (s, s1) => `const ${s1} = AntDesignVue`\r\n },\r\n ]\r\n });\r\n }\r\n },\r\n\r\n vite: {\r\n server: {\r\n host: true,\r\n port: 3001,\r\n fs: {\r\n // for when developing with locally linked theme\r\n allow: ['../..']\r\n }\r\n },\r\n build: {\r\n chunkSizeWarningLimit: Infinity\r\n },\r\n json: {\r\n stringify: true\r\n },\r\n ssr: {\r\n noExternal: ['@wangeditor/editor', '@wangeditor/editor-for-vue', 'ant-design-vue', '@ant-design/icons-vue', '@babel/runtime']\r\n },\r\n plugins: [vueJsx()],\r\n css: {\r\n preprocessorOptions: {\r\n less: {\r\n javascriptEnabled: true\r\n }\r\n }\r\n }\r\n },\r\n\r\n vue: {\r\n reactivityTransform: path.resolve(__dirname, 'src')\r\n }\r\n});\r\n\r\n```\r\n\r\n### Expected behavior\r\n\r\nrender aside component\r\n\r\n### System Info\r\n\r\n\r\n`packages.json`\r\n```shell\r\n\r\n\"@babel/plugin-syntax-jsx\": \"^7.18.6\",\r\n \"@vitejs/plugin-vue\": \"^4.0.0\",\r\n \"@vitejs/plugin-vue-jsx\": \"^3.0.0\",\r\n \"@vue/babel-plugin-jsx\": \"^1.1.1\",\r\n \"@vue/compiler-sfc\": \"^3.0.4\",\r\n \"conventional-changelog-cli\": \"^2.1.0\",\r\n \"cross-env\": \"^7.0.2\",\r\n \"del\": \"^6.0.0\",\r\n \"gulp\": \"^4.0.2\",\r\n \"gulp-babel\": \"^8.0.0\",\r\n \"highlight.js\": \"^10.4.1\",\r\n \"less\": \"^4.1.2\",\r\n \"lint-staged\": \"^13.0.3\",\r\n \"prettier\": \"^2.7.1\",\r\n \"rimraf\": \"^3.0.0\",\r\n \"transliteration\": \"^2.2.0\",\r\n \"vitepress\": \"^1.0.0-alpha.63\",\r\n \"vitepress-plugin-search\": \"^1.0.4-alpha.17\",\r\n \"vitepress-theme-demoblock\": \"^2.0.0\"\r\n```\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] 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.",[3071],{"name":3061,"color":3062},2157,"The Aside component is render nothing","2023-04-05T00:04:02Z","https://github.com/vuejs/vitepress/issues/2157",0.6708605,{"description":3078,"labels":3079,"number":3080,"owner":3023,"repository":3024,"state":3025,"title":3081,"updated_at":3082,"url":3083,"score":3084},"**Describe the bug/feature**\r\n\r\nIn both **Vitepress** and **Vuepress** the way in which the Markdown-it rule `htmlBlock` is implemented is highly subpar. This is particularly true because the primary use-case for both is documentation but currently adding in a VueJS component which takes advantage of slot content tends to break rather quickly. This is because -- by default web-components are considered _inline_ components by Markdown (as per the spec). When Markdown encounters inline components it treats the interior scope of the web-component as Markdown content and therefore tends to wreck havoc on slot content.\r\n\r\nLooking at the `src/node/markdown/plugins/component.ts` file you can start to see the problem when looking at the `HTML_SEQUENCES` symbol (some lines removed for brevity):\r\n\r\n```ts\r\n// An array of opening and corresponding closing sequences for html tags,\r\n// last argument defines whether it can terminate a paragraph or not\r\nconst HTML_SEQUENCES: [RegExp, RegExp, boolean][] = [\r\n // PascalCase Components\r\n [/^\u003C[A-Z]/, />/, true],\r\n // custom elements with hyphens\r\n [/^\u003C\\w+\\-/, />/, true],\r\n]\r\n```\r\n\r\nThe intent here is to mark the opening and closing of scope for a component but as you can see from the RegEx it is only looking for inline components not block components!\r\n\r\nFor example, the component `p-table` has several named slots which help it to render the way the user intends:\r\n\r\n```html\r\n\u003Cp-table>\r\n \r\n \u003Ctemplate #name=\"{ row }\">\r\n {{ row.name }}\r\n \u003C/template>\r\n\r\n \u003Ctemplate #age=\"{ row }\">\r\n {{ row.age }}\r\n \u003C/template>\r\n\r\n\u003C/p-table>\r\n```\r\n\r\nPut this into the template section of a Vue CLI app and it works just fine. Put it into Vuepress or Vitepress and watch the cloud of smoke start to rise as it fumbles around; particularly failing on the `#` symbols used as shorthand for named slots. This is particularly troublesome for a documentation site that is trying to document a set of VueJS components! There should be a way to ensure that this VueJS component's interior scope is left untouched by **Markdown-it** ... at least when that's what you want. \r\n\r\nThere is a second use-case that I would expect Vitepress to just handle and that is _kind of_ what it's doing today but in a hit and miss fashion currently. Let's say that I just have a default slot in my component and therefore I want my component to be seen by the Markdown engine as being an \"inline\" component and process the interior as markdown. Great, then the following should work:\r\n\r\n```md\r\n\u003Csuper-sexy>\r\n# some heading\r\n## some sub heading\r\n\u003C/super-sexy>\r\n```\r\n\r\nThis would just provide some HTML wrapper elements that would in this case make this very dull markdown sexy.\r\n\r\nFinally there is a third use-case that really should be considered required too ... this is the hybrid but it will allow for all sorts of simple but useful documentation components. The use-case presents as a component that exposes named slots -- and therefore is seen by Markdown as a block component -- but these named slots _are_ processed by markdown. An obvious example might be a `\u003Ctwo-columns>` component which provides a `left` and `right` slot and allows authors to more readily leverage their horizontal space.\r\n\r\nImagine the following:\r\n\r\n```html\r\n\u003Ctwo-columns>\r\n\r\n \u003Ctemplate #left>\r\n I'm a lumberjack and I'm ok\r\n \u003C/template>\r\n \u003Ctemplate #right>\r\n I sleep all night and I work all day\r\n \u003C/template>\r\n\r\n\u003C/two-columns>\r\n```\r\n \r\nThis will fail miserably today but it _could_ be grand!\r\n\r\n** Proposed Solution **\r\n\r\nRework the `src/node/markdown/plugins/components.ts` file in Vitepress (same change can be applied to Vuepress) to:\r\n\r\n- use more sophisticated RegEx patterns to actually capture BLOCK content not just inline components\r\n- support two modes of processing for BLOCK VueJS components: \r\n\r\n 1. Isolated - the interior scope is _not_ processed as markdown and all registered VueJS components can operate exactly like they would normally do\r\n 2. Parsed - the interior scope is processed as markdown; this will work well for default slots where the interior content is Markdown content\r\n\r\n- the Isolated mode should be seen as the _default_ as it is more powerful and allows components that work outside the context of Vitepress/Vuepress to just work here as well\r\n- the parsed mode may be popular for components designed strictly for Vitepress and Vuepress and it could be opted into in the HTML template like so:\r\n\r\n ```html\r\n \u003Cmy-crazy-idea parsed>There I was, _there I was_, in the Congo\u003C/my-crazy-idea>\r\n ```\r\n\r\nThis solution so far could pretty easily support the first two use cases which is a big step forward. The third use-case would certainly be nice but would need a bit more thought. I could imagine something as simple as adding the `md` prop to the parent component being used as a means to pass in the Markdownit object into the top-level component so it could chain the rendering into the various named slots:\r\n\r\n ```html\r\n \u003Cmy-crazy-idea md>\r\n \u003Ctemplate #left>\r\n There I was, _there I was_, \r\n \u003Ctemplate #right>\r\n I sleep all night and I work all day\r\n \u003C/template>\r\n \u003C/my-crazy-idea>\r\n ```\r\n\r\nIn all likelihood this last option should be done as an optional second step.\r\n",[],135,"Proper processing of Vue Component slot content","2023-01-21T14:28:50Z","https://github.com/vuejs/vitepress/issues/135",0.67133296,{"description":3086,"labels":3087,"number":3089,"owner":3023,"repository":3024,"state":3025,"title":3090,"updated_at":3091,"url":3092,"score":3093},"\u003C!--\r\nNOTE:\r\nVitePress is still WIP, and it is not compatible with VuePress.\r\nPlease do not open issue about default theme missing features or something doesn't work like VuePress.\r\n-->\r\n\r\n**Describe the bug**\r\nWhen I use the components directly in markdown file, It raised a waring with `vue.js:1099 [Vue warn]: Failed to resolve componen` as:\r\n\r\n\r\n\r\nDoes vitepress auto register components in `.vitepress/components`? or where can I put the `.vue` files and how to use them? thank you.\r\n\r\n**To Reproduce**\r\nSteps to reproduce the behavior:\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:\r\n- vite version:\r\n- Node version:\r\n- OS version:\r\n\r\n**Additional context**\r\nAdd any other context about the problem here.\r\n",[3088],{"name":3020,"color":3021},60,"Is vitepress auto register components in `.vitepress/components`?","2023-01-21T16:25:31Z","https://github.com/vuejs/vitepress/issues/60",0.67197,{"description":3095,"labels":3096,"number":3098,"owner":3023,"repository":3024,"state":3025,"title":3099,"updated_at":3100,"url":3101,"score":3102},"### Describe the bug\n\nimport `svg` with plugin vite-svg-loader\r\nit's type should be `FunctionalComponent`\r\nthis is ok in vite projects\r\nbut not work in vitepress\r\nit's type is `String`\n\n### Reproduction\n\nhttps://github.com/x-wink/wink-ui\r\nthis is my repository\r\nthrow type error in this file: `docs\\src\\examples\\button\\use5.vue`\r\nit's ok in this file: `packages\\components\\select\\tag.vue`\n\n### Expected behavior\n\njust like vite projects\n\n### System Info\n\n```Text\nSystem:\r\n OS: Windows 10 10.0.19045\r\n CPU: (24) x64 Intel(R) Xeon(R) CPU E5-2673 v3 @ 2.40GHz\r\n Memory: 19.04 GB / 31.86 GB\r\n Binaries:\r\n Node: 18.16.0 - D:\\nodejs\\node.EXE\r\n npm: 9.5.1 - D:\\nodejs\\npm.CMD\r\n pnpm: 8.7.4 - ~\\AppData\\Local\\pnpm\\pnpm.CMD\r\n Browsers:\r\n Chrome: bookmarks.html\r\ninitial_preferences\r\n Edge: Chromium (116.0.1938.81)\r\n Internet Explorer: 11.0.19041.1566\n```\n\n\n### Additional context\n\nexists follow projects in my UI libary momorepo:\r\n- docs\r\n- icons\r\n- components\r\n- wink-ui\r\n\r\n`docs` is a vitepress project, dependencie `icons` and `components`\r\n`icons` is a vite project with plugin vite-svg-loader\r\n`components` define vue components and dependencie `icons`\r\n`wink-ui` is a vite project dependencie `components`, build and emits `components`\r\n\r\nI try to upgrade vitepress to latest version,it's same result.\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.",[3097],{"name":3061,"color":3062},2968,"Type error when use svg icon with plugin vite-svg-loader","2024-01-09T00:05:11Z","https://github.com/vuejs/vitepress/issues/2968",0.6732387,{"description":3104,"labels":3105,"number":3107,"owner":3023,"repository":3024,"state":3025,"title":3108,"updated_at":3109,"url":3110,"score":3111},"### Describe the bug\n\n\r\n\r\nhttps://github.com/vuejs/vitepress/blob/9004a801305fa0c21a0064253da95fbad38148fe/src/client/app/utils.ts#L38\r\n\r\nby \r\n\r\nhttps://github.com/vuejs/vitepress/blob/89cc718649b9be547c6ec08d2dc3d10a67f2a3ac/src/client/app/utils.ts#L38-L39\r\n\r\nshould fix this.\r\n\r\n_Originally posted by @brc-dd in https://github.com/vuejs/vitepress/issues/412#issuecomment-1149704365_\r\n \r\n\r\nI still have this problem\r\n\r\nvitepress version:1.0.0-alpha.26 or npm:@brc-dd/vitepress@1.0.0-dev.50d1202\r\n\r\nI try to configure `cleanUrls: 'with-subfolders'` or `cleanUrls:' without-subfolders'` or delete the cleanUrls configuration item makes no difference or is still reporting an error\r\n\r\nI will temporarily open my [repo](https://github.com/you-hengh/myblog_vitepress) to find bugs.\n\n### Reproduction\n\npackage.json\r\n```json\r\n{\r\n \"name\": \"vitepress\",\r\n \"version\": \"1.0.0\",\r\n \"description\": \"\",\r\n \"main\": \"index.js\",\r\n \"scripts\": {\r\n \"dev\": \"vitepress dev docs\",\r\n \"build\": \"vitepress build docs\",\r\n \"serve\": \"vitepress serve docs\"\r\n },\r\n \"keywords\": [],\r\n \"author\": \"\",\r\n \"license\": \"ISC\",\r\n \"devDependencies\": {\r\n \"@algolia/client-search\": \"^4.14.2\",\r\n \"vitepress\": \"npm:@brc-dd/vitepress@1.0.0-dev.50d1202\"\r\n }\r\n}\r\n```\r\n\r\n1. pnpm build\r\n\r\n ```bash\r\n > vitepress build docs\r\n\r\n vitepress v1.0.0-dev.50d1202\r\n ✓ building client + server bundles...\r\n ⠋ rendering pages...[Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n [Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n [Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n [Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n [Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n [Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n [Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n [Vue warn]: Component \u003CAnonymous> is missing template or render function.\r\n ✓ rendering pages...\r\n build complete in 3.35s.\r\n ```\r\n\r\n2. pnpm serve\r\n\r\n ```bash\r\n > vitepress@1.0.0 serve /Users/bddxg/Documents/网站/vitepress 站点\r\n > vitepress serve docs\r\n\r\n vitepress v1.0.0-dev.50d1202\r\n Built site served at http://localhost:4173/\r\n ```\r\n\r\n\n\n### Expected behavior\n\nfix bug or tell me the solution.\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 13.0\r\n CPU: (10) arm64 Apple M1 Max\r\n Memory: 5.11 GB / 32.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 16.17.1 - ~/Library/pnpm/node\r\n npm: 8.15.0 - ~/Library/pnpm/npm\r\n Browsers:\r\n Chrome: 106.0.5249.119\r\n Safari: 16.1\r\n npmPackages:\r\n @brc-dd/vitepress: 1.0.0-dev.50d1202\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.",[3106],{"name":3020,"color":3021},1578,"vitepress serve tries to load an md.undefined.js file","2023-01-21T14:20:50Z","https://github.com/vuejs/vitepress/issues/1578",0.6734415,["Reactive",3113],{},["Set"],["ShallowReactive",3116],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fQJwjSLz5fizuB2OaEt_9Fe6ensPxcyYHAuTqIVibMvU":-1},"/vuejs/vitepress/311"]