-
Notifications
You must be signed in to change notification settings - Fork 968
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
Is this project abandoned? #81
Comments
+1 |
2 similar comments
+1 |
+1 |
The NPM name "reconnecting-websocket" is taken by https://github.com/pladaria/reconnecting-websocket. Could this be a reason for joewalnes loosing interest? Anyway, the other repo (pladaria) seems to be as fine as this one but more alive. |
There are some alternatives such as: |
If anyone is interested in maintaining this in the long run, please let me know. |
Out of the three libraries mentioned, only https://github.com/pladaria/reconnecting-websocket mentioned by msageryd seems to be actively maintained. |
@Parziphal: both libraries have commits dating from less than 4 months ago, but they're also browser-specific. @pladaria's library is "Multiplatform (Web, ServiceWorkers, Node.js, React Native)" but the last commit is from Oct 2017 and are three outstanding PRs. @joewalnes: looks like @pladaria is already maintaining this module, and since he has the npm package name, it would be really great to merge this deprecation notice PR into this repo, because a lot of links out there point to the repo (e.g. the accepted answer on StackOverflow for NodeJS Websocket how to reconnect when server restarts). |
I'm looking for a websocket library just like this and at first glance it looked popular, issues are being ignored and there haven't been and pushes in almost a year.
Should I look elsewhere if I have no interest in "fixing it myself" if something goes wrong under the hood?
Thanks!
The text was updated successfully, but these errors were encountered: