client

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

{
+  "type": "commonjs",
}

Context
Some devices only have mono-output at which point our positional audio feature can't work as it will require at least two channels to simulate any spatial effects.

Describe the feature you have in mind
A warning for anyone that has positional audio enabled but is using a mono device

Describe alternatives you've considered
None

Additional context
See e.g. #5220

The fetch spec does not allow async iterables as request body, we however allow it. The WHATWG doesn't seem to have anything against this per se.

Just needs to add a section in docs describing it.

whatwg/fetch#1291

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