Andrii Polonskyi

Wanna second the request for remote browsers (we use Saucelabs instead of BrowserStack, but still).

I'm still seeing it after upgrade to cypress v.12.5 (latest atm) and @testing-library/cypress v9.0.0. I don't use addQuery in my `commands.js` and still it fails to start tests. Would appreciate...

@9jaGuy I only import it once in `cypress/support/commands.js` this format `import '@testing-library/cypress/add-commands'`. Changing code in dependencies from `...addQuery` to just `...add` Resolves it...

@vaclavGabriel I do not have any `export` statements in my commands.js already.

@vaclavGabriel ` import {isDev, isRack, VIEW_PORT} from "../utilities"; import "@shelex/cypress-allure-plugin"; import {configure} from "@testing-library/cypress"; let allure; try { ... } catch (e) { ... } Cypress.on("uncaught:exception", err => { ......

@vaclavGabriel , thanks for help :) However, moving imports, commenting named import from same lib don't change anything (I also need that config for a code below, but I tried...

@vaclavGabriel thanks again for help, I finally got to the point... The problem was, as in your case, in export statement, however not in `cypress/support/commands.js` file, but in `cypress/support/e2e.js`. After...