-
Notifications
You must be signed in to change notification settings - Fork 136
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
The current state and the future of this library? #239
Comments
@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 |
Hmm, it doesn't give confidence. Thanks @anicioalexandre for pointing it out. |
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
<#239 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AELLKK7DJ7TTWE7B2UPTSWTZMTP55AVCNFSM6AAAAABKHNFNC6VHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZDEMZQGQYDSNBQHA>
.
You are receiving this because you are subscribed to this thread.Message
ID: ***@***.***>
|
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 |
Yes, the plain WebSocket e.g. |
No worries. |
@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. |
@robtaussig, I am completely fine with the state of the project being that it is running like a well-oiled steam machine. Regarding the second screenshot, you are right, it was my oversight. |
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:
The text was updated successfully, but these errors were encountered: