if-env

Simplify npm scripts with "if-env ... && npm run this || npm run that"

  • if-env
  • Loading similar packages

Downloads in past

Stats

StarsIssuesVersionUpdatedCreatedSize
if-env
1.0.46 years ago8 years agoMinified + gzip package size for if-env in KB

Popular Searches

Readme

if-env
Simplify npm scripts with if-env ... && npm run this || npm run that

    • -

I recommend switching to per-env, which is much simpler and much more powerful!
    • -

Suppose you want to simplify development and be able to run npm start in all environments & run the correct scripts.
Your package.json might look like this:
"scripts": {
  "start": "if [[ ${NODE_ENV} == \"production\" ]]; then npm run start:prod; else npm run start:dev; fi",
  "start:dev": "webpack",
  "start:prod": "start-cluster"
}

The problem is, this doesn't work in all environments.
Instead, you can write:
"scripts": {
  "start": "if-env NODE_ENV=production && npm run start:prod || npm run start:dev",
  "start:dev": "webpack",
  "start:prod": "start-cluster"
}

Usage

  1. Install

$ npm install if-env --save

  1. Add to package.json

"scripts": {
  "start": "if-env SOME_ENV_VAR=some_val ANOTHER_ENV_VAR=another_val && npm run this || npm run that"
}

License

MIT © Eric Clemmons 2015