I’m submitting a…

[ ] Regression 
[ x ] Bug report
[ ] Feature request
[ ] Documentation issue or request
[ ] Support request => Please do not submit support request here, instead post your question on Stack Overflow.

Current behavior

Within my app, I was initially managing socket connection from only one file. Everything was working great.

Then, I decided to start some code refactoring and split this file in 2: One for users, one for orders.

@WebSocketGateway({ namespace: 'users' })
export class UsersService implements OnGatewayDisconnect {
  ...
}

and

@WebSocketGateway({ namespace: 'orders' })
export class OrdersService implements OnGatewayConnection {
  ...
}

As soon as I do that, I end up with an error displayed in the frontend: WebSocket connection to 'ws://localhost:3000/socket.io/?EIO=3&transport=websocket&sid=some-sid' failed: Error during WebSocket handshake: Unexpected response code: 400

I can start my app with just the user part, and when I comment everything related to websockets within orders, it’s working.

Expected behavior

I’d like to be able to use multiple @WebSocketGateway for code organisation.

Minimal reproduction of the problem with instructions

Unfortunately I don’t have time to create a repro right now. So in order to reproduce, create a project with 2 @WebSocketGateway and see what’s happening in frontend side.

Just let me know if a repro would be super useful and I’ll do my best to help.

What is the motivation / use case for changing the behavior?

I think it’s a bug, but maybe it’s just something I haven’t understand with websockets? Also, I’ve been putting here some example with a namespace but it wasn’t working either without namespace.

Environment

Nest version: 4.2.2
 
For Tooling issues:
- Node version: 8.6.0
- Platform: Ubuntu 17.10, 64 bits

Others:

Yes! It’s my first project with Nest and also my first issue.
So I’m taking few lines to say thank you for this amazing project, I do feel very productive with it 😄

Congrats and keep up the good work 👏 👏 👏