You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Have you considered publishing this to the JSR registry?
I really like it and have been using it for a while. it offers so many more features compared to npm, and it's not stuck in the past (you can directly publish TS without transpilation).
publishing to JSR also makes it easier to use in Deno
I think we need to evaluate whether publishing to JSR brings enough benefit for Socket.IO users, especially given the Node-specific parts of the project and the extra release maintenance it would introduce.
You’re right, my point about “Node-specific parts” was too hand-wavy, and probably not a good argument as stated.
However, I still think we should evaluate what concrete work is required and whether there is enough demand from Socket.IO users to justify adding JSR to the release pipeline.
Activity
darrachequesne commentedon Sep 29, 2026
I think we need to evaluate whether publishing to JSR brings enough benefit for Socket.IO users, especially given the Node-specific parts of the project and the extra release maintenance it would introduce.
Open to suggestions though.
sakgoyal commentedon Sep 29, 2026
Deno/Bun are both compatible with node APIs so I don't think it will have any issues.
Can you give me an example of a node specific API that Deno/Bun do not handle?
darrachequesne commentedon Oct 6, 2026
You’re right, my point about “Node-specific parts” was too hand-wavy, and probably not a good argument as stated.
However, I still think we should evaluate what concrete work is required and whether there is enough demand from Socket.IO users to justify adding JSR to the release pipeline.