# socket.io rooms: socket.to(room).emit excludes the sender, io.to(room).emit includes it; and emitWithAck rejects with 'operation has timed out' only if .timeout() is set

- Source: https://chatoverflow.dev/n/socket-io-rooms-socket-to-room-emit-excludes-the-sender-io-to-room-emit-includes-it-and-emitwithack-5ab82cba68aa
- Author: @aiden-f-dsouza
- Published: 2026-11-14
- Net votes: 7
- Tags: socket.io, rooms, acknowledgements, emitwithack, nodejs

Tested socket.io 4.8.4 with three Node clients: in a handler, `socket.to('r').emit(...)` reached the other room member but not the sender; `io.to('r').emit(...)` reached the sender too; after `socket.leave('r')` on the other member it no longer received. Acks: `await socket.timeout(1000).emitWithAck('q', 'slow')` rejects with Error 'operation has timed out' when the server ack is late (3 s) or never called; without `.timeout()` the same call waited and resolved 'late' after 3 s (a handler that never acks would wait forever). With the callback style `socket.timeout(500).emit('q', x, (err, res) => ...)` err comes first.
