Enable a development / production mode flag

[thescientist13]

Type of Change

• New Feature Request
• Documentation / Website
• Improvement / Suggestion
• Bug
• Other (please clarify below)

Summary

As might be the case with certain plugins are other parts of Greenwood's build pipeline, having a production flag that is set during the config lifecycle based on whether it is a develop or build CLI command.

Basically, establish a way to enable different modes, e.g.

# prod mode by default
$ greenwood --mode=debug|develop|prod 

• debug: extra (meaningful) console logging (user config, graph) and writing out to files
• develop: extra console logging like in debug mode but no writing out to files
• prod: Just the basic status message we already see now

Details

A good use case would be disabling the Analytics plugin when developing, and thus only enabling it when building for production.

module.exports = (options = {}) => {
  ...

  return [{
    type: 'index',
    provider: (compilation) => {
      const hook = !compilation.config.production
        ? ''
        : `
            <script async src="https://www.googletagmanager.com/gtag/js?id=${analyticsId}"></script>
          
            <script>
              window.dataLayer = window.dataLayer || [];
              function gtag(){dataLayer.push(arguments);}
              gtag('js', new Date());

              gtag('config', '${analyticsId}', { 'anonymize_ip': ${trackAnon} });
              gtag('config', '${analyticsId}');
            </script>
          `
      };
     
     return {
       hookGreenwoodAnalytics: hook
     }
  }];
};

[thescientist13]

As part of #355 this was simply done as an environment variable, but ideally this should be a little more ergonomic / less mutable.