-
-
Notifications
You must be signed in to change notification settings - Fork 11
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
Source map paths are wrong #1
Comments
This commit fixes the problem for me: andrew0@9164973. I would submit a PR but I'm not sure what to do with the snapshot tests, since it makes it so the source maps have an absolute path for the |
Good find. I can fix up the snapshots easily enough to keep absolute paths out. (Tap will automatically prevent cwd in snapshots by default, but other paths can be a problem.) |
Found this issue looking for at source map support for Node.js Test Runner.
This is a known limitation of the Node.js test runner. It causes the code coverage reporting to break. |
I tried using this library but ran into some issues because the stack traces seem to be wrong. I put up a small repro here but it's really basic, just runs a script that prints a stack trace:
When I run this with
node --import=tsimp/import src/main.ts
, I get this:When I build the TypeScript code with tsc and run it with
node --enable-source-maps dist/main.js
, I get this:With
tsimp
, the current directory seems to be removed from the file where the error is thrown (/private/tmp/src/main.ts
when it should be/private/tmp/tsimp-repro/src/main.ts
).The text was updated successfully, but these errors were encountered: