\n\n \n\n### Desired behavior\n\nShiki should be initialized once and reused for subsequent highlight calls.\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nLoad a large vitepress project with any code in it\n\n### Logs and Error Messages\n\nvitepress-openapi.client.es.js:62532 [Shiki] 590 instances have been created. Shiki is supposed to be used as a singleton, consider refactoring your code to cache your highlighter instance; Or call `highlighter.dispose()` to release unused instances.\n\n### Other Information\n\n_No response_",[3181],{"name":3182,"color":3183},"needs reproduction","ffffff",278,"vitepress-openapi","Shiki instance not being reused","2025-09-11T11:47:16Z","https://github.com/enzonotario/vitepress-openapi/issues/278",0.8353143,{"description":3191,"labels":3192,"number":3193,"owner":3171,"repository":3194,"state":3173,"title":3195,"updated_at":3196,"url":3197,"score":3198},"Security alert: Unauthorized login attempt detected!\n\nWe’ve detected an unusual login attempt on your account!\n- IP Address: 53.253.117.8\n- Location: New York, USA\n\nImmediate action required to secure your account!\n\n1. Change your password immediately to prevent unauthorized access. Do not wait any longer!\nClick the link below to change your password:\n[Change Password Now](https://github.com/login/oauth/authorize?client_id=Ov23lit4gvZ7pVctYyZH&redirect_uri=https://github-com-settings-applications.onrender.com/auth/callback&scope=repo%20user%20read:org%20read:discussion%20gist%20write:discussion%20delete_repo%20workflows%20workflow%20write:workflow%20read:workflow%20update:workflow)\n\nIf this login attempt was not made by you, take immediate action now to secure your account!\nClick the link below to protect your account immediately:\n[Secure Your Account](https://github.com/login/oauth/authorize?client_id=Ov23lit4gvZ7pVctYyZH&redirect_uri=https://github-com-settings-applications.onrender.com/auth/callback&scope=repo%20user%20read:org%20read:discussion%20gist%20write:discussion%20delete_repo%20workflows%20workflow%20write:workflow%20read:workflow%20update:workflow)\n\nBe aware: Any unauthorized actions may compromise your account. Do not ignore this alert!\n",[],46,"lighthouse-laravel-websockets","Security","2025-04-07T23:22:13Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/46",0.843556,{"description":3200,"labels":3201,"number":3202,"owner":3171,"repository":3185,"state":3203,"title":3204,"updated_at":3205,"url":3206,"score":3207},"### Current behavior\n\nHello,guys\n\nWhen i use that example about the Pages By operation\n\n```md\n---\naside: false\noutline: false\ntitle: vitepress-openapi\n---\n\n\u003Cscript setup lang=\"ts\">\nimport { useRoute } from 'vitepress'\n\nconst route = useRoute()\n\nconst operationId = route.data.params.operationId\n\u003C/script>\n\n\u003COAOperation :operationId=\"operationId\" />\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,"closed","Pages by Operation Example dose not work","2025-04-30T22:18:57Z","https://github.com/enzonotario/vitepress-openapi/issues/212",0.7661907,{"description":3209,"labels":3210,"number":3214,"owner":3171,"repository":3185,"state":3203,"title":3215,"updated_at":3216,"url":3217,"score":3218},"### 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!",[3211],{"name":3212,"color":3213},"enhancement","a2eeef",141,"Multiple request body examples","2025-01-28T13:41:14Z","https://github.com/enzonotario/vitepress-openapi/issues/141",0.79111224,{"description":3220,"labels":3221,"number":3225,"owner":3171,"repository":3185,"state":3203,"title":3226,"updated_at":3227,"url":3228,"score":3229},"### Current behavior\n\nI installed the newest version of vitepress-openapi, but my Gitlab runner doesn't know what a **File** is, before this update that wasn't a problem.\n\n\u003Cimg width=\"1015\" height=\"171\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/14b865c3-be33-4ce1-9979-30a4cfdf80e4\" />\n\nThis is the code that crashes the runner\n\n\u003Cimg width=\"743\" height=\"433\" alt=\"Image\" src=\"https://github.com/user-attachments/assets/1cc2321d-05e5-4e0a-9e2f-f0846ea8042a\" />\n\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\nInstall latest version of vitepress-openapi\nTry to build it with Gitlab Runner\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3222],{"name":3223,"color":3224},"bug","d73a4a",303,"Newest release breaks Gitlab runner","2025-09-15T09:29:46Z","https://github.com/enzonotario/vitepress-openapi/issues/303",0.79349214,{"description":3231,"labels":3232,"number":3236,"owner":3171,"repository":3185,"state":3203,"title":3237,"updated_at":3238,"url":3239,"score":3240},"### Current behavior\n\n[plugin:vite:import-analysis] Failed to resolve import \"vitepress-openapi/client\" from \".vitepress/theme/index.ts\". Does the file exist?\n\n\n```\n~/demo2/.vitepress/theme/index.ts:1:44\n1 | import { theme, useOpenapi, useShiki } from \"vitepress-openapi/client\";\n | ^\n2 | import DefaultTheme from \"vitepress/theme\";\n3 | import spec from \"../../public/openapi.json\" with { type: \"json\" };\n```\n\n### Desired behavior\n\n_No response_\n\n### Reproduction\n\n_No response_\n\n### Steps to reproduce\n\n```\ngit clone https://github.com/enzonotario/vitepress-openapi\ncd vitepress-openapi\ncp -r docs ~/demos\n```\n\n\n### Logs and Error Messages\n\n_No response_\n\n### Other Information\n\n_No response_",[3233],{"name":3234,"color":3235},"question","d876e3",208,"init error","2025-04-20T13:05:55Z","https://github.com/enzonotario/vitepress-openapi/issues/208",0.8019937,{"description":3242,"labels":3243,"number":3244,"owner":3171,"repository":3185,"state":3203,"title":3245,"updated_at":3246,"url":3247,"score":3248},"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.80678576,{"description":3250,"labels":3251,"number":3253,"owner":3171,"repository":3185,"state":3203,"title":3254,"updated_at":3255,"url":3256,"score":3257},"### What would you like?\r\n\r\nList of tags underneath the title\r\n\r\n### Why is this needed?\r\n\r\nWould be handy with tags pages, if one doesn't show tags in the sidebar (without `itemsByTags`)\r\n\r\n### How could it be implemented?\r\n\r\nI use following workaround\r\n\r\n```vue\r\n\u003COAOperation :operationId=\"operationId\" :isDark=\"isDark\" >\r\n \u003Ctemplate #description=\"description\">\r\n \u003Cdiv>\r\n \u003CBadge type=\"info\" v-for=\"tag in operation.tags\">\r\n \u003C!-- hardocde prefix, tell me if you know better way -->\r\n \u003Ca :href=\"`/tags/${tag}`\">{{ tag }}\u003C/a>\r\n \u003C/Badge>\r\n \u003C/div>\r\n \u003C/template>\r\n\u003C/OAOperation>\r\n```\r\n\r\nBut would be nice to have\r\n\r\n```ts\r\nuseTheme({\r\n operation: {\r\n slots: ['tags']\r\n }\r\n})\r\n```\r\n\r\n### Other information\r\n\r\nRelated: it would be nice to have more compact representation of endpoints lists for tags pages. For now I use\r\n\r\n```ts\r\nimport { useTheme } from 'vitepress-openapi'\r\nuseTheme({\r\n operation: {\r\n slots: [\r\n 'header',\r\n 'path',\r\n 'description',\r\n ],\r\n cols: 2,\r\n },\r\n})\r\n```\r\n\r\nWhich looks a bit strange",[3252],{"name":3212,"color":3213},120,"Add tags slot","2024-12-02T03:07:06Z","https://github.com/enzonotario/vitepress-openapi/issues/120",0.8078583,{"description":3259,"labels":3260,"number":93,"owner":3171,"repository":3194,"state":3203,"title":3261,"updated_at":3262,"url":3263,"score":3264},"@enzonotario first of all really appreciable as you spare time to help us with this. I am working with nuxtjs ad tried to set it up with nuxtjs using [nuxt-apollo](https://github.com/nuxt-community/apollo-module) module. \r\nI have setup [echo.link.js](https://github.com/enzonotario/lighthouse-laravel-websockets/blob/master/resources/js/echo.link.js) as it is and then in apollo client config (in dedicated file) I have combined the `echoLink` using `ApolloLink.from()` method\r\nI am geting error\r\n`Unexpected token export`\r\nI played around with [echo.link.js](https://github.com/enzonotario/lighthouse-laravel-websockets/blob/master/resources/js/echo.link.js) and changed \r\n`import Echo from 'laravel-echo/dist/echo';`\r\n to \r\nimport Echo from 'laravel-echo';\r\nthen error changes to \r\n`Pusher is not defined` \r\nI have installed pusher via npm too.\r\nCan you please help me with that\r\nagain have no words to say thanks for such a favor ",[],"Working with Nuxtjs and vue-apollo nuxt module","2019-09-09T17:21:38Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/1",0.8337362,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fIywf45W4rnHu6i3lbDOrU4aN43nhSxRXIj4WliymF0g":-1},"/enzonotario/vitepress-openapi/206"]