Alex
I think I found the cause of this bug.This is because during the execution of the middleware, the socket has not yet been added to the adapter's namespace. ```js const...
for the example below, we don't use uWebsocketjs this time, even if the socket has not yet been added to the adapter's namespace, it also works well. ```js const {...
I created a fix but don't know if it will have any other impacts, would appreciate if you could check it.
It seems that [email protected] depends on engine.io version ~6.5.2. However, the highest version in the 6.5.x range is 6.5.5, and this version of Type Transport does not include webtransport. Maybe...
yes, the socket.io itself need to update the version of engine.io