Have Jests console respect sourcemaps.

[GeeWee]

Do you want to request a feature or report a bug? Feature,

What is the current behavior?
When transpiling code from other languages (e.g. typescript) to Jest, the line numbers printed in the terminal are off. It'd be nice if Jest would respect sourcemaps and print the actual line numbers.

An example of this: kulshekhar/ts-jest#283

[cpojer]

See #3458

[GeeWee]

Sorry for reopening, but source map support only works for stack traces, and not console statements (it is the same approach we use in ts-jest)

[CoreyCole]

I was still having this issue today (jest v24.8.0 and ts-jest 24.0.2). My console log statements were reporting incorrect line numbers. Running jest with --no-cache fixed the issue for me:

jest --no-cache --runTestsByPath ./__tests__/e2e/*_test.ts

Sorry to bump this issue, but hopefully helpful to anyone googling around...

Related to kulshekhar/ts-jest#283 and evanw/node-source-map-support#186

[SimenB]

This has been fixed in Jest for quite some time (since #5594 which was released in 22.4.1 18 months ago). Dunno what ts-jest does, but this repo is not really the place to discuss it 🙂 As long as correct source maps are provided by the transformer (and nothing funky is done to console.log and friends) it should just work ™

[github-actions]

This issue has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.
Please note this issue tracker is not a help forum. We recommend using StackOverflow or our discord channel for questions.