Closed victorporof closed 7 years ago
As discussed, there's only 3 places we're checking for NODE_ENV at the moment in webpacked code (command-line.js, configure-store.js and btn.jsx), and all are correct except for the one mentioned in https://github.com/mozilla/tofino/issues/1369. Upon further consideration, no real reason to keep this open, better documentation will help.
Everything that is necessary should be in the build config. The necessity of having build config properties to determine whether or not we're running in production or development have been discussed before and can be reiterated if needed.
The
NODE_ENV.TEST
flag is different because testing can happen for both production and development builds, and we don't want to perform rebuilds just because we're running tests (so this shouldn't live in the build config).