Inject Websocket into component

I’m submitting a…

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

Current behavior

Adding these lines:

@WebSocketServer()
public socketServer: SocketIO.Server;

Results in this.socketServer being null in Components.

It would be awesome if one could get the native web socket server from everywhere. So I do not need to create a Gateway everytime I want to emit a simple message.

Expected behavior

Attribute is not null.

Minimal reproduction of the problem with instructions

@Component()
export class SocketService {
    // Only connections that are correctly authenticated get into this array
    protected authenticatedConnections: Array<SocketConnection> = [];

    // this is the SocketIO server (can be used for emit etc.)
    @WebSocketServer()
    public socketServer: SocketIO.Server;
}

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

Environment

Nest version: 4.6.7

 
For Tooling issues:
- Node version: 8  
- Platform:  

Others:

[shekohex]

I was having the same issue, but i had to inject it in one gateway, that gateway dose not do anything, you can think of it as wrapper around the underlying socket server, and then i used it as a dependency in another gateways. Idk if this the only way to do this, but it works 😃

[kamilmysliwiec]

Honestly, it’s not that easy. What if someone uses multiple gateways at the same time? IMO, you should inject a gateway to the component instead and pick up the server then.