Skip to content

Conversation

@clydin
Copy link
Member

@clydin clydin commented Oct 22, 2025

The Angular CLI will default to using the correct builder for i18n extraction if the target definition is not present in a project. This allows for a reduced amount of preset configuration for new projects. The i18n-extract is only needed when using the @angular/localize project and can be added when it is used. Most options for the target are also command line oriented which makes the target definition unused in many cases.

…ojects

The Angular CLI will default to using the correct builder for i18n extraction
if the target definition is not present in a project. This allows for a reduced
amount of preset configuration for new projects. The `i18n-extract` is only needed
when using the `@angular/localize` project and can be added when it is
used. Most options for the target are also command line oriented which makes
the target definition unused in many cases.
@clydin clydin added the target: major This PR is targeted for the next major release label Oct 22, 2025
@clydin clydin added the action: review The PR is still awaiting reviews from at least one requested reviewer label Oct 22, 2025
@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 Oct 22, 2025
@clydin clydin merged commit b524ba4 into angular:main Oct 22, 2025
35 checks passed
@clydin clydin deleted the ng-new/empty-i18n-extract branch October 22, 2025 16:41
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

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

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants