\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.8006756,{"description":2887,"labels":2888,"number":666,"owner":2856,"repository":2866,"state":2858,"title":2889,"updated_at":2890,"url":2891,"score":2892},"Uso query params para invalidar caché pero en la API al incluir cualquier cosa a la URL hace que devuelva 404. Creo que debería devolver el recurso ignorando los params\r\n\r\nEjemplo: https://dolarapi.com/v1/dolares/blue?t=2023-01-16",[],"URL con querystring devuelve 404","2024-01-20T00:15:10Z","https://github.com/enzonotario/esjs-dolar-api/issues/12",0.80501837,{"description":2894,"labels":2895,"number":2899,"owner":2856,"repository":2874,"state":2858,"title":2900,"updated_at":2901,"url":2902,"score":2903},"The generated example code looks like this...\n\n```\ncurl 'https://api.foo/v2/devices/%7Bid%7D/tags' \\\n --header 'Authorization: xxx'\n```\n\nHowever really in the UI it would be nicer to look like\n\n```\ncurl 'https://api.foo/v2/devices/{id}/tags' \\\n --header 'Authorization: xxx'\n```",[2896],{"name":2897,"color":2898},"enhancement","a2eeef",223,"Ugly display of { and } in example code","2025-05-18T01:28:54Z","https://github.com/enzonotario/vitepress-openapi/issues/223",0.8112314,{"description":2905,"labels":2906,"number":2907,"owner":2856,"repository":2857,"state":2858,"title":2908,"updated_at":2909,"url":2910,"score":2911},"after running `composer-update` and install `redis`, in first serve the application i get this error on console:\r\n\r\n```\r\nGraphQL execution errors for subscription 'subscribed'\r\n\r\n\r\nObject { debugMessage: \"Connection refused\", message: \"Internal server error\", extensions: {…}, locations: (1) […], path: (1) […], trace: (63) […] }\r\n\r\ndebugMessage: \"Connection refused\"\r\n\r\nextensions: Object { category: \"internal\" }\r\n\r\nlocations: Array [ {…} ]\r\n\r\nmessage: \"Internal server error\"\r\n\r\npath: Array [ \"test\" ]\r\n\r\ntrace: Array(63) [ {…}, {…}, {…}, … ]\r\n\r\n\u003Cprototype>: Object { … }\r\n```\r\n\r\nhow can i resolve this problem? thanks in advance",[],30,"Getting error on first serve sample","2021-11-08T00:33:32Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/30",0.8139553,{"description":2913,"labels":2914,"number":2916,"owner":2856,"repository":2874,"state":2858,"title":2917,"updated_at":2918,"url":2919,"score":2920},"### 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_",[2915],{"name":2897,"color":2898},111,"prefixItems and oneOf does not seems to be supported","2025-05-03T22:18:47Z","https://github.com/enzonotario/vitepress-openapi/issues/111",0.8180129,{"description":2922,"labels":2923,"number":1562,"owner":2856,"repository":2866,"state":2858,"title":2925,"updated_at":2926,"url":2927,"score":2928},"¡Hola! **Sugiero que la API añada una nueva cotización del dólar.** Específicamente el **Dólar Tarjeta.** Tengo una aplicación que consumiría de la API para calcular los precios finales de los juegos en Steam. \r\n\r\nLos precios se calculan en base al Dólar Tarjeta, que es una cotización diferente de las demás, y que la API no posee. \r\n**Adjunto un enlace en el que se tiene el valor actualizado día a día del Dólar Tarjeta:** [Cotización del dólar tarjeta vía El Cronista](https://www.cronista.com/MercadosOnline/moneda.html?id=ARSTAR)\r\n\r\nQue tenga un endpoint como...\r\n`/v1/dolares/cronista/tarjeta`\r\n\r\nAgradecería muchísimo esta nueva característica. Ya que esto, posibilitaría que la aplicación mía ([Impue-Steam](https://impue-steam.netlify.app/)) funcione correctamente.\r\n\r\nMuchísimas gracias de antemano.",[2924],{"name":2897,"color":2898},"[New feature] Agregar nueva cotización: Dólar Tarjeta","2023-11-06T21:47:37Z","https://github.com/enzonotario/esjs-dolar-api/issues/5",0.81890386,{"description":2930,"labels":2931,"number":2935,"owner":2856,"repository":2874,"state":2858,"title":2936,"updated_at":2937,"url":2938,"score":2939},"My rendered component looks something like this\r\n\r\n\r\n\r\nHowever the define route doesnt require authentication\r\n\r\n```\r\n \"/users/login\": {\r\n \"post\": {\r\n \"description\": \"lalala.\",\r\n \"requestBody\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/LoginRequest\"\r\n }\r\n }\r\n },\r\n \"description\": \"Login\",\r\n \"required\": true\r\n },\r\n \"responses\": {\r\n \"200\": {\r\n \"content\": {\r\n \"application/json\": {\r\n \"schema\": {\r\n \"$ref\": \"#/components/schemas/LoginResponse\"\r\n }\r\n }\r\n },\r\n \"description\": \"OK\"\r\n },\r\n },\r\n \"summary\": \"Login\",\r\n \"tags\": [\r\n \"users\"\r\n ]\r\n }\r\n },\r\n```\r\n\r\nOther endpoints do specify it as a requirement\r\n\r\n```\r\n \"security\": [\r\n {\r\n \"ApiKeyAuth\": []\r\n }\r\n ],\r\n```\r\n\r\nAnd it is defined as a schema in the spec\r\n\r\n```\r\n \"securitySchemes\": {\r\n \"ApiKeyAuth\": {\r\n \"in\": \"header\",\r\n \"name\": \"Authorization\",\r\n \"type\": \"apiKey\"\r\n }\r\n }\r\n```\r\n\r\nBut it should not be rendered by default unless they are deinfed in a top level `security` section\r\n\r\nSee https://swagger.io/docs/specification/authentication/ `Step 2.`",[2932],{"name":2933,"color":2934},"bug","d73a4a",36,"securitySchemes should only be applied to routes that require it","2024-09-14T16:10:12Z","https://github.com/enzonotario/vitepress-openapi/issues/36",0.819767,["Reactive",2941],{},["Set"],["ShallowReactive",2944],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fVOJgoZC6apFXcdThYVh66-gn60gUUukkf92jkjVXP98":-1},"/enzonotario/lighthouse-laravel-websockets/6"]