-
Notifications
You must be signed in to change notification settings - Fork 1.8k
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
Error objects are not logged #1426
Comments
I have the same problem. I use winston-mongodb, and in 'meta' property in database I see level and error message, but not error object. |
+1 |
Same problem here. |
Error object gives undefined |
still not fixed 😕 |
Valid concerns! There is a nice workaround by @SamuelMaddox17 / @indexzero in #1338 , but we should do something so this works more out-of-the-box. Let's track this issue in #1338 since it's the same thing. Thanks all! |
Please tell us about your environment:
winston
version?winston@2
winston@3
node -v
outputs: v9.5.0What is the problem?
The following code does not log the Error object, but just:
I experimented with custom formatters:
which logs the Error message, but there's still no stack trace.
What do you expect to happen instead?
Coming from Winston@2, I'd expect this to log the Error object including a stack trace.
The text was updated successfully, but these errors were encountered: