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 🙏

© 2026 – Pkg Stats / Ryan Hefner

rcfg

v0.1.1

Published

Configurable package.json-aware sync/async rc alternative

Readme

rcfg

Build Status

Search for configurable package.json-aware sync/async rc alternative ends here.

Installation

npm i rcfg --save

Usage

var rc = require('rcfg');

// load synchronously (looks for .apprc, <package.json as JSON>['app'], ...)
// (for complete list of sources see "Defaults" -> "Load order"))
var cfg = rc('app');

// load asynchronously
rc('app', function (err, cfg) { ... })
rc('app', {cwd: '/something/other/than/process.cwd()'}, function (err, cfg) { ... })

You might want to use rcfg together with object-path (or similar), like so:

var cfg = require("object-path")(require('rcfg')('app'));

// check that path exists
cfg.has('key.nested_key.another_nested_key');

// get deep property (with optional default value)
cfg.get('key.nested_key.another_nested_key', 'default_value')

// get the first non-undefined value
cfg.coalesce(['a.b', 'a.c.d'], 'default_value');

Defaults

Load order

sources higher in the list take precedence over those located lower

  • env variables: ${name}_key(__anotherkey)?

    example: name_foo__bar__baz=qux translates to {foo: {bar: {baz: "qux"}}}

  • command line: --config <file>

  • closest .${name}rc* (search will stop on reaching package.json)

  • closest package.json (content of [pkgField || name])

  • ~/.${name}rc*

  • ~/.${name}/config***

  • ~/.config/${name}rc**

  • ~/.config/${name}/config***

  • /etc/${name}rc**

  • /etc/${name}/config***

  • defaults (rcfg('name', {def: {foo: {bar: "baz"}}}))

* or .${name}rc.{json,yml,yaml}, .${name}.{json,yml,yaml}
** or ${name}rc.{json,yml,yaml}, ${name}.{json,yml,yaml}
*** config.json, config.{yml,yaml} will be tried too

This list is controlled by src option.

Formats

Config files can be written in json or yaml. Additional file types can be registered using fmt option. For example, in order to support toml all you need to do is:

var toml = require('toml');

var cfg = rc('name', {
  fmt: function (def) {
    return def.concat({ext: 'toml', parser: toml.parse});
  }
});

Merge strategy

deep (e.g. ~/.apprc {foo: {bar: {baz: 1}}, dox: -3} + .apprc {foo: {bar: {qux: 2}}, dox: 3} = {foo: {bar: {baz: 1, qux: 2}}, dox: 3}). Can be overwritten with merge option.

License

MIT License