You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When running Cypress through a script made in TypeScript, there are conflicts with the current Type Definitions with the actual configs supported.
There are some configs that accept both strings (path to a file / folder) or false to disable that options. The properties I have found that meet this criteria are fixturesFolder, supportFile and pluginsFile, but there could be more.
The type declarations for this config properties accept only strings as values, as seen here.
Screenshot of error thrown in VSCode:
Desired behavior:
false should be a valid value for this mentioned configs.
The code for this is done in cypress-io/cypress#7674, but has yet to be released.
We'll update this issue and reference the changelog when it's released.
Current behavior:
When running Cypress through a script made in TypeScript, there are conflicts with the current Type Definitions with the actual configs supported.
There are some configs that accept both strings (path to a file / folder) or
false
to disable that options. The properties I have found that meet this criteria arefixturesFolder
,supportFile
andpluginsFile
, but there could be more.The type declarations for this config properties accept only
string
s as values, as seen here.Screenshot of error thrown in VSCode:

Desired behavior:
false
should be a valid value for this mentioned configs.Example of correct type declaration:
Test code to reproduce
Versions
Cypress 4.8.0
OS: macOS Catalina 10.15.3
The text was updated successfully, but these errors were encountered: