fix(core): added @angular/compiler as a peer dependency #55610
+6
−0
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.
This fixes an issue with packages managers likes pmpm that will not link the @angular/compiler package to the @angular/core package if it is not listed as a peer dependency.
I added it as optional peer dependency as it's only used in special cases.
Fixes #38096
PR Checklist
Please check if your PR fulfills the following requirements:
PR Type
What kind of change does this PR introduce?
What is the current behavior?
Today @angular/core/testing is using @angular/compiler without specifying it as a dependency.
This results in strict package managers like pnpm don't find the dependency.
Issue Number: #38096
What is the new behavior?
@angular/compiler is added as an optional peerDependency for @angular/core
Does this PR introduce a breaking change?
Other information