No stack traces in `cypress run` and inconsistent from `cypress open`

• Operating System: OSX
• Cypress Version: 0.20.1
• Browser Version: 61.0.3163.100 (Official Build) (64-bit)

Is this a Feature or Bug?

Bug

Current behavior:

Using a Nuxt app and cypress run from the command line, the tests linked below show an Uncaught SyntaxError: Unexpected identifier with no stack trace, but work perfectly when using cypress open

Commenting out cy.visit seems to fix the error, but obviously the tests still fail which suggest to me it’s an error when processing the page however I don’t know how to find out any further than that without any clues.

Desired behavior:

The behaviour in open and run should be the same, but also primarily there should be stack traces to debug syntax errors.

How to reproduce:

Basic versions of the tests and results shown here: https://gist.github.com/samtgarson/dadd2d760c7701c8ab0c2ee8e89bd9a4

I can’t share the entire repo but if you have no idea where to begin I can try to recreate with a basic example.

Test code:

Above

Additional Info (images, stack traces, etc)

Above

[jennifer-shehane]

Have you tried running the tests with cypress open and selecting the Electron browser? We use Electron to run headlessly in cypress run. I’m wondering if the error would show up there.

[brian-mann]

Released in 2.0.0.