-
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
Exception handling not working with Node 9.8 #1312
Comments
Can you upgrade to the latest By that I mean bugs that are |
This isn't working with LTS either. // using Console transport and format simple
const err = new Error('some-error')
log.error(err) // -> error: undefined |
@mikeandtherest going to close this as a duplicate of #1263. I was able to get that sample working with no issue on There could be some nuance in the behavior your use cases is exhibiting, but we need a MWE (minimum working example) such as the one provided in #1263 to triage further. Feel free to reopen if you have time to create one. |
Please tell us about your environment:
Both [email protected] and [email protected]
Node 9.8, 10.0, 10.1
Win 10 Pro
Javascript (ES6)
What is the problem?
It seems that with the latest versions of Node (9.8+), the uncaught exceptions are not handled
properly anymore by winston. That is, they are written to file but the exception message and stack
trace is still output to the console, as if the exception was not handled at all.
What do you expect to happen instead?
I tested this on another PC with Node 8.8.1, and there the exceptions are logged to the file
and the console is clean upon exit, as it should.
Other information
If I use also a transport Console for the exception handler, I get it logged to the console properly, but after it I also get the ugly node js uncaught exception message.
Btw, I started with [email protected] and then I switched to @3.0.0-rc5, but it didn't help since it was the same.
The text was updated successfully, but these errors were encountered: