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

env-config-shared

v2.1.0

Published

Get config objects from ENV variables defined in shared config.env

Downloads

6

Readme

Build Status Coverage Status

Get config objects from ENV variables defined in config.env. This module will search for config.env in current directory and bubble down to root.

If config files are elsewhere, they can be specified on the command line using CONFIG=fullpath1;fullpath2 node app.js. These files will override any configs in default config.env, if it exists.

Configuration values can be grouped together using a prefix and plucked out individually.

See node-env-config-shareduration for info on structuring config.env

Usage

#
# config.env:
#

# db configs
DB_VAR1=true
DB_VAR2=false

# redis configs
REDIS_VAR1=true
REDIS_VAR2=false

# app1
APP1_VAR1=1
APP1_VAR2=2

# app2
APP2_VAR1=3
#
# config2.env:
#

# override a config value
APP1_VAR2=100
//
// app.js
//

var config = require('env-config-shared')

// pluck out configs for app1 and app2
config
	.get('app1')
	.get('app2')

// we can now use the configs for app1 and app2
console.info(config.app1)
console.info(config.app2)

Use the default config only

~ node app.js
{
	var1: 1,
	var2: 2
}
{
	var1: 3
}

Override some config using the CONFIG env

~ CONFIG=./config2.env node app.js
{
	var1: 1,
	var2: 100
}
{
	var1: 3
}