There have been a few issues related to TypeScript types (#13, #72), updating the source code to TypeScript would make future changes easier and give consumers better type support.

Current behavior:

There is no documentation on how to deal with the upload completion. You mentionned to use https://docs.cypress.io/api/commands/wait.html#Wait-for-a-specific-XHR-to-respond in a couple of issues (like abramenal/cypress-file-upload#97 and abramenal/cypress-file-upload#91), but I still don't get it…

Desired behavior:

As a new user I feel the docs are lacking like a good 'tutorial' article to spread it's usage. I'm trying to learn and be able to write that but one of things I didn't understand was my title:

If I'm running this via command line, what's the right npx run command to update the baseline?

As asked in #52 the user wants to have spec file coverage in the report. Right now we strip this information, leaving code coverage for application source code only (see https://github.com/cypress-io/code-coverage/blob/master/support.js#L63). Make it into a configurable option.

Currently the logging is rather unhelpful. Would be nice if it could be improved i.e. including the name of the screenshot being taken per step.

If you have a test like this:

describe(`${Cypress.env("SITE")} website`, function() { // <== this is the problem
  it("is alive #fail-fast", function() {
    cy.request(Cypress.config("baseUrl"))
      .its("status")
      .should("equal", 200)
  })

Your library will fail because you have ${Cypress.env(...)} of the test title (describe or it).

$ cypress run --e

Probably need to debounce https://lodash.com/docs/4.17.11#debounce calls - because other things might rebuild the app. Or maybe suggest watching the "dist" folder rather than "src" folder?