Closed Eitol closed 2 years ago
To simplify our setups and to help prevent these incompatibilities in the future, it would be nice if we could just tell the plugin to supply no configuration options, that way cypress just uses the same default config file that it would if you were to run it from the CLI.
Additionally, it would be good if we could specify a specific config file to use, that way we can create separate configurations that use each of the config files that we might use in our build system.
I'm having the same problem. Just upgraded to Cypress 10 and got the same error => I can no longer run my tests.
Hi folks, Could you try this beta of the plugin with Cypress 10 support. Please report issues here if you find any Cypress Support Pro-3.2-EAP.zip .
I tried it and it worked like a charm - thanks!
Hi folks! I'm close to releasing a new version with full Cypress 10 support. Could you try this bundle: Cypress Support Pro-3.2-EAP-2.zip Now the configuration is evaluated in IDE and the plugin can use it's values to validate paths and make suggestions (the same as it does for Cypress 9 and below).
It worked for me. (Cypress 10.1.0; Ubuntu 22.04; Rubymine 2022.1.3)
THANK YOU!
Plugin 3.2 version has been released today with full support for Cypress 10