-
Notifications
You must be signed in to change notification settings - Fork 11.9k
fix(@schematics/angular): add additional checks for application builder usage #29687
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
fix(@schematics/angular): add additional checks for application builder usage #29687
Conversation
9820e26 to
94b86b1
Compare
| ExtractI18n = '@angular-devkit/build-angular:extract-i18n', | ||
| BuildExtractI18n = '@angular/build:extract-i18n', | ||
| Protractor = '@angular-devkit/build-angular:private-protractor', | ||
| BuildApplication = '@angular/build:application', |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Consider: I see that X and BuildX is an existing convention, but I wonder if it would be worth renaming the existing ones to DevkitX, XDevkit, or something similar to be more clear about the distinction between them.
Alternatively we could potentially drop the BuildX prefix with that being the "default" option we want to use, with DevkitX being the legacy versions.
If we do make this change, it's probably worth a separate PR, but something to think about.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
While these are "internal", they have been and probably still are used by third-party custom schematics. This makes more comprehensive changes problematic. I do like the Devkit variation though.
…er usage The Angular schematics have been updated to perform additional checks for both the `@angular-devkit/build-angular:application` and `@angular/build:application` builders. This ensures that the schematics generate the appropriate output for each of these build systems in addition to the Webpack-based `browser` builder.
94b86b1 to
061b657
Compare
|
The changes were merged into the following branches: main, 19.2.x |
|
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. |
The Angular schematics have been updated to perform additional checks for both the
@angular-devkit/build-angular:applicationand@angular/build:applicationbuilders. This ensures that the schematics generate the appropriate output for each of these build systems in addition to the Webpack-basedbrowserbuilder.