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

l6conf

v0.1.0

Published

This node.js library introduces a policy for transforming environment variables into a hierarchically structured json and allows you to overwrite configurations by importing multiple config files consequently.

Downloads

455

Readme

l6conf

Overview

This node.js library introduces a policy for transforming environment variables into a hierarchically structured json and allows you to overwrite configurations by importing multiple config files consequently.

Overwriting Example

The overwrite direction goes from right to left, each new setting value overwrites previous ones.

/*
  Environment variables:
  FOO=0
*/
config.json({ "foo": "1", "bar": "2", "lorem": "ipsum" }).json({ "bar": "3" }).env();

config.get("foo"); // 0
config.get("bar"); // 3
config.get("lorem"); // ipsum

Nesting Example

DATABASE="MySpecialDB"
DATABASE_USERNAME="root"
DATABASE_PASSWORD="test"

transforms to:

config.get('database'); // MySpecialDB
config.get('database.username'); // root
config.get('database.password'); // test

Documentation

Installation

$ npm i --save l6conf

Load

let config = require('l6conf');

Set Environment variables

/*
  process.env.USER = "test"
  process.env.USER_FIRSTNAME = "John"
  process.env.USER_PASSWORD = "so_secret"
*/

// Sets the variables
config.env();

/*
  config.get('user');           // test
  config.get('user.firstname'); // John
  config.get('user.password')   // so_secret
*/

Set JSON variables

config.json('./path/to/file.json');

or

config.json({ "hello": { "world": "I am json" } });

Set custom variables

config.set('foo', 'bar');

or

config.json('foo.bar', 'hello world!');

Get values

config.get('foo'); // bar
config.get('foo.bar'); // hello world

Hierarchy

The values are being overwritten. This means that the last setting we add will replace previous settings.

config
  .json( { "user": "root", "pass": "secret" })
  .json( { "pass": "not_so_secret" });

config.get('pass'); // not_so_secret

Testing

To test you should install mocha

$ npm -g install mocha

and then run

$ mocha