Codeceptjs doesn't support to use minimist to pass environment variable

What are you trying to achieve?

Using minimist to use -e to passing environment variable. For example adding the following script in package.json

"ci_xxx": "codeceptjs run -c codecept.ci.conf.js --grep @test -e prod",
"stage_xxx": "codeceptjs run -c codecept.ci.conf.js --grep @test -e staging",
"local_xxx": "codeceptjs run -c codecept.ci.conf.js --grep @test -e dev",

What do you get instead?

an error:

unknown option `-e'

Details

It looks like all the supported args are already pre-defined here: https://github.com/codeceptjs/CodeceptJS/blob/3.x/bin/codecept.js

Can we update codeceptjs to support to use minimist? Much Thanks!

[PeterNgTr]

hey @YSuMinto how about using this https://www.npmjs.com/package/dotenv?

Creating the according .env files like .dev.env, etc. In your codecept.conf.js:

...
switch (process.env.ENV) {
  case 'dev':
    require('dotenv').config({ path: '.dev.env' });
    break;
  case 'prod':
    require('dotenv').config({ path: '.prod.env' });
    break;
  default:
    require('dotenv').config({ path: '.staging.env' });
}
...

following script in package.json

"ci_xxx": "export ENV=prod && codeceptjs run -c codecept.ci.conf.js --grep @test",
"stage_xxx": "export ENV=staging && codeceptjs run -c codecept.ci.conf.js --grep @test",
"local_xxx": "export ENV=dev && codeceptjs run -c codecept.ci.conf.js --grep @test",

Then I believe you’d achieve the same expectations.

[DavertMik]

Yes, we don’t support minimist as we use different option to parse arguments and options.

to introduce custom options use environment variables:

TEST_ENV=production codeceptjs run
``