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

plain-config

v0.1.4

Published

A very simple config loader

Downloads

311

Readme

plain-config

A very simple config loader module.

Installation

npm install plain-config

Usage

The simplest form of usage is the following:

'use strict'
const config = Object.freeze(require('plain-config')());

The system will automatically attempt to load these files is top down order

conf/config.js
conf/config-local.js

By default, the base config is read from conf/config.js and extending config is optionally loaded from conf/config-local.js

If either file is not found, it will fail silently

Config file format
var config = {};
config.container = {
  key: 'value'
}
module.exports = config;
Local config file format

A sample local config may look something like this: (conf/config-local.js)

module.exports = {
	config: {
		container: {
			key = 'value2';
		}
	}
}

or

module.exports = function(config) {
	config.container.key = 'value2';
	return config;
}

Advanced usage

'use strict'
const config = Object.freeze(require('plain-config')('/base/path'));

In this example, a cwd directory will be overwritten. Modifies path compilation.

CLI parameters

You can direct plain-config to load configs from specific locations using --base and --conf parameters as follows:

node somefile.js --base=conf/config.js --conf=conf/config-local.js --conf=conf/config-local2.js

--base config is your default config definition and every --conf will be applied in provided order.