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

flconf

v4.0.1

Published

Simple, pluggable, hierarchical configs

Downloads

179

Readme

flconf

Build Status

Simple, pluggable, hierarchical configs

install

$ npm install flconf --save

usage

If you have a config directory that looks like:

config
├── default.json
└── env
    ├── development.json
    ├── production.json
    └── test.json
var config = require('flconf')(__dirname + '/config');

config.use('default');
config.use('env/' + process.env.NODE_ENV || 'development');

module.exports = config.load();

flconf will load default.json first, then it will load the config file for the appropriate NODE_ENV. You can specify as many layers of config as you like.

Config filenames can be globs as matched by minimatch.

methods

var Config = require('flconf');

Config(dirname)

Creates a new Config instance. You must provide the dirname that flconf will use while loading config files.

You can omit the new operator and simply invoke flconf with the dirname if you wish:

var config = require('flconf')(__dirname);

config.use(file)

Adds file as a layer in this config. file should be the path to a config file without the .json extension.

config.use(function)

Adds a plugin to this config's plugin stack. Plugins are simply JSON.parse reviver functions that modify the config in some way. See the plugins section for more details.

config.load()

Loads all of the specified config files and returns the merged config object.

plugins

config.env

Replaces any bash-style environment variables with their actual values in the environment.

{
  "user": "${LOGNAME}"
}

Will load as:

{
  "user": "ruppel"
}

config.ms

config.use(config.ms);

Replaces ms-style time strings with their value in milliseconds.

{
  "maxAge": "1 day"
}

Will load as:

{
  "maxAge": 86400000
}

license

This software is free to use under the MIT license. See the LICENSE file for license text and copyright information.