Skip to content

Support for Bun + Socket.io + Hono Integration (Works on Node.js, not Bun) #4127

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

Open
calebeaires opened this issue May 6, 2025 · 2 comments
Labels
enhancement New feature or request.

Comments

@calebeaires
Copy link

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

  • 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

@calebeaires calebeaires added the enhancement New feature or request. label May 6, 2025
@yusukebe
Copy link
Member

@calebeaires

I've never used Socket.io well. Can you share an example project?

@hunterwilhelm
Copy link

Possibly related to oven-sh/bun#10441

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
enhancement New feature or request.
Projects
None yet
Development

No branches or pull requests

3 participants