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

epa

v0.2.1

Published

simple environment configuration using json files

Downloads

121

Readme

EPA

No, not that EPA... this EPA is a simple way to configure different run time environments using JSON files instead of ENV settings.

How To Use It

1) Install it:

npm install epa

2) Add config files to the root of your project:

mkdir env
mkdir env/development
mkdir env/production

touch env/development/config.json
touch env/production/config.json

3) Require it

var epa = require("epa").getEnvironment();

4) Set the NODE_ENV to the right environment when running your app

NODE_ENV=production node myApp.js

The default is to assume "development" as the environment. If you specify anything other than "development", it will look for that folder / config.json.

5) Use it

In your app, you can reference any value from your config file as a property of the epa object, directly.

{
  "foo": "bar"
}
var epa = require("epa").getEnvironment();
var foo = epa.get("foo");
console.log(epa.foo);

The same works for environment variables. For example, the current "NODE_ENV" environment variable can be retrieved using the same get method:

var epa = require("epa").getEnvironment();
var env = epa.get("NODE_ENV");
console.log(env);

Your Own EPA Instance

The getEnvironment method from the EPA object returns a cached, and default instance of the EPA environment configuration. However, you can create your own instances whenever you want to, using the EPA class that comes with the EPA namespace.

var EPA = require("epa").EPA;

var myEPA = new EPA({
  folder: "my-config",
  systemEnv: process.env,
  environment: "dev"
});

The folder option tells the EPA system what the root folder of your environment configurations is. This parameter is combined with the environment option to find the correct config.json file.

The systemEnv option tells the EPA system what "system" environment variables to use. You should specify process.env unless you have a good reason not to.

Legal Mumbo Jumbo

Copyright © 2014 Muted Solutions, LLC. All Rights Reserved.

Distributed under the MIT license.