Error stacks are broken in Jest watch mode for source mapped files

[ArtemGovorov]

🐛 Bug Report

Error stacks for source mapped files are not always correctly reported in watch mode.

To Reproduce

• clone https://github.com/ArtemGovorov/jest-watch-mode-source-map-issue,
• run npm i,
• run npm test,
• touch the __tests__/a.spec.js file to get the test running,
• observe a correctly reported exception line,
• uncomment the second line of the test file to let Babel transform the import.
• save the file,
• observe an incorrectly reported exception line.

Expected behavior

The error stack should be correctly reported.

Link to repl or repo (highly encouraged)

https://github.com/ArtemGovorov/jest-watch-mode-source-map-issue

Run npx envinfo --preset jest

System:
    OS: macOS High Sierra 10.13.3
    CPU: x64 Intel(R) Xeon(R) W-2140B CPU @ 3.20GHz
  Binaries:
    Node: 9.6.1 - /usr/local/bin/node
    Yarn: 1.6.0 - ~/.yarn/bin/yarn
    npm: 6.1.0 - ~/.nvm/versions/node/v10.3.0/bin/npm
  npmPackages:
    jest: ^23.1.0 => 23.1.0

[SimenB]

Does this only happen in watch mode? If so, it's probably a caching bug

[ArtemGovorov]

It does happen only in watch mode. After restarting, the error is displayed correctly.

[SimenB]

@ArtemGovorov you've solved this upstream?

[SimenB]

Works correctly in Jest 27 and refreshing the lockfile, so calling this one fixed 🙂

[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.