Consider supporting a logErr option

[maxhallinan]

Is there any interest in adding a logErr option? logErr would be passed to loudRejection. I have a need to format error logs. The Meow way seems to be avoiding explicit catch but by doing so, I lose the ability to format the log.

[maxhallinan]

@sindresorhus sorry to bug you about this. Any thoughts?

[SamVerschueren]

I don't see any problem in using .catch in your CLI if you are in need of formatting the error.

[maxhallinan]

@SamVerschueren thanks for commenting. I agree that using .catch is not problematic in the sense that it's easy to do and it works. But by using .catch, I duplicate the (simple) logic encapsulated by loud-rejection. My usage is nearly identical to the .catch example in the loud-rejection docs.

The choice was made to delegate error handling to loud-rejection. loud-rejection anticipates the need for a custom logging function. Why wouldn't meow support this option? I opened this issue in case it's an unforeseen or unrecognized use-case.