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

mconf

v1.0.0

Published

Micro config for nodejs projects.

Readme

mconf

=======

Build Status Coverage Status

Simple config for nodejs.

Using:

  • npm i mconf --save

  • create directory with configurations

  • create files production.js and develop.js and put them into created directory

  • create index.js file with:

    es5 and older

    var Config = require('mconf').default;
    
    if (!__dirname) {
        var __dirname = require('fs').workingDirectory;
    }
    
    var config = new Config(__dirname,['production', 'develop']);
    module.exports = config.getConfig();

    es2016+

      import Config from 'mconf';
      
      if (!__dirname) {
          var __dirname = require('fs').workingDirectory;
      }
      
      let config = new Config(__dirname,['production', 'develop']);
      module.exports = config.getConfig();
  • run your node application with export env : export NODE_ENV=production for production env.

  • By default will be used develop config.

Environment name

By default using NODE_ENV, but if you need to use another environment name:

var config = new Config(__dirname,['production', 'develop']);
module.exports = config
   .setEnv('YOUR_ENV_NAME')
   .getConfig();

Merge config strategy

By default using deep merge strategy. But if you want non deep merge ( rewrite), you should use:

var config = new Config(__dirname,['production', 'develop']);
module.exports = config
   .setDeepMerge(false)
   .getConfig();