You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I’d like to request support (or guidance) for integrating Socket.io with Hono when running on Bun. Currently, using Socket.io with Hono works seamlessly on Node.js, but the same approach does not function as expected on Bun.
Is your feature request related to a problem? Please describe.
Yes. When trying to use Socket.io with Hono on Bun, the server either fails to start, or WebSocket connections do not establish properly. This is a blocker for projects that want to use the performance of Bun with real-time features provided by Socket.io and the simplicity of Hono.
Describe the solution you’d like
An example of integrating Socket.io with Hono on Bun and/or If there are technical blockers in Bun or Hono, a roadmap or explanation would be helpful
Using other WebSocket libraries, but Socket.io is preferred for its features and ecosystem
Additional context
Node.js: Works fine with Socket.io and Hono
Bun: Fails to integrate with Socket.io and Hono
The text was updated successfully, but these errors were encountered:
What is the feature you are proposing?
Describe the feature request
I’d like to request support (or guidance) for integrating Socket.io with Hono when running on Bun. Currently, using Socket.io with Hono works seamlessly on Node.js, but the same approach does not function as expected on Bun.
Is your feature request related to a problem? Please describe.
Yes. When trying to use Socket.io with Hono on Bun, the server either fails to start, or WebSocket connections do not establish properly. This is a blocker for projects that want to use the performance of Bun with real-time features provided by Socket.io and the simplicity of Hono.
Describe the solution you’d like
Additional context
Node.js: Works fine with Socket.io and Hono
Bun: Fails to integrate with Socket.io and Hono
The text was updated successfully, but these errors were encountered: