When command dispatched by event handler fails, application dies

[johanbook]

When a command handler is dispatched from an event handler, and there is an unexpected exception on the command handler, the application will print the error

api            |
api            | /app/src/features/profiles/application/handlers/command-handlers/create-profile.handler.ts:33
api            |     throw new Error("this was an error");
api            |           ^
api            | Error: this was an error
api            |     at CreateProfileHandler.execute (/app/src/features/profiles/application/handlers/command-handlers/create-profile.handler.ts:33:11)
api            |     at processTicksAndRejections (node:internal/process/task_queues:95:5)

and stop.

This should be fixed, but it should also be detected via the infrastructure that pings the application via the health endpoints and the application should then be restarted.

[johanbook]

Similar issue as in nestjs/cqrs#1428. See also nestjs/cqrs#409. I have implemented subscriber for unexpected errors

I have bumped Nestjs to v10 and Nodejs to v20

[johanbook]

Opened nestjs/cqrs#1485