cli options don't override the default options in .ncurc.js about npm-check-updates HOT 6 OPEN

It uses commander, so I'm not sure why the equals delimiter is not working actually. I will look into that.

An option and its option-argument can be separated by a space, or combined into the same argument. The option-argument can follow the short option directly or follow an = for a long option.

serve -p 80
serve -p80
serve --port 80
serve --port=80

from npm-check-updates.

The syntax is actually ncu --target latest.

from npm-check-updates.

nice. it should also support this syntax because it is widly used and more readable.
typically tools like commander, yargs and other cli parsers can read and parse this syntax

from npm-check-updates.

Okay, so that wasn't the problem at all. I'm just not use to the = delimiter, but it works as expected with npm-check-updates.

I set up the scenario you described, and am unable to reproduce the issue. The CLI option correctly overrides the .ncurc.js option:

raine[1355]% cat package.json                                                                                             ✓
{
  "dependencies": {
    "ncu-test-v2": "^1.0.0",
    "ncu-test-tag": "^1.0.0"
  }
}

raine[1355]% cat .ncurc.js                                                                                                ✓
module.exports = {
  target: "minor"
}

raine[1355]% ncu
Using config file /Users/raine/projects/ncu-issues/1355/.ncurc.js
Checking /Users/raine/projects/ncu-issues/1355/package.json
[====================] 2/2 100%

 ncu-test-tag  ^1.0.0  →  ^1.1.0

Run ncu -u to upgrade package.json

raine[1355]% ncu --target=latest                                                                                          ✓
Using config file /Users/raine/projects/ncu-issues/1355/.ncurc.js
Checking /Users/raine/projects/ncu-issues/1355/package.json
[====================] 2/2 100%

 ncu-test-tag  ^1.0.0  →  ^1.1.0
 ncu-test-v2   ^1.0.0  →  ^2.0.0

Run ncu --target=latest -u to upgrade package.json

If you are not seeing the expected upgrades, it is probably due to something else. Feel free to post a package.json and .ncurc.js that reproduce the issue and I'd be happy to investigate further.

from npm-check-updates.

ok, let me reproduce the issue again and give you a feedback

from npm-check-updates.