Skip to content

Conversation

@Deku-nattsu
Copy link
Contributor

PR Checklist

Please check to confirm your PR fulfills the following requirements:

PR Type

What kind of change does this PR introduce?

  • Bugfix
  • Feature
  • Code style update (formatting, local variables)
  • Refactoring (no functional changes, no api changes)
  • Build related changes
  • CI related changes
  • Documentation content changes
  • Other... Please describe:

What is the current behavior?

Issue Number: N/A

What is the new behavior?

Migrating from v20 to v21 causes both esModuleInterop and moduleResolution to be added again which isn't needed when module is set to preserve

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Copy link
Collaborator

@alan-agius4 alan-agius4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, just one NIT.

Would also be nice to add a test for this.

@alan-agius4 alan-agius4 added the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label Nov 21, 2025
@alan-agius4 alan-agius4 added the target: patch This PR is targeted for the next patch release label Nov 21, 2025
@Deku-nattsu
Copy link
Contributor Author

LGTM, just one NIT.

Would also be nice to add a test for this.

okay i'll try

@alan-agius4 alan-agius4 removed the action: cleanup The PR is in need of cleanup, either due to needing a rebase or in response to comments from reviews label Nov 21, 2025
@Deku-nattsu
Copy link
Contributor Author

@alan-agius4
Copy link
Collaborator

i used the same setup in https://github.com/angular/angular-cli/blob/main/packages/schematics/angular/migrations/update-module-resolution/migration_spec.ts#L109

Interesting, probably that could be cleaned up a bit hahaha.

Copy link
Collaborator

@alan-agius4 alan-agius4 left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

LGTM, thanks for your contribution.

@alan-agius4 alan-agius4 added the action: merge The PR is ready for merge by the caretaker label Nov 21, 2025
@dgp1130 dgp1130 merged commit 50d9c0e into angular:main Nov 21, 2025
35 checks passed
@dgp1130
Copy link
Collaborator

dgp1130 commented Nov 21, 2025

This PR was merged into the repository. The changes were merged into the following branches:

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.

3 participants