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 🙏

© 2025 – Pkg Stats / Ryan Hefner

multi-env-config

v0.1.6

Published

Multi environment configuration

Readme

Multi env config

Multiple environment configuration file.

Install

npm install multi-env-config --save

Init

First you need to initialize the module using the following code in your main/start javascript file (for exemple, "index.js"):

const config = require('multi-env-config').init();

The module expects configuration files in "./src/Config" directory relative to the project's base path.

The configuration file name must be the value assigned to "NODE_ENV" environment variable plus ".js".

Alternatively, you can initialize the module specifying your environment variable - in case you have many node instances in the same machine - and the directory of the configuration files.

For example, in the following initialization...

const config = require('multi-env-config').init('MY_PROJECT_NODE_ENV', './src/configuration');

... if your MY_PROJECT_NODE_ENV environment variable has the value "development" the module will look for a "development.js" file in the "./src/configuration" directory.

Usage

When you need to access some property of you configuration file just use:

const config = require('multi-env-config');

For example, if your "development.js" file has the following data:

module.exports = {
	database: {
		server: '192.168.0.10',
		user: 'root',
		password: '123456'
	}
}

you can access the data as following:

const config = require('multi-env-config');
let server = config.database.server;
let user = config.database.user;