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

multi-env

v2.0.0

Published

Merges and loads environment variables from multiple .env files for nodejs projects.

Downloads

202

Readme

multi-env

npm version Build Status codecov Greenkeeper badge

Multi-env merges and loads environment variables from multiple .env files for nodejs projects.

Multi-env is built on dotenv and follows the same rules.

Installation

npm install --save multi-env

Configuration

Add configuration for multi-env to your package.json:

{
  "name": "my-package",
  "version": "0.1.0",
  "scripts": {
    "start": "node ./src/index.js"
  },
  "config": {
    "multi-env": {
      "files": [
        "local.env",
        "shared.env"
      ]
    }
  }
}

files should be an array of .env file paths (relative to package.json).

When the same variable is assigned in multiple files, the earliest file listed in your configuration will take precedence. Environment variables that have already been set will never be modified.

Usage

In Application Code

// src/index.js
require('multi-env')();

console.info(process.env.MY_VARIABLE_FROM_DOTENV);

...

Preload

You can use the node --require (-r) command line option to preload multi-env. By doing this, you do not need to require and execute multi-env in your application code.

{
  "name": "my-package",
  "version": "0.1.0",
  "scripts": {
    "start": "node -r multi-env/config ./src/index.js"
  },
  "config": {
    "multi-env": {
      "files": [
        "local.env",
        "shared.env"
      ]
    }
  }
}
// src/index.js
console.info(process.env.MY_VARIABLE_FROM_DOTENV);

...