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

configyour

v0.0.1

Published

Simple directory and file based configuration using json and yaml

Readme

configyour

Simple directory and file based configuration using json and yaml

Installation

$ npm install configyour

Usage

configyour will read the directory that you pass it and return an object containing the contents of the .json, .yml, and .yaml files, keyed the by filenames. Then it will go a single level down the directory chain to a directory named the same as process.env.NODE_ENV and override any existing keys with those found in the envrionment-specific directory.

For example:

|- my-app
|- server.js
|- config/
|  |- foo.json
|  |- production/
|  |  |- foo.json
|  |- development/
|  |  |- foo.json
|  |  |- debug.json

If your server.js file had the following line in it:

var config = require('configyour')(__dirname + '/config');

In production, the output would be an object that looked like:

{
  "foo": {
    // content of config/production/foo.json
  }
}

In development, the output would be an object that looked like:

{
  "foo": {
    // content of config/development/foo.json
  },
  "debug": {
    // content of config/development/debug.json
  }
}

And finally, in test, the output would be an object that looked like:

{
  "foo": {
    // content of config/foo.json
  }
}

License

Copyright (c) 2013 Matt Insler Licensed under the MIT license.