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

node-env-config-loader

v1.0.1

Published

Load node config from environment variables

Downloads

20

Readme

Node env config loader

travis

Load config from files and environment.

Default config file

The default config file is config/config.json

Application environment config file

If the APPLICATION_ENV variable is set, the file related to will be loaded.

For example if APPLICATION_ENV is set to live, config/config_live.json will be loaded.

Environment variables

All the variables beginning with your application name will try to be loaded.

For example if your application name is my-app and you have the following variables:

process.env.my_app_port = 3000;
process.env.my_app_redis_password = 'foobared';

The config will contain the following json:

 {
     "port": 3000,
     "redis": {
         "password": "foobared"
     }
 }

Override a key

if you have a config.json

{
    "key1": {
        "key11": "value1",
        "key12": "value2"
    }
}

and a config_APPLICATION_ENV.json

{
    "key1": {
        "key13": "value1"
    }
    "override": ["key1"]
}

key1 will be {"key13": "value1"}

Extra configuration

The application name will be automatically added under the name key.