Multiple configs with cypress 10.0

[techshashank80]

I have multiple configs for different env in JSON format. then how we can achieve same thing with cypress 10. As per cypress migration video they did not talk about to migrate these config plans. any clue?

[reggZez]

I'm still working with multiple configs, helps me with more envs. What I did is that I have changed my exampleEnvConfig.json (lets say it's for test env) to exampleEnvConfig.js, and inside of it I have the same code as described in cypress.config.js (added some settings example here for e2e)

Later in the package.json I just specify in the script which config file should be opened when running that specific script, again lets say we are targeting test env (--config-file cypress/config/exampleEnvConfig.js)

When you run "npm run test" it will execute this script by opening cypress runner and using specified config.js.

If you run "npx cypress open" it will run with cypress.config.js. I don't really use it but you can put some default config there in case someone runs without script.

Dunno if this helps you, maybe someone has better approach but this works for me.

[techshashank80]

Yes, this solution worked for me. Thank you, Appreciate it.

[lmiller1990]

Since it's just JS now you could also do something like:

import fs from 'fs-extra'

const config1 = fs.readJsonSync('./config1.json')
const config2 = fs.readJsonSync('./config12json')

export default defineConfig(
  process.env.USE_CONFIG_1 ? config1 : config2
)

Just an idea!

[techshashank80]

Thank you for the idea, we are already using 'fs-extra' but question is, does cypress 10.0 support the 'configFile' option through cli? we have to pass config file name from command line.

[techshashank80]

as per cypress

You may use the --config-file command line flag or the configFile module API option to specify a .js or .ts file. JSON config files are no longer supported.

any input on this?

[lmiller1990]

I tried this out yarn cypress run --component --config-file cypress.blah.ts and it correctly read the cypress.blah.ts file. Is that not working for you? The API should be identical, you just pass a path to a JS module, not a JSON file.

[techshashank80]

Yes above —config-file is working fine , my question was for configFile where we were just passing the json file name without file extension before 10.0 version. But in your example, json files are being read. Is this cypress run env —configFile = stage no longer supported ?

[lmiller1990]

Just to clarify are you referring to this? It looks like it should still work. To clarify you want to have a cypress.env.json and have it merged with your cypress.config at runtime?

It might be good if you can provide a minimum repo if you think there is a bug.

{ 
  baseUrl: "http://staging.com"
}