In Socket.IO v2, the Socket `query` option was sent when connecting to
a custom namespace (but not for the main namespace).

This was fixed in Socket.IO v3 ([1]), so this line is now useless.

[1]: https://socket.io/docs/v3/migrating-from-2-x-to-3-0/#Add-a-clear-distinction-between-the-Manager-query-option-and-the-Socket-query-option

Having type `Object` it was not possible to set values, e.g.:

```ts
if (!this.socket.io.opts.query) {
  this.socket.io.opts.query = {};
}
this.socket.io.opts.query.token = 'abc123';
```

Results in error:

> Element implicitly has an 'any' type because expression of type '"token"' can't be used to index type 'Object'.

…1440)

A polyfill for Node.js "process" was included in the final bundle.

Reference: https://webpack.js.org/configuration/node/

Previously, the following code:

```js
const socket1 = io({
  path: "/test1"
});
const socket2 = io({
  path: "/test2"
});
```

would result in one single Manager, with the "/test2" path being
silently ignored.

Two distinct Manager instances will now be created.

Related: #1225

Diff: 3.1.0...3.1.1

A previous change ([1], included in 3.0.5) broke support for web
workers, which threw "window is not defined" when importing the bundle
in a web worker.

Related: socketio/socket.io#3809

Reference: https://webpack.js.org/configuration/output/#outputglobalobject

[1]: 8c08c5d

Diff: socketio/engine.io-client@4.1.0...4.1.2

Diff: 3.1.1...3.1.2

This change is needed so the bundle can be used with:

```
<script type="module" src="xxxx/socket.io.js"></script>
```

Related:

- socketio/socket.io#3828
- 13b32b3
- 8c08c5d

Backported from master: 43613d1

Diff: 3.1.2...3.1.3