Open anorsich opened 5 years ago
@anorsich As far as I understand the problem has appeared because Node.js can't capture stack trace inside an asynchronous function. But in Node 12 there is a flag --async-stack-traces
in order to resolve the problem. But this flag should be used in the application itself.
We'll have to wait until 2019-10-22
for Node 12 to become LTS release, but this is certainly better than nothing :) @ezhivitsa
With node-mongo we usually get not very helpful stack trace, like this one:
How do we improve it to show where this error has happened?