Bun with socket.io

[N0N1m3]

Starting with version 4.4.0, a Socket.IO server can now bind to a µWebSockets.js server.

const { App } = require("uWebSockets.js");
const { Server } = require("socket.io");

const app = new App();
const io = new Server();

io.attachApp(app);

io.on("connection", (socket) => {
  // ...
});

app.listen(3000, (token) => {
  if (!token) {
    console.warn("port already in use");
  }
});

As written in the Readme: The HTTP server and server-side websockets are based on uWebSockets.

So, is there any way to port this to the capabilities of bun?

P.S. Socket.io article

[amytimed]

This is the main thing stopping me from using Bun at the moment, would love to see it.

[jhwheeler]

Does socket.io work with Bun if you use the default ws instead of a µWebSockets.js server?

[Jarred-Sumner]

socket.io does work with the default ws and internally ws in Bun actually uses uWebSockets so there's no need to use the uWebSockets backend (even if the uWebSockets.js backend did work in Bun, which it does not)

[itsfuad]

How to work with socket.io in Bun?

I need to run socket.io + Hono api server in the same port. In nodejs we can use binding or just pass the http.creatServer() instance to the socket.io's server constructor. But looks like there are issues. If not, please show example.

[hepiska]

i try with uWebSockets that already default by elisyajs but seems not working for pub sub usecase

[LeulAria]

@itsfuad have you found any example ?

[rgillan]

Unless you need the fallback (non ws) support in socket.io it is well worthwhile refactoring your application to use the native Bun websockets directly (Bun.serve etc.). The underlying uWebsockets implementation in our experience will significantly perform better than ws, websocket and socket.io in nodejs implementations (indeed it was the reason we first started looking at Bun). The pub/sub process works as well out of the box if you follow the Bun docs.