npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2024 – Pkg Stats / Ryan Hefner

yargs-config

v1.1.2

Published

Configuration object wrapper for nested configs with yargs integration

Downloads

8

Readme

Build Status

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]).

const yc = require('yargs-config');

let defaults = {
    yourOption: 1,
    nested: {
        option: "two"
    },
    meta: {
        yourOption: 'This is my option',
        nested: {
            option: 'This is my nested option'
        }
    }
};

let 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.

// ...
meta: {
    yourOption: {
        desc: 'This is my option',
        alias: 'y'
        // default: 1,     // will be filled automatically anyway
        // type: 'number'  // will be filled automatically anyway
    }
    // ...
}

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

let overrides = {
    yourOption: 2,
    nested: {
        option: "three",
    },
};

config.add(overrides, {});  // performs deep merge into current config state

Access settings

config.yourOption;  // 2
config.getDefault('yourOption');  // 1
config.nested.option;  // "three"
config.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.
if (!module.parent) {
  // Running from CLI
  config.runFromCmd('', (err, data, argv) => {
    // err is null if ok
    console.log(`This is input: ${data}`);
    console.log(`These are passed settings: ${argv}`);
  });
  
} else {
  // Using as a module
  module.exports = ...;
}

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

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