\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_",[],278,"enzonotario","vitepress-openapi","open","Shiki instance not being reused","2025-07-20T22:19:25Z","https://github.com/enzonotario/vitepress-openapi/issues/278",0.82095444,{"description":3028,"labels":3029,"number":2391,"owner":3020,"repository":3021,"state":3036,"title":3037,"updated_at":3038,"url":3039,"score":3040},"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",[3030,3033],{"name":3031,"color":3032},"enhancement","a2eeef",{"name":3034,"color":3035},"help wanted","008672","closed","Support security schema rendering","2024-08-30T22:52:04Z","https://github.com/enzonotario/vitepress-openapi/issues/12",0.453971,{"description":3042,"labels":3043,"number":1443,"owner":3020,"repository":3044,"state":3036,"title":3045,"updated_at":3046,"url":3047,"score":3048},"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":3050,"labels":3051,"number":734,"owner":3020,"repository":3044,"state":3036,"title":3052,"updated_at":3053,"url":3054,"score":3055},"",[],"does it work with v4 lighthouse?","2020-11-07T13:40:11Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/2",0.7898943,{"description":3057,"labels":3058,"number":734,"owner":3020,"repository":3021,"state":3036,"title":3059,"updated_at":3060,"url":3061,"score":3055},"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":3063,"labels":3064,"number":3071,"owner":3020,"repository":3021,"state":3036,"title":3072,"updated_at":3073,"url":3074,"score":3075},"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",[3065,3068],{"name":3066,"color":3067},"documentation","0075ca",{"name":3069,"color":3070},"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":3077,"labels":3078,"number":3080,"owner":3020,"repository":3021,"state":3036,"title":3081,"updated_at":3082,"url":3083,"score":3084},"### 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_",[3079],{"name":3069,"color":3070},229,"How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.80956537,{"description":3086,"labels":3087,"number":3089,"owner":3020,"repository":3021,"state":3036,"title":3090,"updated_at":3091,"url":3092,"score":3093},"### 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_",[3088],{"name":3031,"color":3032},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":3095,"labels":3096,"number":3097,"owner":3020,"repository":3021,"state":3036,"title":3098,"updated_at":3099,"url":3100,"score":3101},"### 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,{"description":3103,"labels":3104,"number":3106,"owner":3020,"repository":3021,"state":3036,"title":3107,"updated_at":3108,"url":3109,"score":3110},"Especifico el tipo de respuesta que retornara la petición, pero lo toma como un objeto.\r\n\r\n--\r\n\r\n",[3105],{"name":3031,"color":3032},33,"Tipo de respuesta ","2024-09-26T23:34:06Z","https://github.com/enzonotario/vitepress-openapi/issues/33",0.81700975,["Reactive",3112],{},["Set"],["ShallowReactive",3115],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$f79yZ1254sqZjaibEYniy7E39tD_AizxaXgqJeKjPp5o":-1},"/enzonotario/lighthouse-laravel-websockets/12"]