Fixes #7 - Default NODE_ENV to production and allow it to be set by users

Author: bryceosterhaus

packages/liferay-npm-scripts/README.md

@@ -82,3 +82,9 @@ If you need to add additional configuration you can do so by creating a `.lifera
 If you need more flexibility over babel or the bundler. You can still add a `.babelrc` or `.npmbundlerrc` which will be merged with the default settings this tool provides. [Default Babel Config](./src/config/babel.json), [Default Bundler Config](./src/config/npm-bundler.json)
 
 For more control over `lint` and `format`, follow the configuration options [here](https://github.com/liferay/liferay-frontend-source-formatter#custom-configuration)
+
+Want to use a different `NODE_ENV`? Try doing something like
+
+```sh
+NODE_ENV=development liferay-npm-scripts build
+```

packages/liferay-npm-scripts/src/index.js

@@ -1,3 +1,8 @@
+// Do this as the first thing so that any code reading it knows the right env.
+if (!process.env.NODE_ENV) {
+	process.env.NODE_ENV = 'production';
+}
+
 const fs = require('fs');
 const minimist = require('minimist');
 const inquirer = require('inquirer');

packages/liferay-npm-scripts/src/scripts/build.js

@@ -1,7 +1,3 @@
-// Do this as the first thing so that any code reading it knows the right env.
-process.env.BABEL_ENV = 'production';
-process.env.NODE_ENV = 'production';
-
 const CWD = process.cwd();
 
 const spawnSync = require('../utils/spawnSync');