Skip to content

fix(@schematics/angular): drop composite in tsconfig #30125

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
Apr 18, 2025

Conversation

cexbrayat
Copy link
Member

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?

Based on this TS discussion, composite is in fact not necessary, the TS docs are just misleading.

What is the new behavior?

This removes composite from the configs, as it was recently done in create-vue (see vuejs/create-vue#635).

Does this PR introduce a breaking change?

  • Yes
  • No

Other information

Based on this [TS discussion](microsoft/TypeScript#60465), `composite` is in fact not necessary, the TS docs are just misleading.
@clydin clydin added action: merge The PR is ready for merge by the caretaker target: major This PR is targeted for the next major release labels Apr 18, 2025
@clydin clydin merged commit 672ae14 into angular:main Apr 18, 2025
33 checks passed
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