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

@sh4dow/config

v0.10.5

Published

Configuration module

Readme

node-config

Configuration module for nodejs applications. Supports json, js and yaml format files

Simple use

// config.json
{
    "database": {
        "host": "localhost",
        "user": "user"
    },
    "version": "1.2"
}
// index.js
var config = new Config('./config.json');
config.get('database.host'); // 'localhost'
config.get('database'); //  {"host": "localhost", "user": "user"}
config.set('database.host', 'extrenal.host.com'); //emit change event if You need to reload something

Platform configs

Default trigger to recognize platform is enviroment variable NODE_ENV. NODE_ENV can be changed using option envSwitch or manualy set platform name using option env.

// config.json
{
    "database": {
        "host": "localhost",
        "user": "user"
    },
    "logLevel": "info"
}
// stage.js
module.exports = {
    logLevel: "debug"
}

require module YAML@2

# production.yml
database:
  host: production.com
  user: xo74ffo2blydbow
// index.js
var options =  {
    path: './config.json', // main config
    envFiles: [
        './stage.json',
        './production.json'
    ],
    envSwitch: 'NODE_ENV' //default value
}
var config = new Config(, options);

// process.env.NODE_ENV == 'stage'
config.get('database.host'); // localhost
config.get('logLevel'); // debug

// process.env.NODE_ENV == 'production'
config.get('database.host'); // production.com
config.get('logLevel'); // info

Single config with platform changes

Replacing value with object You can change single value.

{
    "index": {
        "value": "default", // default value for all platforms
        "env:plaftormName": "diffrent",
        "env:plaftormName2": "diffrent",
    }
}

Example:

// config.json
{
    "database": {
        "value": {
            "host": "localhost",
            "user": "user"
        },
        "env:production": {
            "host": "production.com",
            "user": "xo74ffo2blydbow"
        }
    },
    "logLevel": {
        "value": "info",
        "env:production": "warning",
        "env:stage": "debug"
}

Cli support

You can use cli arguments (--config.) or enviroment variables (NODE_CONFIG_) to change config value

$ node index.js --config.loglevel=info --config.database.host=test.host.com --config.new.index=true

{
    "database": {
        "host": "test.host.com",
        "user": "user"
    },
    "logLevel": "info",
    "new": {
        "index": true
    }
}

Enviroment variable has disadvantage. Config can't have underscore "_" on names

$ NODE_CONFIG_LOGLEVEL=warning NODE_CONFIG_DATABASE_HOST=example.com node index.js

{
    "database": {
        "host": "example.com",
        "user": "user"
    },
    "logLevel": "warning"
}