As suggested in the ESM guidelines of Node.js it would be good to explicit the type of the module.

{
+  "type": "commonjs",
}

When starting Mumble with: mumble "mumble://user@server.tld" it does not connect to the server and says "This version of Mumble can't handle URLs for Mumble version 1.2.0"

"mumble://user@server.tld?version=1.4.0" also doesn't work.

Works in a new instance if another Mumble instance is already running.

Hey Crew,

Nice job on gocql, I'm a fan...

For my production services, I could use notification events (via callback or channel) when the gocql client disconnects and reconnects to/from Cassandra. This is useful for higher-level application logic (ie: invoke alarms, stop reading from a durable message queue, etc).

After looking through the code, it looks like the connection information is not p

Because in CliClient.resume() we don't account for the case, when there is an exception in one of the async processing stages:

void resume() {
	...
	try {
		client.startAsync(state -> {
			printer.ifPresent(p -> p.print(state));
			if (!options.shouldSeedAfterDownloaded() && state.getPiecesRemaining() == 0) {
				runtime.shutdown();
			}
		}, 1000); // <-- CompletableFuture.w