Errors thrown inside setTimeout lose their stack trace

[matt-smarsh]

Describe the bug

Errors thrown in a setTimeout() block do not receive a stack trace when running in Node v16.16.0

Reproduction

https://stackblitz.com/edit/vitest-dev-vitest-m7mxed?file=test%2Fbasic.test.ts

System Info

System:
    OS: Windows 10 10.0.19044
    CPU: (12) x64 Intel(R) Core(TM) i7-10750H CPU @ 2.60GHz
    Memory: 3.98 GB / 15.75 GB
  Binaries:
    Node: 16.16.0 - C:\Program Files\nodejs\node.EXE
    npm: 8.14.0 - C:\Program Files\nodejs\npm.CMD
  Browsers:
    Edge: Spartan (44.19041.1266.0), Chromium (103.0.1264.77)
    Internet Explorer: 11.0.19041.1566
  npmPackages:
    vite: 3.0.4 => 3.0.4
    vitest: 0.20.3 => 0.20.3

Used Package Manager

npm

Validations

• Follow our Code of Conduct
• Read the Contributing Guidelines.
• Read the docs.
• Check that there isn't already an issue that reports the same bug to avoid creating a duplicate.
• Check that this is a concrete bug. For Q&A open a GitHub Discussion or join our Discord Chat Server.
• The provided reproduction is a minimal reproducible example of the bug.

[matt-smarsh]

Output from Node v16.16.0:

It would be desirable to have the stack trace:

I migrated a large test suite to remove the callback-style (done) => {} syntax to new Promise((done) => {}) and there's a test failing somewhere but I have no idea where because the error message is also a generic assertion error.

[sheremet-va]

Fixed in #1777