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

config-resolver

v0.2.0

Published

A small, unopinionated configuration resolver for node apps

Downloads

6

Readme

Config Resolver

Build Status

A small, unopinionated library for resolving configuration variables in various levels.

Installation

npm install --save config-resolve

Usage

Without any sort of configuration, config-resolver will look at your environment variables and your command line arguments and construct a resolved object of configuration, where the command line arguments override the environment ones.

So:

var conf = require('config-resolver')();
console.log(conf);

And run with

PORT=8080; NAME=MY_APP; node index.js --PORT=3000 --HOST=localhost

Will result in

{
    PORT: 3000
    NAME: 'MY_APP'
    HOST: 'localhost'
}

Resolvers

Config resolver comes with 3 (for now) configuration resolvers. A resolver is a function that reads/resolves configuration, and returns an object. The currently supported resolvers are CommandLineArgumentsResolver, EnvironmentVariablesResolver and JSONResolver.

You can override the default resolver chain by providing them as arguments to the resolve function:

var resolver = require('config-resolver');
var conf = resolver.resolve(resolver.JSONResolver('./config.json'), resolver.CommandLineArgumentsResolver);
console.log(conf);

In this example, resolver will take what's in config.json as the default configuration, and override properties with the same name from the command line arguments.