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
Feature Request: cleaner stack traces #48
Comments
Could you tell me which version of RunJS you're using? |
I just made sure I was on 1.2.4, and now I'm seeing something different, which is that if I have an error with only one line of code, no error shows... ...but if all I do is add an extra blank line to the program, now exceptions show up: Also, not sure what the "unknown" part in those errors is supposed to indicate. The first snippet should say "ReferenceError" and the second one should say "SyntaxError". |
The missing error for one line of code is a simple, dumb bug in my code. I will have a fix in my next release. In my solution I will be dropping the "unknown: " part of the error and preserving the "SyntaxError: ". |
Hmmm... ok, that seems like a Babylon bug. I will confirm and file that. |
1.3.0 resolves the above issues apart from the Babylon bug. |
(Note: I have transpilation turned off. I know that feature would mess with this request significantly, and would require sourcemaps support to get right. So I'm only asking for the fix in non-transpiled mode at the moment.)
See this stack trace:
As you can see, most of that stack trace is entirely irrelevant to me, as it's stuff happening inside of RunJS (node, I guess?)... including the promise resolution, etc.
I know that the stack trace is not your doing, but it would be nice if you could edit its output to make it more friendly to read.
For example, this stack trace:
could maybe be truncated to just:
or even better, fixing the line/column numbers:
I know this is challenging to do, but it would be really nice to have at some point.
The text was updated successfully, but these errors were encountered: