Closed luandro closed 5 years ago
Hey Luandro, thanks.
To be honest, everywhere I use patch-package
, I should replace it with a fork of the package, or a proper PR. I'll remember to do this but if you're in a hurry you can try making forks too
Hey @staltz,
Began trying to replace the patches for forks using @luandro/react-native-ssb-shims to publish the tests so far.
With just a little tweaking I was able to build mmmmm, which is a good starting point to understand how everything comes together, and how. Although MMMMM I built doesn't find peers in my local network. Maybe conflicting something with apk version I had installed before?
Hey @luandro that's good news! React-native-fs could be a newer version, we just need to check if it's API had new breaking changes.
And about multiserver, we shouldn't fork it, the patch was just an ugly hack. We should fork react-native-tcp which should support an API that is compatible with the official tcp
. The reason why I changed multiserver was to make it's usage of tcp API match the (wrong) tcp API in react-native-tcp
Ok, sorry I'm still not familiar with ssb inner workings just yet, but I'll try to investigate thru MMMMM code and see if I can help with the appropriate forks. Cheers!
I could also do it, but it would be great to have some help. Keep on asking if you need any help!
This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.
Worth mentioning that patch-package needs npm(>=5) or
yarn
for it to work correctly. But this occurs even using npm5.6.0
.Problem with
react-native-os
:patch-package
is not found:sh: patch-package: command not found
Tried fixing (2) by installing
patch-package
separately. It lets the module be installed, by when running the project I get an error that seems related toreact-native-fs
:Have tried installing
react-native-fs
separately but that just messes everything up, like reported in this issue.