-
Notifications
You must be signed in to change notification settings - Fork 845
New issue
Have a question about this project? # for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “#”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? # to your account
Using Socket.io with starscream 3.0.5 #1315
Comments
see #1309 |
@nuclearace sorry but I don't really understand the link of the comment Erik ... Could you please explain to us why we need to refer to that? Thanks! We don't want to use Socket.io 3 ... the issue with us is which version of socket.io will support starscream 3.0.5 ? |
@foward I'm currently working on a version that supports the newest Starscream version. Currently that PR only supports socket.io 3.0, but I'm going to go back and make it configurable for socket.io 2 and 3, since it shouldn't be too difficult. |
But beyond that, I'm not sure of a solution to use new starscream in an older socket.io version. |
Hi Erik, The question is, how can we install Socket.IO alongside the other library that we are using without having this Starscream version conflict? Thanks. |
@Abdullah-00 I'm not sure how to do that exactly, if it's even possible. |
Thanks Erik, Do you have some recommendations how to follow in this case? Much appreciated ! Regards |
Hi !
One project is using another library that uses startscream 3.0.5 so we wanted to use socket.io but is conflicting since socket.io latest uses the latest starscrem 3.1. Can we resolve this issue with an older version of Socket.io which uses starscream 3.0.5? Thanks!!!
The text was updated successfully, but these errors were encountered: