Skip to content

Publish to JSR #5381

Open
Open

Description

@sakgoyal

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

Activity

  1. darrachequesne commented on Sep 29, 2026

    @darrachequesne
    Member

    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.

  2. sakgoyal commented on Sep 29, 2026

    @sakgoyal
    Author

    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?

  3. darrachequesne commented on Oct 6, 2026

    @darrachequesne
    Member

    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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Type

    No type

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions