Skip to content
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

Add support for custom logger #2

Closed
iMacTia opened this issue Dec 7, 2020 · 3 comments
Closed

Add support for custom logger #2

iMacTia opened this issue Dec 7, 2020 · 3 comments
Labels

Comments

@iMacTia
Copy link

iMacTia commented Dec 7, 2020

In a Back End service application, chances are that there's already an existing logger tight to the logging system (e.g. Logstash and Kibana) that one might want to use.
However, at the moment, trace-unhandled only allows to log using console.error.
It would make sense to keep that as the default behaviour, while providing the possibility to override that and use a custom logger.

What do you think?

@grantila
Copy link
Owner

grantila commented Mar 3, 2021

That sounds very reasonable, I'll look into it.

@github-actions
Copy link

github-actions bot commented Mar 3, 2021

🎉 This issue has been resolved in version 2.0.0 🎉

The release is available on:

Your semantic-release bot 📦🚀

@mattiagiuffrida-st
Copy link

Thanks @grantila for the quick fix 🎉 !

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Projects
None yet
Development

No branches or pull requests

3 participants