\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":3193,"state":3194,"title":3195,"updated_at":3196,"url":3197,"score":3198},"Hi,\r\n \r\n Nice work you've done here, but i am wondering if there is a other way to support subscription with lighthouse because is so much work to be done to make it work and there must be a way implemented by them.. or should be 👍 \r\n Also I am wondering if you can tell me.. from what i've checked you trigger a subscription from web/routes.php (home page) by clicking on that button, but you can can make that mutation that you have created work in playground?",[],"lighthouse-laravel-websockets","closed","Subscription","2020-11-07T13:39:54Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/12",0.453971,{"description":3200,"labels":3201,"number":1455,"owner":3175,"repository":3193,"state":3194,"title":3202,"updated_at":3203,"url":3204,"score":3205},"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!",[],"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":3207,"labels":3208,"number":736,"owner":3175,"repository":3193,"state":3194,"title":3209,"updated_at":3210,"url":3211,"score":3212},"",[],"does it work with v4 lighthouse?","2020-11-07T13:40:11Z","https://github.com/enzonotario/lighthouse-laravel-websockets/issues/2",0.7898943,{"description":3214,"labels":3215,"number":736,"owner":3175,"repository":3176,"state":3194,"title":3216,"updated_at":3217,"url":3218,"score":3212},"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":3220,"labels":3221,"number":3228,"owner":3175,"repository":3176,"state":3194,"title":3229,"updated_at":3230,"url":3231,"score":3232},"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",[3222,3225],{"name":3223,"color":3224},"documentation","0075ca",{"name":3226,"color":3227},"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":3234,"labels":3235,"number":3237,"owner":3175,"repository":3176,"state":3194,"title":3238,"updated_at":3239,"url":3240,"score":3241},"### 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_",[3236],{"name":3226,"color":3227},229,"How can I custom the render component","2025-05-31T22:29:15Z","https://github.com/enzonotario/vitepress-openapi/issues/229",0.80956537,{"description":3243,"labels":3244,"number":3248,"owner":3175,"repository":3176,"state":3194,"title":3249,"updated_at":3250,"url":3251,"score":3252},"### 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_",[3245],{"name":3246,"color":3247},"enhancement","a2eeef",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":3254,"labels":3255,"number":3256,"owner":3175,"repository":3176,"state":3194,"title":3257,"updated_at":3258,"url":3259,"score":3260},"### 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",3262],{},["Set"],["ShallowReactive",3265],{"$fTRc1wZytZ_XrK4EfJfei_Sz-An4H4Yy6syhVxH_PVJc":-1,"$fBQwil0WzYwRfyULWFBum3WGdcdm3Idzg7ZkExY9FfaI":-1},"/enzonotario/vitepress-openapi/12"]