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

configuration-loader

v0.1.0

Published

A simple environment configuration loader for Node.js

Downloads

2

Readme

configuration-loader

A simple environment configuration loader for Node.js

API

var config = require('configuration-loader');

Returns a singleton instance of the configuration loader using process.env.NODE_ENV as the environment identifier (defaults to development).

config.ConfigurationLoader([environment])

Returns the constructor function for the configuration loader (for use when more than one configuration loader is required). Accepts an optional environment identifier (defaults to development if not specified).

config.load(directory, callback)

Loads the configuration files found at the specified fully-qualified directory. Accepts a callback(err) function which is called when all configurations for the specified environment have been loaded, or an error occurs.

The configuration files should be placed under a subdirectory (named after process.env.NODE_ENV or environment) of directory (refer to examples).

config.get(path)

Returns the configuration property value at path of the loaded configuration, or undefined.

config.set(path, value)

Sets the configuration property value at path of the loaded configuration. If a portion of path does not exist, it is created.

Examples

Usage

Imagine that we have the following directory structure for our project

.
+-- config
|	+-- development
	|	+-- app.js
	|	+-- mongo.js
	|	+-- log.js
|	+-- production
	|	+-- app.js
	|	+-- mongo.js
+-- index.js

and the config folder holds various configurations for different environments. Each configuration file should export a namespaced object containing necessary configuration entries. For example, the contents of app.js for the development environment could be:

'use strict';

module.exports = {
	app: {	// The namespace for our configuration
		title: 'Demo',
		description: 'Configuration loader demo app',
		port: 3000
	}
};

Then in our index.js file we could do the following:

'use strict';

var path = require('path'),
	config = require('configuration-loader');
	
	config.load(path.resolve(__dirname, './config'), function(err) {
		if (err) {
			// handle error
		}
		config.get('app.title'); // returns 'Demo'
		config.set('app.port', 3001);
		config.get('app.port'); // returns 3001
	});

Multiple loaders

The module returns a singleton object by default. In order to have more than one configuration loader instance, use the exported constructor function:

'use strict';

var config = require('configuration-loader'),
	otherConfig = new config.ConfigurationLoader();
	
	console.log(config === otherConfig); // false

Debug

To enable debugging output, use DEBUG=icybit:config when starting Your application.

License

MIT