Subscriptions-transport-ws: Maintenance: No releases since 03/19

[anilanar]

What's the status of this package?

• Issues/PRs are seemingly piling up, most of which are lacking further comments/labels etc.
• Very little activity from maintainers.
• Last release was in March 2019, with no commits since then except auto dependency update PRs.

[sneakyness]

Thanks for drawing attention to this, was wondering why all of the links are broken and nothing seems to make sense. Would not recommend using this to build anything important until this is resolved

[anilanar]

I'm building a generic subscription transport solution that can be integrated with any IO layer. Then maybe I can help maintain this one too.

[sneakyness]

Are you aware of any viable js alternatives otherwise? I haven't even started looking but this is one of those camel-crushing straws that has me thinking "wow, react native and it's ecosystem are trash, time to throw this away and write it in swift"

[anilanar]

No, that's why I'm rolling my own.

This solution seems to work for most people even though it's not maintained.
I roll my own because I must use SocketIO and not raw websocket.

[mattkrick]

shameless plug:

• https://github.com/mattkrick/trebuchet-client is used to manage the transport and connectivity logic. Supports WebSockets or SSE.
• https://github.com/mattkrick/graphql-trebuchet-client is used to manage the GraphQL communication protocol

Used in production for a couple years now: https://github.com/parabolinc/parabol

I broke it into 2 because a WebSocket should be able to do more than just talk GraphQL (e.g. WebRTC signal server, binary data, etc). How you implement the server is up to you, but you can use the reference implementation as an example.