CODEWITHSUNDEEP
protractorpackage.jsoncucumberjs
sininen
sininen

Reputation: 553

Protractor option does not work in package.json script

The following command works as expected:

protractor --cucumberOpts.tags='not @tag1' conf.js

Now I want to add this command as a script to package.json like this:

"scripts": {
    "my-script": "protractor --cucumberOpts.tags='not @tag1' conf.js"
}

Running the command npm run my-script gives me the following error:

Usage: protractor [configFile] [options]
configFile defaults to protractor.conf.js
The [options] object will override values from the config file.
See the reference config for a full list of options.

Options:
  ...

Error: Error: more than one config file specified

Why is that?

Both of the commands seem to be identical.

Upvotes: 0

Views: 482

Answers (1)

DublinDev
DublinDev

Reputation: 2348

This is not actually a protractor issue. I was able to recreate this issue and resolved it by using escaped doubles quotes in that script string like so.

"scripts": {
    "my-script": "protractor --cucumberOpts.tags=\"not @tag1\" conf.js"
}

This issue (apparently) is to do with how node handles single quotes on different operating systems. There is some more info in this question.

Upvotes: 1

Related Questions