`--prod` ignored since CLI 5.3.0 (Cordova/Angular)

Description: Since upgrading to CLI 5.3.0, the ionic CLI will not run

ng run app:ionic-cordova-build:production

if being called with ionic cordova build ios --prod or ionic cordova build ios --configuration=production

Steps to Reproduce:

• Install the latest CLI
• Try to initiate a prod build
• Observe the CLI only calling ng run app:ionic-cordova-build --platform=ios

Output:

My ionic info:

Ionic:

   Ionic CLI                     : 5.3.0 (/Users/Wilk/.nvm/versions/node/v10.16.3/lib/node_modules/ionic)
   Ionic Framework               : @ionic/angular 4.9.0
   @angular-devkit/build-angular : 0.801.2
   @angular-devkit/schematics    : 8.1.1
   @angular/cli                  : 8.1.1
   @ionic/angular-toolkit        : 2.0.0

Cordova:

   Cordova CLI       : 8.1.2 (cordova-lib@8.1.1)
   Cordova Platforms : ios 5.0.1
   Cordova Plugins   : cordova-plugin-ionic-keyboard 2.2.0, cordova-plugin-ionic-webview 4.1.1, (and 5 other plugins)

Utility:

   cordova-res : 0.6.0 
   native-run  : 0.2.8 

System:

   Android SDK Tools : 25.2.2 (/Users/Wilk/Library/Android/sdk)
   ios-sim           : 8.0.2
   NodeJS            : v10.16.3 (/Users/Wilk/.nvm/versions/node/v10.16.3/bin/node)
   npm               : 6.9.0
   OS                : macOS Mojave
   Xcode             : Xcode 10.3 Build version 10G8

Other Information: This was really a showstopper for us, as this bug breaks our production builds using the Ionic CLI. Downgrading to 5.2.8 seems to work.

[imhoffd]

Thanks for the report! Looks like I missed something. The fix will be released shortly.

[wilk-polarny]

@l3ender , we usually use fixed versions - except for global dependencies (which in our case caused the issues after we upgraded it on our machines - lessons learned here). Project dependencies are pinned, though, as we have to verify each dependency and its dependencies in regards to compatibility, licensing and so on.

For Ionic projects, we usually stick to the ionic starter project deps as a base (combination of ionic + angular + other deps) because those are “known to work”.

Other people I know use caret ranges and obligatory package locks to ensure consistent builds across machines.

I would say, it also depends on the package you’re pulling in and whether package maintainers/devs actually get it right and don’t introduce breaking changes with minor or patch versions. No risk, no fun.