feat(@schematics/angular): allow application migration to use new build package in projects where possible #27520
Conversation
This file contains hidden or 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
…lication builder The `deployUrl` option is now supported with the new build system when using the `application` builder. The migration schematic no longer needs to remove the option if present.
clydin
force-pushed
the
application/cleanup-2
branch
from
5582122 to
95ce022
Compare
…ld package in projects where possible When using the optional application build system migration, the newly introduced `@angular/build` package which contains only the new build system and no Webpack-related dependencies will be directly used when possible. The migration will check for usage of any other builders from the `@angular-devkit/build-angular` package. if none are present in the `angular.json` file (excluding `dev-server` and `extract-i18n`), the `@angular/build` package will be added as a dependency and used in the `angular.json` file. The `@angular-devkit/build-angular` package will then be removed as a dependency. Project usage of karma and/or protractor will be the most common reasons this part of the migration will not be performed.
clydin
force-pushed
the
application/cleanup-2
branch
from
95ce022 to
094e85c
Compare
alan-agius4
approved these changes
Apr 24, 2024
|
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.
When using the optional application build system migration, the newly
introduced
@angular/buildpackage which contains only the new buildsystem and no Webpack-related dependencies will be directly used when
possible. The migration will check for usage of any other builders from
the
@angular-devkit/build-angularpackage. if none are present in theangular.jsonfile (excludingdev-serverandextract-i18n), the@angular/buildpackage will be added as a dependency and used in theangular.jsonfile. The@angular-devkit/build-angularpackage willthen be removed as a dependency. Project usage of karma and/or protractor
will be the most common reasons this part of the migration will not be
performed.
Also includes a fix to the migration to no longer remove the now support deployUrl option.