\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.83380616,{"description":3078,"labels":3079,"number":3080,"owner":3009,"repository":3023,"state":3024,"title":3081,"updated_at":3082,"url":3083,"score":3084},"Hi! It took me some time to figure out how to prevent vitepress-openapi styles from leaking into `.vp-raw` (`:::raw`) blocks. Consider adding an example to the documentation:\n\n```js\n// docs/postcss.config.mjs\n\nimport { postcssIsolateStyles } from 'vitepress';\n\nexport default {\n plugins: [\n // Make `::: raw` sections be isolated from vitepress-openapi plugin styles\n postcssIsolateStyles({\n includeFiles: [ /vitepress-openapi\\.css/ ], // ← NOT `vitepress-openapi/dist/style.css` (!)\n }),\n ],\n};\n```\n\nThank you for your work!",[],251,"Mention style isolation in documentation","2025-07-05T14:22:04Z","https://github.com/enzonotario/vitepress-openapi/issues/251",0.83628076,{"description":3086,"labels":3087,"number":3089,"owner":3009,"repository":3023,"state":3024,"title":3090,"updated_at":3091,"url":3092,"score":3093},"Follow on to https://github.com/enzonotario/vitepress-theme-openapi/issues/10\r\n\r\nIt would be great to allow trying out requests that have a body required.\r\n\r\nProbably a first version of this would just provide a single text input box for the whole \"body\" to be provided.\r\n\r\nUsers could then easily copy and paste the example (probably json) body, and modify it",[3088],{"name":3020,"color":3021},42,"Support body for \"try it out\"","2024-09-24T05:03:33Z","https://github.com/enzonotario/vitepress-openapi/issues/42",0.8365918,{"description":3095,"labels":3096,"number":3100,"owner":3009,"repository":3023,"state":3024,"title":3101,"updated_at":3102,"url":3103,"score":3104},"### Current behavior\n\nOn some route, the schema view is empty even though the json view is not\n\n### Desired behavior\n\nI expect the schema view to always represent the type\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\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# navigate to http://localhost:5173/api/post-api-scheduling-scheduleExecution.html\r\n# click on Schema view for Request Body, see it is empty\r\n```\r\n\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3097],{"name":3098,"color":3099},"bug","d73a4a",110,"Schema view empty even though json view is not","2024-11-30T14:09:26Z","https://github.com/enzonotario/vitepress-openapi/issues/110",0.83851093,["Reactive",3106],{},["Set"],["ShallowReactive",3109],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fTVhjUK3Zj1OXV8aXRqHq0_7RR3-V7SvwBxNCG_Q9iig":-1},"/enzonotario/vitepress-openapi/178"]