Closed mitar closed 4 years ago
This problem is less related to this plugin but rather to how Meteor is handling the code. You'll get a similar call-stack when your Meteor app crashes.
Just some ideas to get further on ... Does this only apply to client-side or also to server-side code? Would using this plugin already help you? https://www.npmjs.com/package/source-map-support
Generally Meteor is pretty good at mapping back to lines, even for exceptions it shows. So I am not sure where this is breaking here?
I think this is something MDG could give some insight how to do or how they are doing? cc @benjamn
I looked into it a bit more and found out that puppeteer (or also any other browser I've been looking into) does not apply source maps to the stack traces. https://github.com/GoogleChrome/puppeteer/issues/985
If you ask me, this looks like a browser related problem. Until now I was not really successful in applying the proposed solutions like https://github.com/novocaine/sourcemapped-stacktrace or https://github.com/evanw/node-source-map-support.
It would maybe the right place to ask Meteor to add support for this. Another way would be if you'd write a reporter yourself which prints out the native exception to the console so the browser transforms the stack.
Closing because it's off-topic for this package. This package just takes whatever the console of the browser reports and forwards it to the command-line. If the stack-trace is not how you'd like to have it, please report this on the repository of the meteor framework.
Assertion like this:
Is not very useful. Because of babel and my using of async code, there is no way to really discover which assert failed in the code from:
I would hope that this gets mapped to original source code locations.
I am using
meteortesting:mocha@1.0.1
.