Weird types in middleware

[MalekD5]

When I try to use middleware socket.use(), for some reason it returns the incorrect types

when I log the req parameter, it returns a Socket object

I'm not sure if this is a result from my typescript setup. but I have to do this so typescript stops complaining

[darrachequesne]

Hi! Which kind of middleware are you using?

• at the namespace level?

io.use((socket, next) => {
  // ...
});

Reference: https://socket.io/docs/v4/server-api/#serverusefn

• or at the socket level?

io.on("connection", (socket) => {
  socket.use(([event, ...args], next) => {
    // ....
  });
});

Reference: https://socket.io/docs/v4/server-api/#socketusefn

[MalekD5]

Hi, as it turns out I was incorrectly inferring the types by using Socket type instead of Server type. This confusion was related to nestjs websocket package that was using the type any for the lifecycle hooks (afterInit to be precise) not realizing that the parameter was referring to a server rather than a client (Socket).

I think I should have been asking for support directly from nestjs rather than socket.io
My apologies.