On https://angular.io/cli/build, it says:
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?
Hi, --prod is an alias for --configuration=production and there is nothing more to it.
There is currently a PR to improve this doc https://github.com/angular/angular-cli/pull/12837
That's a speedy response, much appreciated!
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
_This action has been performed automatically by a bot._
Most helpful comment
Hi,
--prodis an alias for--configuration=productionand there is nothing more to it.There is currently a PR to improve this doc https://github.com/angular/angular-cli/pull/12837