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 🙏

© 2025 – Pkg Stats / Ryan Hefner

handy-config

v1.2.0

Published

A lightweight module that takes care of handling configs / credentials based on node environment

Readme

Handy Config

A lightweight module that takes care of handling configs / credentials based on node environment

Usage

Require the module with:

var cfg = require('handy-config')();   //in a single file
global.cfg = require('handy-config')();  //globally
if (cfg.error) throw cfg.error;

The module will load only the data specific to your NODE_ENV. This is how your .cfg file should look like:

{
  "all": {
    "session_secret": "meatballs",
    "port": 3000
  },
  "production": {
    "port": 80,
    "mongo_url": "mongodb://localhost/prod",
    "mongo_pass": "spaghetti"
  },
  "development": {
    "port": 8080,
    "mongo_url": "mongodb://localhost/dev"
  }
}

Fields under all apply regardless of NODE_ENV, but will get overridden by environment specific fields.

In this example the port field doesn't apply (given NODE_ENV='development'), because it was already defined.

Given that you set NODE_ENV to production, invoking the module returns the following:

cfg = {
  port: 80,
  mongo_url: "mongodb://localhost/prod"
  mongo_pass: "spaghetti",
  session_secret: "meatballs"
}
// FYI the module uses the spread operator to handle this
// cfg = {...config.all, ...config.production}

You only have to invoke the module once.

// app.js
var cfg = require('handy-config')(); //configures the modules and returns the config
// This step cannot be omitted and needs to be done before all other imports

// mongo.js
var cfg = require('handy-config'); //returns the config

Config

You can override the default file name and encoding. Below are the defaults:

var cfg = require('handy-config')({
  path: '.cfg',
  encoding: 'utf8'
});

Set your NODE_ENV easily

You can add this to your package.json

"scripts": {
  "dev": "set NODE_ENV=development&& node app",
  "prod": "set NODE_ENV=production&& node app"
}

And then just run it in your command line

npm dev

This will automatically set your NODE_ENV before runtime.

Install

Run this command in your command line:

npm i handy-config

And that's it!