You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
When true, sets the build configuration to the production environment.
All builds make use of bundling and limited tree-shaking.
A production build also runs limited dead code elimination using UglifyJS.
Which begins to explain one thing and then changes subjects, while using old name convention (environment vs configuration). Now, in new CLI, with angular.json, it would seem to me, that all configuration specifies its own build parameters and it is controlled from there. Are there other "optimizations" connected solely to --prod switch, that are not in angular.json?
Is --prod:
a) just an alias for --configuration=production
b) an alias for --configuration=production, as well as flag for other optimizations, that are not connected to what is specified in angular.json file?
The text was updated successfully, but these errors were encountered:
sebastian-zarzycki-apzumi
changed the title
The difference between ng build --prod and ng-build --configuration=production is unclear.
The difference between ng build --prod and ng build --configuration=production is unclear.
Nov 8, 2018
On https://angular.io/cli/build, it says:
Which begins to explain one thing and then changes subjects, while using old name convention (environment vs configuration). Now, in new CLI, with angular.json, it would seem to me, that all configuration specifies its own build parameters and it is controlled from there. Are there other "optimizations" connected solely to --prod switch, that are not in angular.json?
Is --prod:
a) just an alias for --configuration=production
b) an alias for --configuration=production, as well as flag for other optimizations, that are not connected to what is specified in angular.json file?
The text was updated successfully, but these errors were encountered: