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

x-config

v0.0.18

Published

Configuration package for node applications.

Downloads

11

Readme

Build Status

#x-config This package provides an easy way to access configuration information based on local or system configuration files. This package follows the following inheritance flow:

  • ./config/default.json
  • ./config/{{environment}}.json
  • {{system}}/{{id}}.json
  • {{system}}/default.json

NOTES:

  • The locator climbs the path from the parent module location to the volume root looking for a config directory. This enables packages to maintain seperate configurations.
  • The environment can be determined via HOSTNAME, or by placing env in default.json with dev, test, or prod, or pattern matching (see below).

##Usage

npm install x-config --save

{
	"id": "my-app",
	"env": { "dev": "^dev", "test": "^test", "prod": "^prod" }, 
	"consoleEnabled": true
}
var config = require('x-config');
if (config.consoleEnabled){
	console.log(config);
}
var configFn = require('x-config'); // returns a function if _rest is enabled.

configFn(function(err, config){
  if (config.consoleEnabled){
    console.log(config);
  }
});

The path to the system configuration files can either be defined using a SYSTEM_CONFIG environment variable or set systemConfig in the default or environment config files.

{ "systemConfig": "/etc/node/" }

To pull configuration from a REST service, use the following. This will cause the config library to return a function which you will want to call.

{ "_rest": { "url": "http://myrestservice/...", "headers": { "X-AuthToken": "auth-token" } } }