If reconnections are disabled, the FluentClient constructor can throw an unhandledPromiseRejection, which isn't ideal.
Thinking about it, we're not doing a great job of supporting reconnectDisabled, since we should also expose the events on the socket so that the user can decide to reconnect. For now this isn't used, so we can probably come back to it, just like the server :)
If reconnections are disabled, the FluentClient constructor can throw an unhandledPromiseRejection, which isn't ideal.
Thinking about it, we're not doing a great job of supporting reconnectDisabled, since we should also expose the events on the socket so that the user can decide to reconnect. For now this isn't used, so we can probably come back to it, just like the server :)