PeelTechnologies/react-native-tcp

Is this library safe to use?

Opened this issue · 7 comments

albertkim commented

This is for all the people who have used this package in their projects - would you recommend others to try it out?

  • The last commit was pretty much a year ago
  • There are 24 issues
  • There are 8 pull requests
  • React Native moves super quickly

I feel skeptical using this, but if someone can vouch that it works for its intended use case (maybe with just a few edge cases not working), that would be awesome. Otherwise, this issue can be a warning to developers wanting to save themselves a headache.

beau6183 commented

I wish I could vouch for it. I'm doing a prototype with it right now and cannot send more than a single message from server to client before socket.write('...') stops doing anything.

jmceara commented

The problem is that there is no alternative for pure-tcp library :(
I'm looking for alternatives too.

beau6183 commented

@jmceara This fixes the issue that I was complaining about. So far it's been pretty solid.
#87

schontz commented

@aprock Is this repo being maintained? Or has this been abandoned?

pstanton commented

looks abandoned, however still the best out there. someone needs to fork and maintain, but who!

acb commented

I found a fork here: https://github.com/sausaw/react-native-tcp

It looks like they've pulled in some/most of the PRs here, including the fix mentioned above.

Can't vouch for that maintainer, it seems like the safest method is to make your own fork and pull the things that you want. Not great.

  • 👍2
phillbaker commented

Hi all. I recently started helping to maintain this library and have released a new version to NPM - maintenance has moved to a fork: https://github.com/aprock/react-native-tcp. Any PRs there would be welcome!

  • 👍2