Skip to content

fix(@schematics/angular): remove karma config devkit package usages during application migration #30415

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

Merged
merged 1 commit into from
May 29, 2025

Conversation

clydin
Copy link
Member

@clydin clydin commented May 29, 2025

When performing an ng update to Angular v20, the application migration will detect the usage of the karma builder's karmaConfig 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 direct require 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 by ng generate config karma.

Closes #30413

@clydin clydin added the target: patch This PR is targeted for the next patch release label May 29, 2025
@clydin clydin force-pushed the update/karma-config-application branch from a2856a2 to 3c2461e Compare May 29, 2025 16:08
@clydin clydin marked this pull request as ready for review May 29, 2025 16:28
…uring application migration

When performing an `ng update` to Angular v20, the application migration
will detect the usage of the `karma` builder's `karmaConfig` 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 direct `require` 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 by `ng generate config karma`.
@clydin clydin force-pushed the update/karma-config-application branch from 3c2461e to 4075d2b Compare May 29, 2025 18:15
@clydin clydin added the action: merge The PR is ready for merge by the caretaker label May 29, 2025
@clydin clydin merged commit a2aba4c into angular:main May 29, 2025
54 of 55 checks passed
@clydin
Copy link
Member Author

clydin commented May 29, 2025

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

@clydin clydin deleted the update/karma-config-application branch May 29, 2025 20:54
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: patch This PR is targeted for the next patch release
Projects
None yet
Development

Successfully merging this pull request may close these issues.

after upgrade to 20 tests fail
2 participants