Motivation

Currently, the agent seems to be usinghttps://github.com/googollee/go-socket.io which (besides being archived) implements the v1.4 ofSocket.IO client (it looks like it's compatible with 2.x as well for some reason).

Now, the current state of theJS library for communicating with the agent is pretty bad from multiple points of view (from a lack of documentation to a lack of types, to an annoying number of bugs, issues and gotchas in the current implementation).

Now, the issue is that in order to communicate with the agent we're forced to use the v2 implementation (again, because server v2 seems to be working somehow, otherwise we'd have to go v1.x - seehttps://socket.io/docs/v4/client-installation/#version-compatibility), and that means our hands are tied in various places:

• It doesn't have first class support for TypeScript
• It's on life support (last release -https://github.com/socketio/socket.io/releases/tag/2.5.0)
• It doesn't tree shake, which means the users have to download the whole bundle (which isn't small by any means -https://bundlephobia.com/package/socket.io-client@2.5.0)
  Additionally, the implementation is not a real websocket server as stated by [Socket.IO themselves]https://socket.io/docs/v4/#what-socketio-is-not) and that makes it incompatible with [WebSocket API]((https://developer.mozilla.org/en-US/docs/Web/API/WebSockets_API) forcing us to stay on v2 with the aforementioned drawbacks.

• What kind of change does this PR introduce?

Feature

• What is the current behavior?

• What is the new behavior?

• Does this PR introduce a breaking change?

• Other information: