\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_",[3171],{"name":3172,"color":3173},"needs reproduction","ffffff",278,"enzonotario","vitepress-openapi","open","Shiki instance not being reused","2025-09-11T11:47:16Z","https://github.com/enzonotario/vitepress-openapi/issues/278",0.82095444,{"description":3183,"labels":3184,"number":93,"owner":3175,"repository":3185,"state":3177,"title":3186,"updated_at":3187,"url":3188,"score":3189},"Si quieres proponer nuevas APIs para ser documentadas, deja un comentario incluyendo lo siguiente:\n\n- Nombre de la API:\n- Descripción breve:\n- URL del OpenAPI o documentación oficial:",[],"apidocs.ar","Propuestas de nuevas APIs a documentar","2025-08-30T12:25:19Z","https://github.com/enzonotario/apidocs.ar/issues/1",0.83535933,{"description":3191,"labels":3192,"number":2407,"owner":3175,"repository":3176,"state":3199,"title":3200,"updated_at":3201,"url":3202,"score":3203},"My API has a security scheme defined, such as the following\r\n\r\n```\r\n \"security\": [\r\n {\r\n \"ApiKeyAuth\": []\r\n }\r\n ],\r\n \"components\": {\r\n \"securitySchemes\": {\r\n \"ApiKeyAuth\": {\r\n \"type\": \"apiKey\",\r\n \"in\": \"header\",\r\n \"name\": \"Authorization\"\r\n }\r\n },\r\n```\r\n\r\nWhich can then be interpereted as being applied globally, or overridden on a per route level, such as by defining\r\n\r\n\r\n```\r\n \"security\": [\r\n {\r\n \"ApiKeyAuth\": []\r\n }\r\n ]\r\n```\r\n\r\nFor the route.\r\n\r\nPer the spec at https://swagger.io/docs/specification/authentication/\r\n\r\nAs far as I can see this is not currently represeented anywhere by the component\r\n\r\n\r\n\r\nhttps://gist.github.com/addshore/e6b973939739e25902025bf1667e69a1 is an example API spec that demonstrates this feature and thus issue",[3193,3196],{"name":3194,"color":3195},"enhancement","a2eeef",{"name":3197,"color":3198},"help wanted","008672","closed","Support security schema rendering","2024-08-30T22:52:04Z","https://github.com/enzonotario/vitepress-openapi/issues/12",0.453971,{"description":3205,"labels":3206,"number":1455,"owner":3175,"repository":3207,"state":3199,"title":3208,"updated_at":3209,"url":3210,"score":3211},"Hi There,\r\n\r\nI am here because of this issue: https://github.com/nuwave/lighthouse/issues/1796.\r\n\r\nYour code added to the `ArrayChannelManager` removes _all_ subscriptions connection to the websocket server each time a connection is removed from all channels.\r\n\r\nhttps://github.com/enzonotario/lighthouse-laravel-websockets/blob/222531f198a4722ad9928f39aa7e96474071b6d9/app/WebSockets/Channels/ChannelManager/ArrayChannelManager.php#L16-L19\r\n\r\nThis also removes subscription for other connections, so this code only works if you have a single connection connected, but as you add more connections every time one of them disconnects it will remove _all_ subscriptions.\r\n\r\nMight I suggest you update the example with some of the new ideas from here: https://github.com/nuwave/lighthouse/issues/847#issuecomment-618254044?\r\n\r\nThis way when people use your example they won't have a broken setup like the author of the issue I mentioned earlier.\r\n\r\nThanks for creating it in the first place, a lot of people have a hard time getting it working and we are working towards official support in Lighthouse but until that time I'd appreciate it if you could update!",[],"lighthouse-laravel-websockets","Warning, this example removes _all_ subscriptions when closing a single connection","2021-04-23T22:45:29Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/17",0.75599384,{"description":3213,"labels":3214,"number":736,"owner":3175,"repository":3207,"state":3199,"title":3215,"updated_at":3216,"url":3217,"score":3218},"",[],"does it work with v4 lighthouse?","2020-11-07T13:40:11Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/2",0.7898943,{"description":3220,"labels":3221,"number":736,"owner":3175,"repository":3176,"state":3199,"title":3222,"updated_at":3223,"url":3224,"score":3218},"By default ES is used, and I have the component rendering, but can't figure out how to switch to en by default.\r\nDocumentaiton for this would be appreciated.",[],"How to use the EN locale / language","2024-08-24T10:20:43Z","https://github.com/enzonotario/vitepress-openapi/issues/2",{"description":3226,"labels":3227,"number":3234,"owner":3175,"repository":3176,"state":3199,"title":3235,"updated_at":3236,"url":3237,"score":3238},"Hey there! First of all, thank you so much for such a cool enhancement to VitePress.\n\nI'm currently using the `By Operation` method of displaying OAS content, i.e. grouping the specific endpoint pages under the tags in the sidebar.\n\nIs it possible to make the categories/groupings collapsed by default, or introduce the collapsing mechanism from VitePress altogether? Something akin to `collapsed: true` [for the VitePress sidebar groups](https://vitepress.dev/reference/default-theme-sidebar#collapsible-sidebar-groups).\n\nHere's a grouping that I would like collapsed, to help visualize this issue:\n\n",[3228,3231],{"name":3229,"color":3230},"documentation","0075ca",{"name":3232,"color":3233},"question","d876e3",195,"Collapsible operation grouping in the sidebar","2025-04-08T21:55:25Z","https://github.com/enzonotario/vitepress-openapi/issues/195",0.7908356,{"description":3240,"labels":3241,"number":3243,"owner":3175,"repository":3176,"state":3199,"title":3244,"updated_at":3245,"url":3246,"score":3247},"### What would you like?\n\nHow can I create my own custom components to implement my own needs?\n\n### Why is this needed?\n\n_No response_\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3242],{"name":3232,"color":3233},229,"How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.80956537,{"description":3249,"labels":3250,"number":3252,"owner":3175,"repository":3176,"state":3199,"title":3253,"updated_at":3254,"url":3255,"score":3256},"### What would you like?\n\nI'd love it if there was an easy to use component that allowed displaying a link that looked like the nice fancy sidebars\n\nThis should be documented\n\n\n\nI'd like to be able to use this anywhere in text\n\n### Why is this needed?\n\n_No response_\n\n### How could it be implemented?\n\n_No response_\n\n### Other information\n\n_No response_",[3251],{"name":3194,"color":3195},222,"Reusable component for linking to specs / api pages","2025-06-30T01:23:53Z","https://github.com/enzonotario/vitepress-openapi/issues/222",0.81524414,{"description":3258,"labels":3259,"number":3260,"owner":3175,"repository":3176,"state":3199,"title":3261,"updated_at":3262,"url":3263,"score":3264},"### 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,"Pages by Operation Example dose not work","2025-04-30T22:18:57Z","https://github.com/enzonotario/vitepress-openapi/issues/212",0.815585,["Reactive",3266],{},["Set"],["ShallowReactive",3269],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f79yZ1254sqZjaibEYniy7E39tD_AizxaXgqJeKjPp5o":-1},"/enzonotario/lighthouse-laravel-websockets/12"]