Feature: Added support for key value mapping in env vars file
Feature: Added support for inline comments ENV=VALUE # inline comment
Change: Will now ignore invalid lines in env vars file instead of throwing an error
Change: Migrated all the parsing over to regex since the file format is simple enough right now to support that
Bug: Removed old test cases for the -e/--env flags that were not needed anymore

Readme

Source

env-cmd

A simple node program for executing commands using an environment from an env file.

Install

npm install env-cmd

Usage

Environment file ./test/.env

# This is a comment
ENV1=THANKS # Yay inline comments support
ENV2=FOR ALL
ENV3 THE FISH # This format is also accepted

Package.json

{
  "scripts": {
    "test": "env-cmd ./test/.env mocha -R spec"
  }
}

Terminal

./node_modules/.bin/env-cmd ./test/.env node index.js

Environment File Formats

These are the currently accepted environment file formats. If any other formats are desired please create an issue.

key=value
key value

Why

Because sometimes its just too cumbersome passing lots of environment variables to scripts. Its usually just easier to have a file with all the vars in them, especially for development and testing.

Do not commit sensitive environment data to a public git repo!

cross-env - Cross platform setting of environment scripts

Special Thanks

Special thanks to cross-env for inspiration (use's the same cross-spawn lib underneath too).

Keywords

FAQs

What is env-cmd?

Is env-cmd popular?

Is env-cmd well maintained?

Last updated on 18 Aug 2016

Did you know?

Socket for GitHub automatically highlights issues in each pull request and monitors the health of all your open source dependencies. Discover the contents of your packages and block harmful activity before you install or update your dependencies.

Install