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

hconf

v1.2.1

Published

Hierarchical configs using nconf

Downloads

6

Readme

hconf

An opinionated config loader for nodejs.

hconf looks for the file .<package name> (dot + package name from package.json) in the following directories (in case of conflicting property keys, the last one wins).

  • factory: in the package's root (dir where package.json is located).
  • user: in process.env.HOME, the current user's home directory.
  • custom files: a list of filenames with path. hconf is of the opinion that this option should used rarely.

hconf also looks for environment variables that look like: <uppercase package name>_A_B_C will map to the property key a.b.c (all lowercase) for the package's config.

Configuration data is global

Configuration data is merged into a nodejs global object. Once loaded, a package's config keys can be accessed with string keys <package name>.path.to.the.config.property.

Multiple packages

The sequence of require statements determines the order of merging of config data into the global object and therefore determines which config wins in the case of conflicting keys.

Example

For example, if package2 uses package1 and both packages use hconf for configuration management:

package1

/* .package1 */
{
  "some" : {
    "var" : "from package 1"
  }
}
# package1/index.coffee
hconf = require('hconf')(module:module)

hconf.get("package1.some.var")
.then (value) ->
  # value is "from package 1"

package2

/* .package2 */
{
  "some" : {
    "var" : "from package 2"
  },
  "__packages" : {
    "package1": {
      "some" : {
        "var" : "now from package 2"
      }
    }
  }
}
# package2/index.coffee

# requiring package1 loads its config first
package1 = require 'package1'

# package2's data merges and mutates the global config object
hconf = require('hconf')(module:module)

hconf.get("package2.some.var", "package1.some.var")
.then ([p2, p1]) ->
  # p2 is "from package 2"
  # p1 is "now from package 2"

Installation

Install with npm

npm install hconf

Usage

hconf = require("hconf") module: module

get(key, [key...])

  • key {String} configuration key to retrieve
  • Returns a Promise which resolves to the requested value(s) (or undefined).