Can Uberproto be removed in Crow v4 to support Hermes? #2493
jamesholcomb
started this conversation in
General
Replies: 2 comments 1 reply
-
|
Unfortunately not since it is technically a breaking change (documented here). |
Beta Was this translation helpful? Give feedback.
0 replies
-
|
I see...I suppose I could migrate client apps to v5 (staying at socket-io.client@2.3) for now. I did some prelim testing and it seems to be compatible with the v4.5 server. |
Beta Was this translation helpful? Give feedback.
1 reply
-
|
That is definitely an option. None of the communication APIs changed as long as you are using the same socket.io-client version as on the server. |
Beta Was this translation helpful? Give feedback.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
I would like to enable Hermes in react native apps using the v4 Crow client. This was reported in #2076.
Uberproto was removed in v5 Dove with this PR #2178
Is backporting the PR to v4 feasible @daffl? Or do the existing dependencies make this unworkable?
I do plan on eventually migrating client and server to v5, but this would be a nice stopgap.
Beta Was this translation helpful? Give feedback.
All reactions