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 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.
Example of correct type declaration:
pluginsFile: string | false
Test code to reproduce
// cypressScript.ts
import { run } from 'cypress';
const runConfig = {
config: {
pluginsFile: false,
}
}
run(runConfig);
Versions
Cypress 4.8.0
OS: macOS Catalina 10.15.3
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
falseto disable that options. The properties I have found that meet this criteria arefixturesFolder,supportFileandpluginsFile, 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:
falseshould 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