` , no errors.\n\n### Expected behavior\n\nno errors, compile success\n\n### System Info\n\n```shell\nSystem:\r\n OS: Windows 10 10.0.19044\r\n CPU: (8) x64 Intel(R) Core(TM) i7-6700HQ CPU @ 2.60GHz\r\n Memory: 16.46 GB / 31.85 GB\r\n Binaries:\r\n Node: 14.18.2 - E:\\apps\\node-v14\\node.EXE\r\n Yarn: 1.22.10 - E:\\apps\\node-v14\\node_global\\yarn.CMD\r\n npm: 7.20.0 - E:\\apps\\node-v14\\npm.CMD\r\n Browsers:\r\n Edge: Spartan (44.19041.1266.0), Chromium (98.0.1108.50)\r\n Internet Explorer: 11.0.19041.1202\r\n npmPackages:\r\n vitepress: ^0.22.2 => 0.22.2\n```\n\n\n### Additional context\n\n_No response_\n\n### Validations\n\n- [X] Follow our [Code of Conduct](https://vuejs.org/coc)\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.",[2891],{"name":2892,"color":2893},"need more info","bdbefc",534,"closed","in markdown file, use image file, image file exists and path correct, but image load failed","2023-01-21T14:34:14Z","https://github.com/vuejs/vitepress/issues/534",0.72022194,{"description":2901,"labels":2902,"number":2906,"owner":2872,"repository":2873,"state":2895,"title":2907,"updated_at":2908,"url":2909,"score":2910},"### Describe the bug\n\nRunning `npm run docs:build` results in an error when using latest (`-rc.2`) packaged version:\r\n\r\n```\r\n$ npm run docs:build\r\n\r\n> docs:build\r\n> vitepress build docs\r\n\r\n\r\n vitepress v1.0.0-rc.3\r\n\r\n✘ [ERROR] \"vitepress\" resolved to an ESM file. ESM file cannot be loaded by `require`. See http://vitejs.dev/guide/troubleshooting.html#this-package-is-esm-only for more details. [plugin externalize-deps]\r\n\r\n node_modules/esbuild/lib/main.js:1373:27:\r\n 1373 │ let result = await callback({\r\n ╵ ^\r\n\r\n at file:///tmp/vpress/node_modules/vite/dist/node/chunks/dep-df561101.js:66190:35\r\n at requestCallbacks.on-resolve (/tmp/vpress/node_modules/esbuild/lib/main.js:1373:28)\r\n at handleRequest (/tmp/vpress/node_modules/esbuild/lib/main.js:729:19)\r\n at handleIncomingPacket (/tmp/vpress/node_modules/esbuild/lib/main.js:755:7)\r\n at Socket.readFromStdout (/tmp/vpress/node_modules/esbuild/lib/main.js:679:7)\r\n at Socket.emit (node:events:513: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\r\n This error came from the \"onResolve\" callback registered here:\r\n\r\n node_modules/esbuild/lib/main.js:1292:20:\r\n 1292 │ let promise = setup({\r\n ╵ ^\r\n\r\n at setup (file:///tmp/vpress/node_modules/vite/dist/node/chunks/dep-df561101.js:66158:27)\r\n at handlePlugins (/tmp/vpress/node_modules/esbuild/lib/main.js:1292:21)\r\n at buildOrContextImpl (/tmp/vpress/node_modules/esbuild/lib/main.js:978:5)\r\n at Object.buildOrContext (/tmp/vpress/node_modules/esbuild/lib/main.js:786:5)\r\n at /tmp/vpress/node_modules/esbuild/lib/main.js:2177:15\r\n at new Promise (\u003Canonymous>)\r\n at Object.build (/tmp/vpress/node_modules/esbuild/lib/main.js:2176:25)\r\n at build (/tmp/vpress/node_modules/esbuild/lib/main.js:2025:51)\r\n at bundleConfigFile (file:///tmp/vpress/node_modules/vite/dist/node/chunks/dep-df561101.js:66109:26)\r\n\r\n The plugin \"externalize-deps\" was triggered by this import\r\n\r\n docs/.vitepress/config.ts:1:278:\r\n 1 │ ...import_meta_url = \"file:///tmp/vpress/docs/.vitepress/config.ts\";import { defineConfig } from 'vitepress'\r\n ╵ ~~~~~~~~~~~\r\n\r\nfailed to load config from /tmp/vpress/docs/.vitepress/config.ts\r\nbuild error:\r\nError: Build failed with 1 error:\r\nnode_modules/esbuild/lib/main.js:1373:27: ERROR: [plugin: externalize-deps] \"vitepress\" resolved to an ESM file. ESM file cannot be loaded by `require`. See http://vitejs.dev/guide/troubleshooting.html#this-package-is-esm-only for more details.\r\n at failureErrorWithLog (/tmp/vpress/node_modules/esbuild/lib/main.js:1649:15)\r\n at /tmp/vpress/node_modules/esbuild/lib/main.js:1058:25\r\n at runOnEndCallbacks (/tmp/vpress/node_modules/esbuild/lib/main.js:1484:45)\r\n at buildResponseToResult (/tmp/vpress/node_modules/esbuild/lib/main.js:1056:7)\r\n at /tmp/vpress/node_modules/esbuild/lib/main.js:1085:16\r\n at responseCallbacks.\u003Ccomputed> (/tmp/vpress/node_modules/esbuild/lib/main.js:703:9)\r\n at handleIncomingPacket (/tmp/vpress/node_modules/esbuild/lib/main.js:762:9)\r\n at Socket.readFromStdout (/tmp/vpress/node_modules/esbuild/lib/main.js:679:7)\r\n at Socket.emit (node:events:513:28)\r\n at addChunk (node:internal/streams/readable:315:12)\r\n```\n\n### Reproduction\n\n```\r\nmkdir vpress\r\ncd vpress\r\nnpm install -D vitepress\r\nnpx vitepress init\r\n#│ ./docs\r\n#│ My Awesome Project\r\n#│ A VitePress Site\r\n#│ Default Theme\r\n#│ Yes\r\n#│ Yes\r\nnpm run docs:build\r\n```\n\n### Expected behavior\n\nBuild runs successfully.\n\n### System Info\n\n```sh\nSystem:\r\n OS: Linux 6.4 Fedora Linux 38.20230806.0 (Silverblue)\r\n CPU: (12) x64 11th Gen Intel(R) Core(TM) i5-11400H @ 2.70GHz\r\n Memory: 8.91 GB / 15.25 GB\r\n Container: Yes\r\n Shell: 5.2.15 - /bin/bash\r\n Binaries:\r\n Node: 16.19.0 - ~/.nvm/versions/node/v16.19.0/bin/node\r\n npm: 8.19.3 - ~/.nvm/versions/node/v16.19.0/bin/npm\r\n npmPackages:\r\n vitepress: ^1.0.0-rc.3 => 1.0.0-rc.3\r\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.",[2903],{"name":2904,"color":2905},"bug: pending triage","e99695",2754,"[ERROR] \"vitepress\" resolved to an ESM file.","2023-08-16T00:04:18Z","https://github.com/vuejs/vitepress/issues/2754",0.74085224,{"description":2912,"labels":2913,"number":2914,"owner":2872,"repository":2873,"state":2895,"title":2915,"updated_at":2916,"url":2917,"score":2918},"### Is your feature request related to a problem? Please describe.\n\nI want to vitepress cli support this feature to set some path for vitepress configuration. I search the vitepress docs and found nothing about it.\r\nHonestly, path \"./vitepress/config.ts\" is ugly to me.\n\n### Describe the solution you'd like\n\nLike that: vitepress --config yourConfigPath dev\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.",[],2084,"How can I change default config path, like /projectRoot/config/vitepress.config.ts.","2023-03-22T00:03:23Z","https://github.com/vuejs/vitepress/issues/2084",0.7416799,{"description":2920,"labels":2921,"number":2922,"owner":2872,"repository":2873,"state":2895,"title":2923,"updated_at":2924,"url":2925,"score":2926},"### Describe the bug\n\nerror happened here\r\n version: 1.1.3\n\n### Reproduction\n\nnode环境下,字符串类型没有replaceAll方法\n\n### Expected behavior\n\n能正常看到组件预览\n\n### System Info\n\n```shell\nSystem:\r\n OS: macOS 12.5.1\r\n CPU: (8) x64 Intel(R) Core(TM) i7-8557U CPU @ 1.70GHz\r\n Memory: 126.73 MB / 16.00 GB\r\n Shell: 5.8.1 - /bin/zsh\r\n Binaries:\r\n Node: 14.19.1 - /usr/local/bin/node\r\n Yarn: 1.22.4 - /usr/local/bin/yarn\r\n npm: 6.14.16 - /usr/local/bin/npm\r\n Browsers:\r\n Chrome: 107.0.5304.87\r\n Safari: 15.6.1\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.",[],1574,"replaceAll is not a function","2023-01-21T14:20:54Z","https://github.com/vuejs/vitepress/issues/1574",0.7471884,{"description":2928,"labels":2929,"number":2933,"owner":2872,"repository":2873,"state":2895,"title":2934,"updated_at":2935,"url":2936,"score":2937},"### Is your feature request related to a problem? Please describe.\r\n\r\nI'd like to write the following code on one of my VitePress pages:\r\n\r\n```vue\r\n\u003Cscript setup>\r\nimport { useRoute } from 'vitepress';\r\nimport { watch } from 'vue';\r\n\r\nconst route = useRoute();\r\n\r\nwatch(route.query, (newQuery) => {\r\n // Do something....\r\n});\r\n\u003C/script>\r\n```\r\n\r\nHowever, the current [useRoute()](https://vitepress.dev/reference/runtime-api#useroute) object does not provide access to query parameter information.\r\n\r\n### Describe the solution you'd like\r\n\r\nI'd like to be able to access the `search` property of the current location as is possible in `vue-router`:\r\n\r\nhttps://router.vuejs.org/api/interfaces/RouteLocationNormalizedLoaded.html#query\r\n\r\n### Describe alternatives you've considered\r\n\r\n_No response_\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 [Contributing Guidelines](https://github.com/vuejs/vitepress/blob/main/.github/contributing.md).\r\n- [X] Read the [docs](https://vitepress.dev).\r\n- [X] Check that there isn't already an issue that asks for the same feature to avoid creating a duplicate.",[2930],{"name":2931,"color":2932},"has-workaround","1B4515",3908,"Cannot watch for changes in route query parameters using `useRoute()`","2024-07-03T04:41:59Z","https://github.com/vuejs/vitepress/issues/3908",0.7500762,{"description":2939,"labels":2940,"number":2941,"owner":2872,"repository":2873,"state":2895,"title":2942,"updated_at":2943,"url":2944,"score":2945},"### Is your feature request related to a problem? Please describe.\n\nI have some queries if I asked them under bug its not the right place, So I request you to create a new category for help required category to ask question. \n\n### Describe the solution you'd like\n\nCreate a new Category like 'Help Required' or Ask Questions, Do we have any forum or discord to ask questions ?\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.",[],549,"Please create a category for help required","2023-01-21T16:20:04Z","https://github.com/vuejs/vitepress/issues/549",0.7503366,{"description":2947,"labels":2948,"number":2954,"owner":2872,"repository":2873,"state":2895,"title":2955,"updated_at":2956,"url":2957,"score":2958},"### Is your feature request related to a problem? Please describe.\n\nI am currently writing an API documentation and miss a function to specify http(s) requests and websocket/socket.io connections with all their parameters and responses.\n\n### Describe the solution you'd like\n\nDocument API with following features:\r\na) http(s) requests\r\nDisplay the request method and the request URL. (GET, POST, DELETE... and other methods.) It should also be possible to specify the header and body of the request with a description and the types of the parameters. Furthermore, a display for possible returns should be included which displays the response status and the send json/text/number... .\r\n(In short: specification of the request method to an API URL with the necessary parameters and the return).\r\n\r\nb) websocket / socket.io\r\nA specification of websockets contains namespaces with connection options and events. The individual events should be listed separately. These are listed with the parameters their types and descriptions. In addition, expected return events or no return are specified. Events that the server can send at any time should also be listed separately.\r\n(In short: specification of the connection url with accessable namespaces with their connect-options and a list with all events which the client and the server can send).\r\n\r\nFor both extensions, it is best to have a kind of container that directly specifies the function (GET,POST, WS...) and the URL in the header and displays the parameters and the responses when expanded.\r\nIt should also be possible to copy the URL directly by clicking on it.\r\nIt would also be great to extend the copy functionality in such a way that the parameters can be copied formatted in the programming language used (JS, C, Rust...). If the programmer wishes, he can also specify an implementation of the entire function (also in different languages).\r\n\r\nOptionally, an integration for a direct test request via the documentation can also be built in. This would also require input fields for an API key or Auth token and the required parameters.\n\n### Describe alternatives you've considered\n\nSo far I have used containers to specify the URL in the head and the content in the expandable body.\r\nI have also used the code blocks without format.\n\n### Additional context\n\nAll links below show possible designs and functions as described above.\r\n\r\nhttps://petstore.swagger.io/#/pet/\r\nhttps://redocly.github.io/redoc/#tag/pet\r\nhttps://developers.write.as/docs/api/#introduction\r\nhttps://apidocjs.com/example/\r\nhttps://stoplight.io/demo\r\nhttps://readme.com/\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.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.",[2949,2950,2953],{"name":2866,"color":2867},{"name":2951,"color":2952},"wont fix","EDEED1",{"name":2869,"color":2870},2338,"http / ws codeblocks","2023-08-12T00:04:10Z","https://github.com/vuejs/vitepress/issues/2338",0.7568868,{"description":2960,"labels":2961,"number":2962,"owner":2872,"repository":2873,"state":2895,"title":2963,"updated_at":2964,"url":2965,"score":2966},"### Is your feature request related to a problem? Please describe.\n\nNo. It's a new feature I want\n\n### Describe the solution you'd like\n\n```ts\r\nimport { useArticle } from 'vitepress'\r\nconst list = useArticle\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.",[],2111,"Need an API to get the list of all articles, then I can show the list at Home page or as a timeline","2023-03-28T00:04:34Z","https://github.com/vuejs/vitepress/issues/2111",0.7578011,["Reactive",2968],{},["Set"],["ShallowReactive",2971],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fyOfJwzLgfJFTar2kOpd84EPIzJLKh98QoQsWj00TUFE":-1},"/vuejs/vitepress/1785"]