The current state and the future of this library?

robtaussig / react-use-websocket

React Hook for WebSocket communication

MIT License

1.63k stars 135 forks source link

The current state and the future of this library? #239

Open nemonemi opened 4 months ago

nemonemi commented 4 months ago

Hi guys, My team is evaluating libraries for handling WebSockets.

Is this library alive? Are there any planned updates?

Also, docs seem to be a bit out of sync:

anicioalexandre commented 4 months ago

@nemonemi can't say about the future of the lib, but you can find its releases here https://www.npmjs.com/package/react-use-websocket?activeTab=versions

nemonemi commented 4 months ago

Hmm, it doesn't give confidence.

Thanks @anicioalexandre for pointing it out.

robtaussig commented 4 months ago

What about that screenshot makes you think the docs are out of sync?

Sent from mobile. Please forgive brevity.

On Tue, Jul 16, 2024 at 5:14 AM Nemanja Milosavljevic < @.***> wrote:

Hmm, it doesn't give confidence.

Thanks @anicioalexandre https://github.com/anicioalexandre for pointing it out.

— Reply to this email directly, view it on GitHub https://github.com/robtaussig/react-use-websocket/issues/239#issuecomment-2230409408, or unsubscribe https://github.com/notifications/unsubscribe-auth/AELLKK7DJ7TTWE7B2UPTSWTZMTP55AVCNFSM6AAAAABKHNFNC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZQGQYDSNBQHA . You are receiving this because you are subscribed to this thread.Message ID: @.***>

anicioalexandre commented 4 months ago

I've been using the lib without any problems so far... Looks like it's being maintained, they just don't sync it too much on the github repo :D @nemonemi did you find any alternative?

nemonemi commented 3 months ago

Yes, the plain WebSocket e.g. new WebSocket('websocketBackendUrl', 'graphql-transport-ws').

nemonemi commented 3 months ago

What about that screenshot makes you think the docs are out of sync? - Sent from mobile. Please forgive brevity.

No worries. Well, the first one states that the last "release" was 2 years ago. The second one says "Version 4.0.0, please install version 3.0.0". This, to me, seemed like, at least, a typo.

robtaussig commented 3 months ago

@nemonemi to be honest, I’m not clear on what constitutes a release from GitHub’s perspective, but if you look at npm, I’ve released more recently than 2022. 3.0.0 was from a PR by a contributor — they documented it a bit differently such that it did not get added to the README, but did get captured by GitHub releases.

The second screenshot is meant to convey that 4.0.0 now requires you to use React 18 — if your project is React 17, then you should stick to/install 3.0.0.

nemonemi commented 3 months ago

@robtaussig, I am completely fine with the state of the project being that it is running like a well-oiled steam machine. I simply pointed out things that stuck out when I was evaluating it. Usually, the releases on the GitHub repo would reflect the actual list of changes, and the latest version on the releases screen, or there would be a RELEASES.md file or some such way of seeing the latest state of releases and the change log.

Regarding the second screenshot, you are right, it was my oversight. Happy to close it.