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

context-config

v0.3.10

Published

context-config-node ===================

Downloads

10

Readme

context-config-node

  • ConfigurationBuilder allows reading/writing configs using local or remote storage. Single API is used in both cases which makes it easier to work with the class. This is the only class users should be using directly to utilize all functionality provided by the module. ConfigurationBuilder uses the following classes underneath:
    • ContextConfiguration is an advanced configuration lookup utility. The main feature is to look for best match of the same keywords, given a list of additional contexts. Compared with config.get(key), it provides config.get(key, contexts, default).
      • ForwardConfiguration is a proxy which stores an array of ContextConfigurations and forwards get(key) requests to elements of that array. It allows notifying users about changes in configs using 'change' event on EventEmitter.
      • NodeConfig is used to work with configs stored in local file system. It is a wrapper of node-config library

API

| Function | Description | |---|---| |ConfigurationBuilder| |require('context-config').ConfigurationBuilder|importing the constructor| |new ConfigurationBuilder(emitter)|constructor accepts an EventEmitter and will emit 'config-read' event when new config is read| |build(context, ref)| ref object lists properties of the app whose configs we want to load (can contain properties domain, target, project, config, and version). Returns a promise.

Usage

ConfigurationBuilder

create a new instance of ConfigurationBuilder

var ConfigurationBuilder = require('context-config').ConfigurationBuilder;
var builder = new ConfigurationBuilder(emitter);

call build method to load the config which in turn returns a promise.

builder.build(context, ref)
.then(function(config){
	// use the config
	console.log(config.get('key'));
})
.fail(function(error){
	// handle the error
	console.log(error.stack);
})
.done();

ContextConfiguration

create a new instance of ContextConfiguration

var ContextConfiguration = require('context-config').ContextConfiguration;
var config = new ContextConfiguration([],[]);

append new values to the config

// without context
config.append({
	"key":"k1",
	"value":"v1"
});
// with context
config.append({
    "key":"k1",
    "context": {"site":"en-US"},
    "value":"v2"
});

get values using a key

// without a context
config.get("k1");	// should return "v1"
// with a context
config.get("k1", [{"site":"en-US"}]);	// should return "v2"