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

confiig

v4.0.3

Published

Super simple config loader 💾

Downloads

19

Readme

confiig

Super simple config loader. confiig loads configuration based on NODE_ENV environment variable.

Getting Started

$ npm install confiig

Usage

Basically, configuration loads from ./config directory.
You can set CONFIG_PATH environment variable to change default config path.
confiig tries to load config file that named like BUILD_PHASE or NODE_ENV + '.js'.

├── config
│   ├── cbt.js
│   ├── default.js
│   ├── development.js
│   ├── local.js
│   ├── production.js
│   └── sandbox.js
const conf = require('confiig');

console.log(conf.read('foo.bar'));

Default config

If 'default.js' config file exists in config path then configuration consisted based on the 'default' file and merged NODE_ENV configs into default one.

Multiple Configs

Multiple configs can be merged with separator. For example, set NODE_ENV with separator / like local/foo then default.js + local.js + foo.js configs are merged.

Dynamic NODE_ENV

If the NODE_ENV or BUILD_PHASE environment variable changes, it will automatically reread and merge the config files and return the path values when you call the read method. If no changes that environment variable, then it memoization that merged configs.

const conf = require('confiig');

process.env.NODE_ENV = 'development';
console.log(conf.read('foo.bar')); // development config value

process.env.NODE_ENV = 'sandbox';
console.log(conf.read('foo.bar')); // sandbox config value

API

.read(path, [defaultValue])

path (string): The path of the property to get.
defaultValue (any): The value returned for undefined resolved values. Optional.
returns (any): the value in the config if found, otherwise it returns undefined.