From f16ecc07663dee3739a8d5e18ab70ee1a9465c0a Mon Sep 17 00:00:00 2001
From: Alex Mikhalev <alexmikhalevalex@gmail.com>
Date: Mon, 3 Sep 2018 18:07:30 -0600
Subject: [PATCH] fix: Don't use NODE_ENV in webpack build

---
 client/env.js | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/client/env.js b/client/env.js
index cf7b349..4f9c998 100644
--- a/client/env.js
+++ b/client/env.js
@@ -49,7 +49,7 @@ exports.getClientEnvironment = function getClientEnvironment(env, publicUrl) {
       }, {
         // Useful for determining whether we’re running in production mode.
         // Most importantly, it switches React into the correct mode.
-        NODE_ENV: process.env.NODE_ENV || env,
+        NODE_ENV: env,
         // Useful for resolving the correct path to static assets in `public`.
         // For example, <img src={process.env.PUBLIC_URL + "/img/logo.png"} />.
         // This should only be used as an escape hatch. Normally you would put