How are errors actually supposed to be handled?

[jstasiak]

There's this example in the readme[1]:

import { createClient } from "redis";

const client = await createClient()
  .on("error", (err) => console.log("Redis Client Error", err))
  .connect();

await client.set("key", "value");
const value = await client.get("key");
client.destroy();

additionaly the document says

⚠️ You MUST listen to error events. If a client doesn't have at least one error listener registered and an error occurs, that error will be thrown and the Node.js process will exit. See the > EventEmitter docs for more details.

My question is: what should the listener actually do?

Surely I shouldn't just ignore the errors (logging doesn't count as doing anything in my books)?

What is the right way to handle this in production code? What kinds of errors can we even get there?

[1] https://github.com/redis/node-redis/blob/bcf8d2b36b6fbcd5a0a10b2ce5b39eaf1994f473/README.md#basic-example

[nkaradzhov]

The error event listener requirement is a Node.js EventEmitter thing - without it, errors crash your process. The client already handles reconnection automatically, so for most applications, logging + optional monitoring integration is actually a reasonable approach. The errors you see there are network-level issues that the client is already working to recover from.

If you need stricter behavior, use reconnectStrategy to control when to give up