-
Notifications
You must be signed in to change notification settings - Fork 10.1k
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
Allow to bind socket.io to bun built in server. #4969
Comments
That's an interesting idea 👍 not sure how we can do this elegantly though. Food for thoughts:
|
will be nice if you guys expose it like a custom parser you guys had, but for a server. so we can easily intergrade it on anything. that has server express type like syntax. we have to expose those needed will be nice to finally use elysiajs(bun server/ws wrapper) with socket io compatible xD |
The current Deno solution is missing very useful features due to not being updated for 2 years. It would be very nice to have Deno/Bun/Winter etc engines/parsers to "attach" that don't need as much updating every time a new feature is added to the protocol/client. Maybe not a 4.x solution, but hope you all keep it in mind for 5.x. Company I work for is interested in the performance benefits of getting off Nodejs, but socket.io not having acks and connection recovery for Deno is currently a road block. |
Hi, need for a solution (Bun + Hono + Socket.IO). |
Is your feature request related to a problem? Please describe.
so I can use 1 port instead of two port separate. cant use uwebsocket.js due to bun already using it under the hood. it wont compile. and yes im aware that socket.io uses built in ws.. which is bun ws.. that is uwebsocket under the hood. but im only here for one port solution.
Describe the solution you'd like
i dont know
io.attachApp(bun here XD)
;Describe alternatives you've considered
nothing really i dont know how it works.. but you guys bind the uwebsocket server it might be same as bun too.. since it uses uwebsocket under the hood. all i need is so bun server and socket io has same port.
Additional context
nothing
The text was updated successfully, but these errors were encountered: