feat(@schematics/angular): production builds by default #20128
Merged
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
alan-agius4
changed the title
alan-agius4
added
the
target: major
|
@alan-agius4 |
|
@destus90, yeah indeed, thanks for pointing that out. |
With this change we deprecated the `--prod` command line argument. This argument is confusing especially to new users, since users expect that this builds an application in production mode. This however, is only an alias for `--configuration="production"`
clydin
requested changes
Mar 9, 2021
clydin
approved these changes
Mar 9, 2021
With this change we do several changes to the `angular.json` configuration for `build` , `server` and `app-shell` targets so that these are `production` by default. - build, server and app-shell targets are configured to run production by default. - We add a new configuration named `development` to run the mentioned builder targets in development. Ex: `ng build --configuration development`. - When adding `universal` or `app-shell`, we generate the full set of configurations as per the `buiid` target. Previously, we only generated the `production` configuration. - We added a helper script in `package.json` to run build in watch mode. `npm run watch` which is a shortcut for `ng build --watch --configuration development`
jessicajaniuk
pushed a commit
to angular/angular
that referenced
this pull request
Mar 16, 2021
In CLI version 12, we introduced the concept of production builds by default. With this change we update the documentation to reflect the changes. More information about the change can be found angular/angular-cli#20128 PR Close #41173
|
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
With this change we do several changes to the
angular.jsonconfiguration forbuild,serverandapp-shelltargets.developmentto run the mentioned builder targets in development. Ex:ng build --configuration development.universalorapp-shell, we generate the full set of configurations as per thebuiidtarget. Previously, we only generated theproductionconfiguration.package.jsonto run build in watch mode.npm run watchwhich is a shortcut forng build --watch --configuration development--prodcommand line argument. This argument is confusing especially to new users, since users expect that this builds an application in production mode. This however, is only an alias for--configuration="production"Closes #14471