Skip to content
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

Correct stack traces using source-map-support #54

Open
tomchambers2 opened this issue Apr 20, 2020 · 1 comment
Open

Correct stack traces using source-map-support #54

tomchambers2 opened this issue Apr 20, 2020 · 1 comment

Comments

@tomchambers2
Copy link

Is it possible to use source-map-support to have stack traces refer to the uncompiled source? It's quite tricky seeing where errors in tests have come from at present.

@cmawhorter
Copy link

i've been adding ts-mocha -r source-map-support/register which gets stack traces mostly working.

but i've noticed some of the low-line-number (e.g. line 8) refer to something that i'm assuming typescript injects. the rest of the line numbers are accurate though so it hasn't been a problem to just ignore those

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants