Skip to content

Conversation

@clydin
Copy link
Member

@clydin clydin commented Feb 20, 2025

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.

@clydin clydin marked this pull request as ready for review February 20, 2025 18:02
@clydin clydin added the target: rc This PR is targeted for the next release-candidate label Feb 20, 2025
@clydin clydin force-pushed the schematics/app-support-improvements branch 3 times, most recently from 9820e26 to 94b86b1 Compare February 20, 2025 18:52
@clydin clydin added the action: review The PR is still awaiting reviews from at least one requested reviewer label Feb 20, 2025
@clydin clydin requested a review from dgp1130 February 20, 2025 19:03
ExtractI18n = '@angular-devkit/build-angular:extract-i18n',
BuildExtractI18n = '@angular/build:extract-i18n',
Protractor = '@angular-devkit/build-angular:private-protractor',
BuildApplication = '@angular/build:application',
Copy link
Collaborator

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.

Copy link
Member Author

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.
@clydin clydin force-pushed the schematics/app-support-improvements branch from 94b86b1 to 061b657 Compare February 24, 2025 22:24
@clydin clydin added action: merge The PR is ready for merge by the caretaker and removed action: review The PR is still awaiting reviews from at least one requested reviewer labels Feb 24, 2025
@clydin clydin merged commit 1b43c05 into angular:main Feb 24, 2025
31 checks passed
@clydin
Copy link
Member Author

clydin commented Feb 24, 2025

The changes were merged into the following branches: main, 19.2.x

@clydin clydin deleted the schematics/app-support-improvements branch February 24, 2025 23:34
@angular-automatic-lock-bot
Copy link

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.

@angular-automatic-lock-bot angular-automatic-lock-bot bot locked and limited conversation to collaborators Mar 27, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

action: merge The PR is ready for merge by the caretaker area: @schematics/angular target: rc This PR is targeted for the next release-candidate

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants