fix(@schematics/angular): remove karma config devkit package usages during application migration #30415
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 performing an
ng update
to Angular v20, the application migration will detect the usage of thekarma
builder'skarmaConfig
option and attempt to remove usages of the no longer needed@angular-devkit/build-angular
karma framework and plugin usage. While the karma framework usage will be specifically ignored when using the@angular/build:karma
builder, the plugin usage leverages a directrequire
within the configuration file. Regardless of the ability of the builder to ignore, neither usage is needed with@angular/build:karma
and removing the code aligns with what would be generated byng generate config karma
.Closes #30413