Some tasks may need the NODE_ENV variable set to "production" in order for various plugins to produce production-ready output. Task configs can now have an optional environment property that the task runner will use to set NODE_ENV variable when that task is run:
{ name: 'export', environment: 'production' }
Interested to know what you guys think about this idea and/or the naming convention I used for the property.
Some tasks may need the NODE_ENV variable set to "production" in order for various plugins to produce production-ready output. Task configs can now have an optional
environmentproperty that the task runner will use to set NODE_ENV variable when that task is run:{ name: 'export', environment: 'production' }Interested to know what you guys think about this idea and/or the naming convention I used for the property.