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

unified-config

v0.1.0

Published

Merges static config with environment variables

Downloads

1

Readme

unified-config

Travic CI status

Merges env and local config and provides consistent camelCased config properties in one place.

Config structure

Library merges two parts of config together:

  • Env config, that relies on ENV variables or default ones
  • Common config, that is usually static across all deployments.

ENV config - required

This part of config checks if required environment variables are provided and provides default values for others. Transfers each ENV variable into camelCased one.

To declare default value for variable, just provide it in configuration. To make some variable required, provide its value as null.

Example config file:

{
  testVariable1: 'test',
  testVariable2: null
}

Case 1:

export TEST_VARIABLE_1='overwritten'

This case will throw error, because second variable TEST_VARIABLE_2 is missing and it's required one.

Case 2:

export TEST_VARIABLE_2='test2'

This example will result in following config structure:

{
  testVariable1: 'test', // Using default value
  testVariable2: 'test2' // Using one provided by ENV
}

Case 3:

export TEST_VARIABLE_1='test123'
export TEST_VARIABLE_2='test2'

This example will result in following config structure:

{
  testVariable1: 'test123', // Overriden default value
  testVariable2: 'test2' // Using one provided by ENV
}

Common config - optional

This is part of config that is provided as it is and is merged with latter, overwriting values if any existing are found. It could store e.g. static variables that aren't changed between different environments and deployments.

Example common config file:

{
  commonVar1: 'test',
  commonVar2: 123
}

Usage

Library uses ES6 classes. In order to start using it, instance has to be constructed, using at least ENV config:

    var config = require('unified-config');

    var envConfig = {
      var1: 1,
      var2: null
    };
    var commonConfig = {
      commonVar: 'common'
    }

    var unifiedConfig = new Config(envConfig, commonConfig);
    unifiedConfig.getConfig(); // Returns one configuration file
    // or error if required ENV config variable wasn't provided

Scripts

To run eslint:

npm run lint

To run tests:

npm test

To check coverage:

npm run coverage