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
Line numbers in stack trace wrong (on Windows) #1058
Comments
@cspotcode absolutely! will close this. Duplicate of #1055 |
I can confirm that this works when using master. |
@jugglingthebits Thanks, I'm working on preparing a release to fix this. Unfortunately, I am swamped at work this week, so I think I'm going to publish as a different npm dist-tag so that people can install and test. Then when I get confirmation that it works, I'll promote the dist-tag to |
@cspotcode thanks you! I can test the update here if it helps. |
I can confirm that it works for me (on Windows) |
@cspotcode thank you for your efforts! |
Expected Behavior
I use ts-node to run an express app. An error handler catches exceptions. I expect line numbers to match the actual ones.
Actual Behavior
The line numbers don't match.
Steps to reproduce the problem
Minimal reproduction
When I run TypeStrong/ts-node-repros#4 locally on my Windows machine, I get different results compared to the Github Action result.
Github Action (correct):
Local machine (wrong):
On my machine, it reports line 4 to throw, as opposed to line 6 in the Github Action.
When I set
hookRequire = true
in the sourceMap setup, it starts reporting correct line numbers on my machine, too.Specifications
ts-node v8.10.1
node v12.17.0
compiler v3.9.3
Operating system and version: Windows 10
If Windows, are you using WSL or WSL2?: No
The text was updated successfully, but these errors were encountered: