Do not filter out stack trace for unhandled rejections

🐛 Bug Report

In strict unhandled rejections mode (https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode), the stack trace of unhandled rejection is not displayed in the console. This mode is default in Node.js 15.

To Reproduce

Steps to reproduce the behavior:

1. Run a test with an unhandled rejection, for example:

test("foo", () => {
  Promise.reject(new Error());
  expect(1).toBe(1);
});

1. The output is:

 RUNS  ./index.test.js
node:internal/process/promises:218
          triggerUncaughtException(err, true /* fromPromise */);
          ^

[UnhandledPromiseRejection: This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). The promise rejected with the reason "Error".] {
  code: 'ERR_UNHANDLED_REJECTION'
}

Expected behavior

The stack trace is displayed in the console.

Link to repl or repo (highly encouraged)

https://github.com/vkrol/jest-unhandled-rejection-stack-trace

envinfo

  System:
    OS: Windows 10 10.0.19042
    CPU: (8) x64 Intel(R) Core(TM) i7-6700 CPU @ 3.40GHz
  Binaries:
    Node: 15.1.0 - ~\scoop\apps\nodejs\current\node.EXE
    Yarn: 1.22.5 - ~\scoop\apps\yarn\current\Yarn\bin\yarn.CMD
    npm: 7.0.8 - ~\scoop\apps\nodejs\current\npm.CMD
  npmPackages:
    jest: 26.6.3 => 26.6.3

[justsml]

This is such a frustrating default behavior. Usually I can quickly figure out the location of the error, but today I’ve been working on the wrong area of my app.

Turns out the bug wasn’t caused by my code changes, but an upgraded dependency in unrelated code…

I had to use VS Code debugger to trap the error. It was pretty frustrating to find all the line number details I’d expect were there. They were simply dropped by node+jest’s output.

Is there a way to let users know the risk of using NODE_OPTIONS="--unhandled-rejections=strict" ?

Or is there a node.js option to make the crash behavior less user-hostile?

[LvChengbin]

Currently, you can just use NODE_OPTIONS=--unhandled-rejections=warn yarn test to resolve this problem.