How to stop yargs handling --help, --version etc about nconf HOT 2 OPEN

That's an interesting find! I need to look at this a bit deeper to see if there's a way to alter this behavior. This might also be a bug in nconf...

In the meantime, if you happen to discover any new information, please let me know!

from nconf.

@jcoglan I finally got a few minutes to take a closer look at this.

I'm not sure what the original intent of nconf + yargs was, but it makes sense to me that someone might want to use some of the CLI features from yargs (like usage and help) as part of their nconf-enabled app. I would assume there are folks doing this today.

However, as you noted, some people may not want that behavior, which is why nconf supports a custom/external yargs instance being passed to the argv loader (as you showed in your final example).

You also observed that passing a custom yargs instance to nconf results in options like parseValues being ignored/unavailable. While the readme doesn't explicitly state that such a scenario is supported, I do agree that intuitively, someone would expect to be able to use both features in parallel. I've implemented a fix for this behavior and updated the readme to explicitly show its availability. I think this will launch as part of nconf v0.13 next week.

Finally, I investigated your assertion that parseValues: false is not the default for the argv loader, but I could not duplicate the behavior you indicated. When I don't specify that option in the args, values are not parsed (e.g., 'false' is a string, not a boolean). Fliping parseValues: true resulted in the expected behavior of 'false' becoming a boolean. If you still find that this is a problem, please provide a code sample so I can duplicate it.

from nconf.