Annoying stack trace in output

[papermana]

Every time I encounter any failure when testing with Jest, my console gets flooded with ridiculously long stack traces. They look like this. You can see in this example that there isn't even anything there which relates to my own files. It's just a hundred lines of internal Jest errors.

Is this a bug or an intended feature? (I don't really know how it could be useful, but maybe that's just me.) I know you can program your own template for test results but I don't really want to devote time to that kind of thing unless it's necessary.

[cpojer]

This absolutely sucks and happened because we changed everything about Jest around in 13.0. If you are brave, you can install jest@test which is currently a test release and should have this fixed – it will definitely be resolved in the next version of Jest but because we are making more large scale rewrites right now, I don't know exactly when we'll publish this version as stable.

(Closing because it's fixed on master)

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