Uncaught error does not display stack trace

[chrisbreiding]

Current behavior:

If an uncaught error occurs, in either app code or test code, Cypress displays the error message, but not its stack, which could be useful for debugging.

Desired behavior:

Cypress should always display the stack for uncaught errors.

Test code to reproduce

In your spec file:

setTimeout(() => {
  foo.bar()
})

// give the test time to run, so the run doesn't end before the error is caught
it('waits', () => {
  cy.wait(9999)
})

Versions

Cypress: 4.3.0

[cypress-bot]

The code for this is done in cypress-io/cypress#6965, but has yet to be released.
We'll update this issue and reference the changelog when it's released.

[cypress-bot]

Released in 4.4.0.

This comment thread has been locked. If you are still experiencing this issue after upgrading to
Cypress v4.4.0, please open a new issue.