New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Consider supporting a logErr
option
#59
Comments
@sindresorhus sorry to bug you about this. Any thoughts? |
I don't see any problem in using |
@SamVerschueren thanks for commenting. I agree that using 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. |
Is there any interest in adding a
logErr
option?logErr
would be passed toloudRejection
. I have a need to format error logs. The Meow way seems to be avoiding explicitcatch
but by doing so, I lose the ability to format the log.The text was updated successfully, but these errors were encountered: