Type of Change
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.
export default {
logger: 'debug' | 'prod'
}
debug: extra (meaningful) console logging (user config, graph)prod: Just the basic status message we already see now
This would just be a more formal variation of https://greenwoodjs.dev/docs/reference/appendix/#environment-variables
Details
A good use case could be to disable / configure an Analytics plugin when developing vs building for production. Also, this could be used to enable additional debug logs?
Type of Change
Summary
As might be the case with certain plugins are other parts of Greenwood's build pipeline, having a
productionflag that is set during theconfiglifecycle based on whether it is adeveloporbuildCLI command.Basically, establish a way to enable different modes, e.g.
debug: extra (meaningful) console logging (user config, graph)prod: Just the basic status message we already see nowDetails
A good use case could be to disable / configure an Analytics plugin when developing vs building for production. Also, this could be used to enable additional debug logs?