Configuration object wrapper for nested configs with yargs integration. Extends nested-config with runCmd function.

JSDoc

API docs are available on the wiki.

Usage

yargs-config is itself a configuration object. All your current settings are stored in it. It keeps track of default options for you as well.

Initialize with your default settings

Create new config object using create(overrides [object], defaults [object]).

1const yc = require('yargs-config');
2
3let defaults = {
4    yourOption: 1,
5    nested: {
6        option: "two"
7    },
8    meta: {
9        yourOption: 'This is my option',
10        nested: {
11            option: 'This is my nested option'
12        }
13    }
14};
15
16let config = yc.create({}, defaults);

Notice the structure of meta object. It is used to populate yargs configuration. You can use either short form and provide just the description as shown above, or you can provide full meta object.

1// ...
2meta: {
3    yourOption: {
4        desc: 'This is my option',
5        alias: 'y'
6        // default: 1,     // will be filled automatically anyway
7        // type: 'number'  // will be filled automatically anyway
8    }
9    // ...
10}

default and type will be determined automatically, so no need to fill them out explicitly. Note that if config property is not inside meta object, it will not be exposed through yargs.

Update current settings

1let overrides = {
2    yourOption: 2,
3    nested: {
4        option: "three",
5    },
6};
7
8config.add(overrides, {});  // performs deep merge into current config state

Access settings

1config.yourOption;  // 2
2config.getDefault('yourOption');  // 1
3config.nested.option;  // "three"
4config.getDefault('nested.option');  // "two"

Run yargs

runFromCmd(propStr [string], callback)

Starts command-line application with yargs, supporting piped inputs.

• propStr - where to look for settings in case of nested config (e.g. consider propStr as the root). Leave empty for using whole object.
• callback - calls when done with (err, data, argv), where data is stdin and argv is parsed yargs argv object.

1if (!module.parent) {
2  // Running from CLI
3  config.runFromCmd('', (err, data, argv) => {
4    // err is null if ok
5    console.log(`This is input: ${data}`);
6    console.log(`These are passed settings: ${argv}`);
7  });
8  
9} else {
10  // Using as a module
11  module.exports = ...;
12}

Now your application app.js can be launched from CLI as follows:

1$ echo "your input" | app.js --yourOption 5 --nested.option "five"
2$ app.js "your input" --yourOption 5 --nested.option "five"