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

ih-config

v1.0.3

Published

Influence Health common config module

Downloads

3

Readme

ih-config

A common configuration module to abstract precedence of config options.

about

ih-config is a lightweight wrapper on top of the https://github.com/flatiron/nconf module, which abstracts access to various configuration stores. Configuration data may come from files, machine environment variables, or the node command line.

usage

  • require the module
var config = require('ih-config');
  • get a config value
var foo = config.get('foo');

// nested property access
var bar = config.get('foo:bar');

config stores

ih-config supports 3 types of configuration storage, and 4 levels of precedence (listed from highest to lowest precedence):

  • CMD params - command line parameters, passed to node
  • ENV variables - machine environment variables
  • files - JS files, located in a directory in the root of your project named config
    • *.config.local.js takes precedence over
    • *.config.js

config files

Config files must be placed in the root config directory. Files should match for format *.config.js in order to be included. Additionally, files matching *.config.local.js are also parsed. Local files take precedence over non-local files. Normally a repo should ignore config/*.local.*, allowing developers to override properties as needed, without committing those changes to the repository.

environment variables

Machine environment variables are included in the available configuration data. This is the same set of data normally provided by node under process.env.

command line parameters

Config data may also be set directly from the command line, when starting node. To set a parameter value, prefix it with two dashes, and place an equals sign between the value. For example: --value='hello world' Note that command line parameters take the highest priority.