@datorama/if-env

1.0.0 • Public • Published

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

2. 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

Readme

Keywords

Package Sidebar

Install

npm i @datorama/if-env

Weekly Downloads

0

Version

1.0.0

License

MIT

Unpacked Size

5.36 kB

Total Files

8

Last publish

Collaborators

  • mohamadhusari
  • natassor
  • ebelenki
  • meireliezer-salesforce
  • rsvilemshema
  • omilitscher
  • bdimand
  • mperets
  • ssegal
  • maliperlman
  • distroy123
  • aavgil
  • ori007
  • yonatanlevy
  • jmeguira
  • abh86
  • keinans
  • gurdotan
  • org86
  • iglikman
  • ashakked
  • lron
  • samerkinaan
  • amitb
  • nhaimov
  • eliran.aharoni
  • ritox
  • ofirb25
  • yousef.baba
  • netbasal
  • kaufguy
  • idafna