\r\n```\r\n\r\n```\r\n// test-2.md\r\n---\r\ntitle: ❌\r\n---\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nimport { ref } from \"vue\";\r\nimport yaml from \"yaml\";\r\nimport \"uno.css\";\r\n\u003C/script>\r\n\r\n\u003CTestInfo />\r\n```\r\n\r\n```\r\n// test-3.md\r\n---\r\ntitle: ❌\r\n---\r\n\r\n\u003Cscript setup lang=\"ts\">\r\nconst data = 123;\r\n\u003C/script>\r\n\r\n\u003CTestInfo />\r\n\r\n```\r\n\r\nWhen I execute `pnpm dev`(`vitepress dev website`), accessing `/test-1`, `/test-2`, `/test-3` works fine.\r\n\r\nWhen I execute `pnpm build && pnpm preview`(`vue-tsc && vitepress build website && vitepress preview website`), visit `/test-1`, `/test-2`, `/test-3`, my custom component does not work properly and the F12 console reports `Hydration completed but contains mismatches.`.\r\n\r\n\r\n\r\n### Expected behavior\r\n\r\nWhen I add the valid `\u003Cscript>` and execute `vue-tsc && vitepress build website && vitepress preview website`, the custom components will display normally and the console will not report an error.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Windows 10 10.0.22000\r\n CPU: (16) x64 12th Gen Intel(R) Core(TM) i5-12500H\r\n Memory: 1.13 GB / 15.73 GB\r\n Binaries:\r\n Node: 16.17.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - ~\\AppData\\Roaming\\npm\\yarn.CMD\r\n npm: 8.15.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22000.120.0), Chromium (109.0.1518.78)\r\n Internet Explorer: 11.0.22000.120\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.32 => 1.0.0-alpha.32\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.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3048,3051],{"name":3049,"color":3050},"bug: pending triage","e99695",{"name":3020,"color":3021},1918,"closed","Warn `Hydration completed but contains mismatches.` and Custom components are not rendered","2023-08-11T00:04:12Z","https://github.com/vuejs/vitepress/issues/1918",0.75100857,{"description":3059,"labels":3060,"number":3062,"owner":3023,"repository":3024,"state":3053,"title":3063,"updated_at":3064,"url":3065,"score":3066},"### Describe the bug\r\n\r\nThe dev mode doesn't work/serve a working website.\r\n\r\nFirefox v105:\r\n\r\n````txt\r\nUncaught TypeError: import_meta.hot is undefined\r\n \u003Canonymous> http://localhost:5173/@fs/~/faker/node_modules/.pnpm/vitepress@1.0.0-alpha.17_w6dk4dwpgdxdglls4cxrxtpqg4/node_modules/vitepress/dist/client/theme-default/components/VPSkipLink.vue?v=341ae09c:51\r\n````\r\n\r\nChrome v105:\r\n\r\n```txt\r\nUncaught TypeError: Cannot read properties of undefined (reading 'accept')\r\n at VPSkipLink.vue:37:3\r\n```\r\n\r\nBuilding and serving (prod) works fine.\r\n\r\n### Reproduction\r\n\r\n````sh\r\ngit clone git@github.com:faker-js/faker.git\r\npnpm install\r\npnpm run build\r\npnpm run docs:dev\r\n# Open Browser\r\n````\r\n\r\n### Expected behavior\r\n\r\nA working website is shown.\r\n\r\n### System Info\r\n\r\n```shell\r\n System:\r\n OS: Windows 10 10.0.22621\r\n CPU: (16) x64 Intel(R) Core(TM) i7-7820X CPU @ 3.60GHz\r\n Memory: 53.71 GB / 63.69 GB\r\n Binaries:\r\n Node: 16.17.1 - C:\\Program Files\\nodejs\\node.EXE\r\n Yarn: 1.22.19 - C:\\Program Files (x86)\\Yarn\\bin\\yarn.CMD\r\n npm: 8.16.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22621.521.0), Chromium (105.0.1343.53)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: 1.0.0-alpha.17 => 1.0.0-alpha.17 \r\n```\r\n\r\n\r\n### Additional context\r\n\r\nFails with:\r\n- 1.0.0-alpha.17\r\n- 1.0.0-alpha.16\r\n- 1.0.0-alpha.15\r\n- 1.0.0-alpha.10\r\n- No more versions tested\r\n\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.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3061],{"name":3049,"color":3050},1422,"Dev mode not working","2023-01-21T14:25:17Z","https://github.com/vuejs/vitepress/issues/1422",0.7512222,{"description":3068,"labels":3069,"number":3071,"owner":3023,"repository":3024,"state":3053,"title":3072,"updated_at":3073,"url":3074,"score":3075},"### 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.",[3070],{"name":3049,"color":3050},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.7719594,{"description":3077,"labels":3078,"number":3079,"owner":3023,"repository":3024,"state":3053,"title":3080,"updated_at":3081,"url":3082,"score":3083},"### Is your feature request related to a problem? Please describe.\n\nI would like to show level 2 and 3 titles in the aside. Currently, it only supports showing level 2.\n\n### Describe the solution you'd like\n\nExtend the config for aside to accept e.g. `{ depth: 2 }`.\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.",[],4143,"Allow aside depth customization","2024-08-25T04:42:02Z","https://github.com/vuejs/vitepress/issues/4143",0.7757726,{"description":3085,"labels":3086,"number":3090,"owner":3023,"repository":3024,"state":3053,"title":3091,"updated_at":3092,"url":3093,"score":3094},"### Describe the bug\n\nStatic resource build is not packaged\r\n\r\n\r\n\r\nWhen I use it, I use the relative path `./modules/` , which works fine at runtime, but when packaged it prompts 404\r\n\r\n\n\n### Reproduction\n\n*\n\n### Expected behavior\n\nHow do you ensure that your development and production environments are consistent\r\n\n\n### System Info\n\n```shell\nwindows\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.",[3087],{"name":3088,"color":3089},"need more info","bdbefc",1626,"Static resource build is not packaged","2023-01-21T14:16:45Z","https://github.com/vuejs/vitepress/issues/1626",0.7828317,{"description":3096,"labels":3097,"number":3101,"owner":3023,"repository":3024,"state":3053,"title":3102,"updated_at":3103,"url":3104,"score":3105},"### Is your feature request related to a problem? Please describe.\n\nI want user `h1` as my article outline, i can't use theme config to custom my outline\n\n### Describe the solution you'd like\n\nif i have config in my config.js\r\n```js\r\n themeConfig: {\r\n outline: [1,6] || 'all'\r\n}\r\n```\r\nthe title selector should like this\r\n```js\r\ndocument\r\n .querySelectorAll\u003CHTMLHeadingElement>('h1,h2, h3, h4, h5, h6') // include h1 title\r\n .forEach((el) => {\r\n if (el.textContent && el.id) {\r\n updatedHeaders.push({\r\n level: Number(el.tagName[1]),\r\n title: el.innerText.replace(/\\s+#\\s*$/, ''),\r\n link: `#${el.id}`\r\n })\r\n }\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.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.",[3098],{"name":3099,"color":3100},"theme","0754FB",1529,"The levels of header to display in the outline can't support h1 title","2023-08-12T00:04:14Z","https://github.com/vuejs/vitepress/issues/1529",0.79034287,{"description":3107,"labels":3108,"number":3109,"owner":3023,"repository":3024,"state":3053,"title":3110,"updated_at":3111,"url":3112,"score":3113},"### Describe the bug\n\nWhen using custom children in the `\u003Cbadge>` component, it breaks the `outlineBadges: false` option and will display the badge's text in the sidebar outline.\n\n### Reproduction\n\n1. Add a badge to an H2 title (##)\r\n2. Add custom children in the badge slot\r\n3. Set `outlineBadges` option to `false`\r\n\r\nhttps://stackblitz.com/edit/vite-smtupz?file=docs/example.md\n\n### Expected behavior\n\n`outlineBadges` honors badges with custom children/elements when set to false.\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.22621\r\n CPU: (32) x64 AMD Ryzen 9 5950X 16-Core Processor\r\n Memory: 18.43 GB / 31.93 GB\r\n Binaries:\r\n Node: 18.12.0 - C:\\Program Files\\nodejs\\node.EXE\r\n npm: 9.2.0 - C:\\Program Files\\nodejs\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.22621.1344.0), Chromium (110.0.1587.63)\r\n Internet Explorer: 11.0.22621.1\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.50 => 1.0.0-alpha.50\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.dev).\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[],2060,"Badge slot breaks `outlineBadges`","2023-03-19T00:04:50Z","https://github.com/vuejs/vitepress/issues/2060",0.79892087,{"description":3115,"labels":3116,"number":3120,"owner":3023,"repository":3024,"state":3053,"title":3121,"updated_at":3122,"url":3123,"score":3124},"### Describe the bug\r\n\r\nAttempting to run `vitepress build docs` when there exists a file `docs/**/arguments.md` results in a crash.\r\n```shell\r\n$ yarn vitepress build docs\r\nyarn run v1.22.19\r\n$ /home/.../website/node_modules/.bin/vitepress build docs\r\nvitepress v1.0.0-alpha.4\r\n⠇ building client + server bundles...[vite:esbuild-transpile] Transform failed with 1 error:\r\narguments.md.js:21:4: ERROR: Declarations with the name \"arguments\" cannot be used in strict mode\r\n\r\nDeclarations with the name \"arguments\" cannot be used in strict mode\r\n19 | return _sfc_setup ? _sfc_setup(props, ctx) : undefined\r\n20 | };\r\n21 | var arguments = /*#__PURE__*/pluginVue_exportHelper._export_sfc(_sfc_main, [['ssrRender',_sfc_ssrRender]]);\r\n | ^\r\n22 | \r\n23 | exports.__pageData = __pageData;\r\n\r\n✖ building client + server bundles...\r\n[vite:esbuild-transpile] Transform failed with 1 error:\r\nassets/arguments.md.88297d47.js:14:4: ERROR: Declarations with the name \"arguments\" cannot be used in an ECMAScript module\r\n\r\nDeclarations with the name \"arguments\" cannot be used in an ECMAScript module\r\n12 | return (openBlock(), createElementBlock(\"div\", null, _hoisted_2))\r\n13 | }\r\n14 | var arguments = /*#__PURE__*/_export_sfc(_sfc_main, [['render',_sfc_render]]);\r\n | ^\r\n15 | \r\n16 | export { __pageData, arguments as default };\r\n\r\nbuild error:\r\n Error: Transform failed with 1 error:\r\narguments.md.js:21:4: ERROR: Declarations with the name \"arguments\" cannot be used in strict mode\r\n at failureErrorWithLog (/home/.../website/node_modules/esbuild/lib/main.js:1615:15)\r\n at /home/.../website/node_modules/esbuild/lib/main.js:1404:29\r\n at /home/.../website/node_modules/esbuild/lib/main.js:669:9\r\n at handleIncomingPacket (/home/.../website/node_modules/esbuild/lib/main.js:766:9)\r\n at Socket.readFromStdout (/home/.../website/node_modules/esbuild/lib/main.js:635:7)\r\n at Socket.emit (node:events:527:28)\r\n at addChunk (node:internal/streams/readable:315:12)\r\n at readableAddChunk (node:internal/streams/readable:289:9)\r\n at Socket.Readable.push (node:internal/streams/readable:228:10)\r\n at Pipe.onStreamRead (node:internal/stream_base_commons:190:23) {\r\n errors: [\r\n {\r\n detail: undefined,\r\n id: '',\r\n location: [Object],\r\n notes: [Array],\r\n pluginName: '',\r\n text: 'Declarations with the name \"arguments\" cannot be used in strict mode'\r\n }\r\n ],\r\n warnings: [],\r\n frame: '\\n' +\r\n '\\x1B[33mDeclarations with the name \"arguments\" cannot be used in strict mode\\x1B[39m\\n' +\r\n '19 | return _sfc_setup ? _sfc_setup(props, ctx) : undefined\\n' +\r\n '20 | };\\n' +\r\n \"21 | var arguments = /*#__PURE__*/pluginVue_exportHelper._export_sfc(_sfc_main, [['ssrRender',_sfc_ssrRender]]);\\n\" +\r\n ' | ^\\n' +\r\n '22 | \\n' +\r\n '23 | exports.__pageData = __pageData;\\n',\r\n loc: {\r\n column: 4,\r\n file: 'arguments.md.js',\r\n length: 9,\r\n line: 21,\r\n lineText: \"var arguments = /*#__PURE__*/pluginVue_exportHelper._export_sfc(_sfc_main, [['ssrRender',_sfc_ssrRender]]);\",\r\n namespace: '',\r\n suggestion: ''\r\n },\r\n code: 'PLUGIN_ERROR',\r\n plugin: 'vite:esbuild-transpile',\r\n hook: 'renderChunk'\r\n}\r\n```\r\n\r\n### Reproduction\r\n\r\nTo reproduce, create a file called `arguments.md` with any content inside the vitepress `docs` folder (or other target).\r\nThen, run `vitepress build \u003Cfolder>`, and the error will occur.\r\n\r\n### Expected behavior\r\n\r\nThe expected behaviour is to generate an `arguments.html` file.\r\n\r\n### System Info\r\n\r\n```shell\r\nSystem:\r\n OS: Linux 5.18 Arch Linux\r\n CPU: (12) x64 AMD Ryzen 5 2600X Six-Core Processor\r\n Memory: 18.11 GB / 31.28 GB\r\n Container: Yes\r\n Shell: 5.9 - /usr/bin/zsh\r\n Binaries:\r\n Node: 16.16.0 - /usr/bin/node\r\n Yarn: 1.22.19 - /usr/bin/yarn\r\n npm: 8.14.0 - /usr/bin/npm\r\n Browsers:\r\n Chromium: 103.0.5060.134\r\n npmPackages:\r\n vitepress: ^1.0.0-alpha.4 => 1.0.0-alpha.4 \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.vuejs.org).\r\n- [X] Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.",[3117],{"name":3118,"color":3119},"build","377ba8",1068,"Documents named `arguments.md` cannot be built.","2023-01-21T14:27:03Z","https://github.com/vuejs/vitepress/issues/1068",0.79894245,["Reactive",3126],{},["Set"],["ShallowReactive",3129],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f2U0X9lpRJ3Qv_1id29ZudptyGX5adJl7NkgPnaQfUQo":-1},"/vuejs/vitepress/2735"]