Brian Mann

Sorry, I totally missed this comment! I just finished implementing a module generator and it's very similar to yours. I like how you've added the ability to specify the templating...

Can you just get rid of the `race` altogether and just just `npm start` and use `wait-on` ??

It would match better what we actually recommend to our users (and be a lot less confusing) https://docs.cypress.io/guides/guides/continuous-integration.html#Booting-Your-Server

Why do we need a single command? You'll just background the server process.

This likely has to do with `electron` and not necessarily Cypress. It may be easier opening an issue over there https://github.com/electron/electron/issues and ask about what it will take to build...

If you're testing the behavior of an element coming into focus, or you're testing things like styles you can just focus the element directly. ``` javascript cy.get("input").focus() ``` What this...

@scottschafer that fires the event, but the browser will not perform the default action such as moving the tab focus to the next focusable element

I actually believe this issue will be fixed by this PR which will be merged in the next patch release: https://github.com/cypress-io/cypress/pull/4406

It was an oversight / bug that we were still taking snapshots when a single test even though `numSnapshotsKeptInMemory` was 0 - so it's expected that the memory would grow...

Closing this issue as duplicate because I'm **very** confident this is describing the same behavior as https://github.com/cypress-io/cypress/issues/4104