Skip to content
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

Update peer dependencies for angular 13 support #16758

Merged
merged 2 commits into from
Nov 23, 2021
Merged

Conversation

SnakeSVx
Copy link
Contributor

Issue: #16749

What I did

Update peer dependencies to support current angular versions 12/13.

How to test

  • Is this testable with Jest or Chromatic screenshots?
  • Does this need a new example in the kitchen sink apps?
  • Does this need an update to the documentation?

If your answer is yes to any of these, please make sure to include it in your PR.

- rxjs 7 (angular 13)
- build-angular version range change from angular 12
@nx-cloud
Copy link

nx-cloud bot commented Nov 22, 2021

Nx Cloud Report

CI ran the following commands for commit 5ec9ca1. Click to see the status, the terminal output, and the build insights.

📂 See all runs for this branch

Status Command
#000000 nx run-many --target=prepare --all --parallel --max-parallel=15

Sent with 💌 from NxCloud.

Copy link
Member

@shilman shilman left a comment

Choose a reason for hiding this comment

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

Thanks @SnakeSVx !!! 🙏

@literalpie per your comment on the issue, it looks like the CI is not failing any worse than it was before. since peer dependencies should "accept" whatever the user has already installed in their app/library i suspect that this is a safe change and am inclined to merge. but let me know if you think it's a bad idea!! 🙏

@shilman shilman added this to the 6.4 PRs milestone Nov 22, 2021
@literalpie
Copy link
Contributor

I don't think there's any reason not to merge this. Worst case scenario is that it only partially fixes the issue :-)

Copy link
Member

@kroeder kroeder left a comment

Choose a reason for hiding this comment

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

LGTM, besides the @angular/* >=6.0.0 we definitely should get rid of anytime soon. But it does not block this PR

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants