[Bug]: Incomplete stack trace with async tests
ian-eulith opened this issue · comments
Ian Fisher commented
Version
29.1.1
Steps to reproduce
- Clone https://github.com/ian-eulith/jest-bug-repro
- Run
npm run test-js
- Run
npm run test-ts
Expected behavior
npm run test-ts
should print the same stack trace as npm run test-js
.
Actual behavior
The stack trace for npm run test-ts
only includes the line where the exception was thrown, plus one other unhelpful line.
Debug log
https://github.com/ian-eulith/jest-bug-repro/blob/main/ts-jest.log
Additional context
No response
Environment
System:
OS: macOS 13.4
CPU: (10) arm64 Apple M1 Max
Binaries:
Node: 18.16.0 - ~/.nvm/versions/node/v18.16.0/bin/node
npm: 9.7.1 - ~/.nvm/versions/node/v18.16.0/bin/npm
npmPackages:
jest: ^29.6.0 => 29.6.0