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 🙏

© 2026 – Pkg Stats / Ryan Hefner

fleng-config

v1.1.4

Published

Hierarchical configuration for fleng with YAML files and atomic object merging.

Readme

fleng-config

Hierarchical fleng configuration with YAML files and atomic object merging.

Installation

npm install --save fleng-config

Usage

var fconf = require('fleng-config');

// Initialize config provider
var config = new fconf.Provider(__dirname);

// Add default.yaml file as `default` store
config.add('default', 'config/default.yaml');

// Add development.yaml file as `environment` store
config.add('environment', 'config/development.yaml');

// Add an object literal as `overrides` store
config.add('overrides', {
  group: {
    property: 'value'
  }
});

// Add defaults store
config.defaults('global', { group: { property: 'value' } });

// Add overrides store
config.overrides('important', { group: { property: 'value' } });

// Explicitly set value at path `group.property`. It cannot be overrided
config.set('group.property', 'updated value');

// Get full config as an object
config.get();

// Get `group` branch of config
config.get('group');

// Get value at path `group.property`
config.get('group.property');

API

new fconf.Provider([String root])

Create a new config provider. Optional parameter root sets the directory against which file paths will be resolved. If omitted process.cwd() will be used.

.add(String name, String filePath|Object store)

Add a store to the config provider. If filePath is passed provider will try to load a file from that path. The path is resolved against root passed to the constructor or process.cwd(). If an object literal was passed as second argument, it will be added to the config provider as is.

.get([String path])

Get a value by the path passed. If value was not found, method will return undefined.

.set(String path, * value)

Set a value at the passed path. Values set with this method could not be overrided later.

.defaults(String path, * value)

Add a default store. Values from this store will be used if they were not found in generic and overrides stores.

.overrides(String path, * value)

Add an override store. Values from this store will not be overrided by generic or defaults stores.

Build

Module source is in ES6 module syntax. It's built using Babel.js.

Install development dependencies:

npm install -d

and run:

make

Tests

Tests are written using mocha and should.js library. To run testing install development dependencies:

npm install -d

and run:

npm test

License

MIT.