npm-run-script with commander.js

Question

Good day. The question is simple, how to pass flags/options to npm-run-script and read them using commander.js.

Example: package.json

{
  "scripts": {
    "start": "node index.js"
  },
  "dependencies": {
    "commander": "^12.1.0"
  }
}

index.js

const { program } = require("commander");

program.option("-p --config-path <path>", "config path", ".").parse();
console.log(`options: ${ JSON.stringify(program.opts()) }`);

Running 1 and 2, works as expected:

(1) node index.js -p "/path/foo/boo"
(2) node index.js --config-path="/path/foo/boo"

results in: options: {"configPath":"/path/foo/boo"}

Running npm start (used special --)

(1) npm start -- -p="/path/foo/boo"
(2) npm start -- --config-path="/path/foo/boo"

results in:

> start
> node index.js

options: {"configPath":"."}

configPath option received default value ".".

Can the same result be achieved with npm-run-script?

similar question

shadowspawn · Accepted Answer · 2024-08-29 09:18:58Z

1

This is a problem with recent versions of npm on PowerShell. You could try an older version of npm, or using a different shell, or using -- twice as a temporary work-around!

There is more detail in this npm issue: https://github.com/npm/cli/issues/7375

answered Aug 29, 2024 at 9:18

shadowspawn

3,91527 silver badges34 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

babinik Over a year ago

thanks. Work-around works (using -- twice). npm start -- -- --config-path="/path/foo/boo"

Collectives™ on Stack Overflow

npm-run-script with commander.js

1 Answer 1

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related