I did it, i've been testing this and my specs which got renamed to *.cy.js and the tests run fine

I reverted that back to index.js and that worked then all of a sudden

I m getting these issues when trying to

hey I just tried adding Cypress 10 to my project, went through the setup and it's saying my config (

cypress.config.ts

) is invalid because

ERR_REQUIRE_ESM

. My

package.json

has

{ type: "module" }

. Is there something I need to do to tell Cypress I'm using ESM?

I feel like I have a pretty typical typescript setup

Does this sound like the same issue reported here? https://github.com/cypress-io/cypress/issues/22038

it does

i'll see if i can add a minimal sample in a comment

thanks!

Hello

this was probably mentioned before but just in case not: it seems that updating the baseUrl in the config won't take effect until restarting cypress

noticed that too

Hey All, I was able to resolve the issues with our component test migration and wanted to share the root cause and solution. The issue was for next.js component tests using a standard webpack. When starting the component tests they would hang with the message "Cannot GET /__cypress/src/index.html" and in the terminal had a few errors for "Module not found". The cause of this was that the support/components.ts included an import for the commands.ts. However, within the ./commands.ts we were importing Percy and a few other packages. This caused webpack to fail compile due to not finding the modules for those imports. Simple solution was to remove the import of commands form component.ts and as a BP I plan to move the imports for Percy and other packages specific to our e2e tests into the support/e2e.ts

Can you create a GitHub issue for this? https://github.com/cypress-io/cypress/issues/new

Thanks for pointing that out! I've put in a fix here: https://github.com/cypress-io/cypress-documentation/pull/4545

Can you file an issue in the repo for this? https://github.com/cypress-io/cypress-docker-images/issues/new

In GitHub actions, Cypress trying to use old format config file. I have

cypress.config.ts

and there is no

cypress.json

in a codebase. https://github.com/laststance/nsx/runs/6714339952?check_suite_focus=true#step:6:129

Can I change cypress 10 back to a light color scheme? The contrast between my light pages on the right & the black left is a little blinding

Not currently. Someone else opened an issue around wanting a light mode if you want to add any comments there: https://github.com/cypress-io/cypress/issues/22035

Does cypress mock process now? I'm seeing issues where env variables are trying to be read (in third party libraries) because process is defined

Trying to figure out if it's something specific to my setup 🤔

Or maybe it always has but env isn’t being mocked?

with the release of 10.0.2 to address this issue:

Error [ERR_REQUIRE_ESM]: require() of ES Module cypress.config.js

https://github.com/cypress-io/cypress/issues/22038#issuecomment-1145433804 I am now having this issue:

TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts" for cypress.config.ts

https://github.com/cypress-io/cypress/issues/21997#issue-1256410391 just fyi because both got closed and locked but there may be more that needs fixing

issue filed: https://github.com/cypress-io/cypress-docker-images/issues/673

The 3 (or you could even say 4) pane setup shrinks the browser too much. Like way too much on a laptop. Can't find a way around it.

Cypress mocking process

are there some tags that i should put on this?

Hello All, I Have updated my cypress to 10.0.2 but its not working Would you please someone can help with it. Thanks

as explained in another channel, please provide full explanation:

it's not working

is far from being an explanation. What happened? What did you do to make it occur? What's the current behavior? What's your expectation?

The 3 or you could even say 4 pane setup