npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details


  • User packages



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.


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 🙏

© 2021 – Pkg Stats / Ryan Hefner




hardwired configuration loader





Based on RC npm downloads

The non-configurable runtime configuration loader for lazy people.

npm version dependencies Status codecov npm downloads


The only option is to pass run-con the name of your app, and your default configuration.

var conf = require('run-con')(appname, {
  //defaults go here.
  port: 2468,

  //defaults which are objects will be merged, not replaced
  views: {
    engine: 'jade'

run-con will return your configuration options merged with the defaults you specify. If you pass in a predefined defaults object, it will be mutated:

var conf = {};
require('run-con')(appname, conf);

If run-con finds any config files for your app, the returned config object will have a configs array containing their paths:

var appCfg = require('run-con')(appname, conf);
appCfg.configs[0] // /etc/appnamerc
appCfg.configs[1] // /home/dominictarr/.config/appname
appCfg.config // same as appCfg.configs[appCfg.configs.length - 1]


Given your application name (appname), run-con will look in all the obvious places for configuration.

  • command line arguments, parsed by minimist (e.g. --foo baz, also nested:
  • environment variables prefixed with ${appname}_
    • or use "__" to indicate nested properties (e.g. appname_foo__bar__baz =>
  • if you passed an option --config file then from that file
  • a local .${appname}rc or the first found looking in ./ ../ ../../ ../../../ etc.
  • $HOME/.${appname}rc
  • $HOME/.${appname}/config
  • $HOME/.config/${appname}
  • $HOME/.config/${appname}/config
  • /etc/${appname}rc
  • /etc/${appname}/config
  • the defaults object you passed in.

All configuration sources that were found will be flattened into one object, so that sources earlier in this list override later ones.

Configuration File Formats

Configuration files (e.g. .appnamerc) may be in either json or ini format. No file extension (.json or .ini) should be used. The example configurations below are equivalent:

Formatted as ini

; You can include comments in `ini` format if you want.


; `run-con` has built-in support for ini sections, see?

  www     = ./commands/www
  console = ./commands/repl

; You can even do nested sections

  engine  = ejs

  new     = generate-new
  engine  = generate-backend

Formatted as json

  // You can even comment your JSON, if you want
  "dependsOn": "0.10.0",
  "commands": {
    "www": "./commands/www",
    "console": "./commands/repl"
  "generators": {
    "options": {
      "engine": "ejs"
    "modules": {
      "new": "generate-new",
      "backend": "generate-backend"

Comments are stripped from JSON config via strip-json-comments.

Since ini, and env variables do not have a standard for types, your application needs be prepared for strings.

To ensure that string representations of booleans and numbers are always converted into their proper types (especially useful if you intend to do strict === comparisons), consider using a module such as parse-strings-in-object to wrap the config object returned from run-con.

Simple example demonstrating precedence

Assume you have an application like this (notice the hard-coded defaults passed to run-con):

const conf = require('run-con')('myapp', {
    port: 12345,
    mode: 'test'

console.log(JSON.stringify(conf, null, 2));

You also have a file config.json, with these contents:

  "port": 9000,
  "foo": "from config json",
  "something": "else"

And a file .myapprc in the same folder, with these contents:

  "port": "3001",
  "foo": "bar"

Here is the expected output from various commands:

node .

  "port": "3001",
  "mode": "test",
  "foo": "bar",
  "_": [],
  "configs": [
  "config": "/Users/stephen/repos/conftest/.myapprc"

Default mode from hard-coded object is retained, but port is overridden by .myapprc file (automatically found based on appname match), and foo is added.

node . --foo baz

  "port": "3001",
  "mode": "test",
  "foo": "baz",
  "_": [],
  "configs": [
  "config": "/Users/stephen/repos/conftest/.myapprc"

Same result as above but foo is overridden because command-line arguments take precedence over .myapprc file.

node . --foo barbar --config config.json

  "port": 9000,
  "mode": "test",
  "foo": "barbar",
  "something": "else",
  "_": [],
  "config": "config.json",
  "configs": [

Now the port comes from the config.json file specified (overriding the value from .myapprc), and foo value is overridden by command-line despite also being specified in the config.json file.

Advanced Usage

Pass in your own argv

You may pass in your own argv as the third argument to run-con. This is in case you want to use your own command-line opts parser.

require('run-con')(appname, defaults, customArgvParser);

Pass in your own parser

If you have a special need to use a non-standard parser, you can do so by passing in the parser as the 4th argument. (leave the 3rd as null to get the default args parser)

require('run-con')(appname, defaults, null, parser);

This may also be used to force a more strict format, such as strict, valid JSON only.

Note on Performance

run-con is running fs.statSync-- so make sure you don't use it in a hot code path (e.g. a request handler)


Original author is @dominictarr


Multi-licensed under the two-clause BSD License, MIT License, or Apache License, version 2.0