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
console.error(error.stack) does not display clickable stack traces. #811
Comments
This makes it easy to browser the files in devtools, see electron/electron#811.
Fixed with atom/node@8c26bda. |
Implementing this requires setting the internal representing filename to However this causes troubles when throwing an exception from We can work around this by either patching CoffeeScript or making necessary node APIs recognize |
Just putting it out there. I would have liked this 🌹 Doesn't mean it has to be done |
In Chrome, calling
console.error(error.stack)
results in a clickable calls in the stack trace. In atom-shell the stack trace isn't clickable if the error is caught and displayed this way.The code that generated this behavior can be found at https://github.com/probablycorey/atom-shell/compare/stack-bug
The text was updated successfully, but these errors were encountered: