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 🙏

© 2024 – Pkg Stats / Ryan Hefner

binford-config

v0.0.1

Published

Read only config module that pulls together optimist with json and yaml file parsing

Downloads

3

Readme

Binford Configuration

A read-only key-value and hierarchical runtime config API. The configuration comes from three places:

  • command line arguments
  • environment variables
  • environment-specific json and yml files
  • environment-agnostic json and yml files

You load the config once at runtime, typically next to other initialization code, and then throughout your code you simply call get() with the specified key. Configuration is merged together and follows the precedence set by the order you load the configuration.

The get() method will not throw an exception, and instead prefers to return undefined if a key isn't found.

Synopsis

var config = require('binford-config');

config.binfordConvention(__dirname); // many people prefer this as well // config.binfordConvention(__dirname + "/conf");

var database = require('database').connect( config.get("database:username"), config.get("database:password") );

var isProduction = (config.get("NODE_ENV") == 'production');

// That's it.

Binford Convention

The binford precendence is roughly implemented using this logic:

// load values from the specific fil config.loadFile(path.join(__dirname, ".binford.json")); config.loadFile(path.join(__dirname, ".binford.yml")); // checks the environment variables set at runtime config.loadFile(path.join(__dirname, ".binford.production.json")); config.loadFile(path.join(__dirname, ".binford.production.yml")); // load any values stored in the system environment variables config.loadEnv(); // load any arguments passed in via the command-line config.loadArgv();

// That's it!