-
-
Notifications
You must be signed in to change notification settings - Fork 534
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
reported stackframe provide wrong line number (on Windows) #1055
Comments
I hope you're going to publish the fix soon since this bug seems to be affecting Mocha Test Explorer (which uses stack traces to detect the test locations in the code). |
I should have time to publish a release on Saturday. Unfortunately I am swamped at work this week, so that's the soonest I will be able to work on Maybe @blakeembrey is able to publish a new release in the meantime? |
@hbenl @erossignon @rinick |
Expected Behavior
Expecting ts-node to report accurate stack frame, pointing to the original typescript file.
Steps to reproduce the problem
package.json
test.ts
( no tsconfig file necessary)
Minimal reproduction
$ npx [email protected] test1.ts
now run with older version
$ npx [email protected] test1.ts
observe the result
at c:\temp\tsnode-issue\test1.ts:9:9
incorrect with [email protected]where it should report
at c:\temp\tsnode-issue\test1.ts:8:9
'(correct with [email protected]In real production, the line number discrepancy can be large and annoying as it make it almost impossible to identify where the exception was raised ( annoying when doing TDD)
TypeStrong/ts-node-repros#3
Specifications
Bug can be reproduced on Windows from a DOS box,
cannot exhibit bug in WSL
The text was updated successfully, but these errors were encountered: