Sourcemaps are broken for JavaScript files imported by TypeScript files

[jamietre]

• Issue

When running TypeScript tests, if an error occurs in a JavaScript dependency, the source map is not preserved; stack trace has line number in compiled code.

• Expected behavior

Source maps always work.

• Output from your debug log

none

• Link to a minimal repo that reproduces this issue

https://github.com/jamietre/jest-source-map-problem/tree/20b8c62b45d19ca241b181f994d3bd6d3527fe69

Possibly related issue:

jestjs/jest#5925

[felipeochoa]

I had the same issue, but fixed it using "disableSourceMapSupport": true as described in:
#340 (comment)

[jamietre]

This works for the this trivial case but didn't work for my more complex case. However with this change: jestjs/jest#5945

and disableSourceMapSupport all my problems seem to go away...

[kulshekhar]

@jamietre thanks for pointing that out. I'll wait for that change to be published and then check back on this issue

[SimenB]

Jest 23 is out with the fix

[GeeWee]

Can you confirm this issue is fixed in Jest 23? @SimenB ?

[SimenB]

no, just that the fix @jamietre said worked for them is released

[huafu]

This should have been fixed in latest version. If it's not the case, please re-open the issue ;-)

[jamietre]

@huafu I just updated to jest@23.6.0 and ts-jest@23.1.4 and everything seems to be working.

I had to change ts-jest config to "disableSourceMapSupport": false whereas before I had to have it set to true to work around the problem. So all seems good at this point.