\n\n```\n\n```js\nimport { usePaths } from 'vitepress-openapi'\nimport spec from '../../public/test.json' with {type: 'json'}\n\nexport default {\n paths() {\n return usePaths({ spec })\n .getPathsByVerbs()\n .map(({ operationId, summary }) => {\n return {\n params: {\n operationId,\n pageTitle: `${summary} - vitepress-openapi`,\n },\n }\n })\n },\n}\n```\n\nThe terminal show this error,but i dont understand what it mean\n\n\n\nThe terminal guide me the links https://cn.vite.dev/guide/troubleshooting which is show The CJS build of Vite's Node API is deprecated and will be removed in Vite 6. \n\nHope u give the answer thank u so much\n\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n\n\n### Logs and Error Messages\n\n\n\n### Other Information\n\n_No response_",[],212,"Pages by Operation Example dose not work","2025-04-30T22:18:57Z","https://github.com/enzonotario/vitepress-openapi/issues/212",0.80689514,{"description":2881,"labels":2882,"number":1229,"owner":2857,"repository":2883,"state":2859,"title":2884,"updated_at":2885,"url":2886,"score":2887},"Hi @enzonotario \r\n\r\nFirst of all, thank you for this repo! It is very helpful.\r\nI followed exactly the steps you wrote, but i get a strange error, and i ran out of ideas what could be wrong. I receive an error message from Pusher in the console saying: json returned from auth endpoint was invalid, yet status code was 200.\r\nIn the DevTools i see that it hits the authEndpoint with status code 200, but as a response i get back the content of my app.blade.php. It is really strange. Do you have any idea what could cause this?\r\n\r\nIt's not just my app. I downloaded and installed this repo of yours, and i get the same error.",[],"lighthouse-laravel-websockets","json returned from auth endpoint was invalid, yet status code was 200.","2020-04-16T18:51:33Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/6",0.8100784,{"description":2889,"labels":2890,"number":2894,"owner":2857,"repository":2858,"state":2859,"title":2895,"updated_at":2896,"url":2897,"score":2898},"### What would you like?\n\nI'd like to be able to render the openapi specification with a signle column layout. It would be nice if it is configurable in the parameters of the components like OASpec or globally in the theme config. In addition to that, it would also be nice if the different child components could be enabled/disabled (i.e. turn off samples). \n\n### Why is this needed?\n\nI want this because the standard theme does not have a lot of content width, Having a two column layout looks crowded and sometimes the content is wrapped. Having all the child components below each other with a single column layout would bring more clarity to the rendered documentation.\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[2891],{"name":2892,"color":2893},"enhancement","a2eeef",91,"Single column layout","2024-10-27T14:41:53Z","https://github.com/enzonotario/vitepress-openapi/issues/91",0.81968296,{"description":2900,"labels":2901,"number":2902,"owner":2857,"repository":2903,"state":2859,"title":2904,"updated_at":2905,"url":2906,"score":2907},"_Originally posted by @danielGithinji in https://github.com/moby/buildkit/pull/5291_",[],40,"esjs-dolar-api","H","2025-03-02T11:54:17Z","https://github.com/enzonotario/esjs-dolar-api/issues/40",0.8199856,{"description":2909,"labels":2910,"number":2912,"owner":2857,"repository":2858,"state":2859,"title":2913,"updated_at":2914,"url":2915,"score":2916},"### Current behavior\r\n\r\nMy openapi spec contains oneOf and prefixItems \r\n\r\n- [x] #124\r\n\r\n- [x] #125\r\n\r\n### Desired behavior\r\n\r\n_No response_\r\n\r\n### Reproduction\r\n\r\n_No response_\r\n\r\n### Steps to reproduce\r\n\r\n```\r\ngit clone https://github.com/wighawag/fuzd.git\r\ncd fuzd\r\ngit checkout feat/vitepress-openapi\r\npnpm i\r\npnpm docs:dev\r\n# for oneOf, see http://localhost:5173/api-all-in-one/#get-api-paymentAccountBroadcaster\r\n# it shows null, while null is only one of the possible type\r\n\r\n# for prefixItems I had an earlier example here : https://github.com/wighawag/fuzd/commit/d47b3452280a13aeb6d38c6c7301e51b8be7f2fc\r\n# where error (click 500) where not showing properly because I was using prefixItems\r\n```\r\n\r\n### Logs and Error Messages\r\n\r\n_No response_\r\n\r\n### Other Information\r\n\r\n_No response_",[2911],{"name":2892,"color":2893},111,"prefixItems and oneOf does not seems to be supported","2025-05-03T22:18:47Z","https://github.com/enzonotario/vitepress-openapi/issues/111",0.82012135,{"description":2918,"labels":2919,"number":2921,"owner":2857,"repository":2858,"state":2859,"title":2922,"updated_at":2923,"url":2924,"score":2925},"### What would you like?\r\n\r\nIt would be nice to have a select element that switches between request body examples.\r\nThis is possible in swagger UI, for example:\r\n\r\n\u003Cimg width=\"1672\" alt=\"Screenshot 2024-12-27 at 15 12 50\" src=\"https://github.com/user-attachments/assets/e5313373-cc8f-4027-9311-0e5d446b6027\" />\r\n\r\n\r\n\r\n### Why is this needed?\r\n\r\nThis is useful for endpoints that accept different request bodies\r\n\r\n### How could it be implemented?\r\n\r\nImplement and show a select element when examples are present in openapi.json:\r\n\r\n```\r\n \"requestBody\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/ExamplePost\"\r\n },\r\n \"examples\": {\r\n \"Example 1\": {\r\n \"summary\": \"Creating example 1\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\"\r\n }\r\n },\r\n \"example 2\": {\r\n \"summary\": \"Creating example 2\",\r\n \"value\": {\r\n \"first_name\": \"John\",\r\n \"last_name\": \"Doe\",\r\n \"email\": \"test@test.com\",\r\n \"phone_number\": \"123456789\"\r\n }\r\n }\r\n }\r\n }\r\n },\r\n \"required\": true\r\n },\r\n```\r\n\r\n### Other information\r\n\r\nI couldn't find this anywhere in the documentation, but if it is already possible i would like to know how. Thank you!",[2920],{"name":2892,"color":2893},141,"Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.8208469,{"description":2927,"labels":2928,"number":104,"owner":2857,"repository":2903,"state":2859,"title":2930,"updated_at":2931,"url":2932,"score":2933},"Sugiero que la API retorne cotizaciones del día anterior, de esa manera se puede calcular fácilmente las variaciones porcentuales.\r\n\r\nEjemplo:\r\n\r\n```\r\n[\r\n \"Hoy\": {\r\n \"compra\": \"number\",\r\n \"venta\": \"number\",\r\n \"casa\": \"string\",\r\n \"nombre\": \"string\",\r\n \"moneda\": \"string\",\r\n \"fechaActualizacion\": \"string\"\r\n },\r\n \"Ayer\": {\r\n \"compra\": \"number\",\r\n \"venta\": \"number\",\r\n \"casa\": \"string\",\r\n \"nombre\": \"string\",\r\n \"moneda\": \"string\",\r\n \"fechaActualizacion\": \"string\"\r\n }\r\n]\r\n```",[2929],{"name":2892,"color":2893},"[New Feature] Añadir cotización del día anterior","2024-01-31T23:06:14Z","https://github.com/enzonotario/esjs-dolar-api/issues/3",0.82166743,{"description":2935,"labels":2936,"number":104,"owner":2857,"repository":2858,"state":2859,"title":2937,"updated_at":2938,"url":2939,"score":2933},"> operationId is an optional unique string used to identify an operation. If provided, these IDs must be unique among all operations described in your API.\r\n\r\nAs a result my spec doesnt actually have `operationId` in it for each route\r\nIt would be great if route and method could be used in combination insead of operationId :)",[],"Allow selection by path / key as well as / insead of operationId ?","2024-08-27T23:04:25Z","https://github.com/enzonotario/vitepress-openapi/issues/3",["Reactive",2941],{},["Set"],["ShallowReactive",2944],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f-xPiVRBh5GgbHdHTk4BGF65emXcVIyX3u43_lTS1jK4":-1},"/enzonotario/vitepress-openapi/223"]