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
Support for rxjs 7 #41897
Comments
Before update to RXJS 7.0, the framework needs to be compatible. Transferring to the FW repo to keep tracking this. |
rxjs v7 won't be stable for v12, so it won't be included by default. Related: #41590 |
@jelbourn, actually rxjs 7.0.0 was released 1 day before you said that. Were you not aware of that release at that time or did you mean that rxjs 7 support in Angular won't be stable enough for v12 ? |
v12's first Release Candidate (rc0) was cut 2 weeks ago. After that, the versions of dependencies such as RxJS are generally fixed. Note that this doesn't mean you can't use RxJS 7 with Angular v12 - changes such as #41590 will still land to ensure the framework is compatible with the new RxJS. We just can't change the default/minimum required version until v13, as doing so is a breaking change for users and we don't merge such changes in the RC period. |
Yeah, it caught me by surprise- I wasn't expecting it until after v12 since there are still outstanding issues w/ v7 inside Google. |
I had read somewhere that V7 was good to go on V12, hmm. ➜ client git:(master) ✗ npm i npm ERR! A complete log of this run can be found in: |
Angular 12 with rxjs 7.0.1 could be built and run, however, the VS IDE could not check reference. And tsconfig with strict=true has NG CLI complaining no reference to rxjs could be found and suggesting downloading type info. |
Now that RXJS v7.1 is out, can we expect Angular v12.1.0 to start using it? This new RXJS is so much better and smaller, it will be a shame not to start using it with v12 of Angular. |
|
We can't update the minimum required version of rxjs until Angular 13, because rxjs version 7 includes breaking changes. We're exploring how to support both 6 and 7 for projects that want to opt into it earlier. |
@crisbeto thank you! It would be great to be able to use RxJS 7. It brings so many benefits. |
This comment has been minimized.
This comment has been minimized.
We can't update the framework to rxjs7 until version 13, because it contains breaking changes, but we can allow users to opt into it since all of our code should be compatible. These changes expand the allowed version range of rxjs and add an integration test to verify that we don't get compilation errors. Note that we also have a test that runs the AIO examples against rxjs 7 already (angular#42660). Fixes angular#41897.
We can't update the framework to rxjs7 until version 13, because it contains breaking changes, but we can allow users to opt into it since all of our code should be compatible. These changes expand the allowed version range of rxjs and add an integration test to verify that we don't get compilation errors. Note that we also have a test that runs the AIO examples against rxjs 7 already (angular#42660). Fixes angular#41897.
We can't update the framework to rxjs7 until version 13, because it contains breaking changes, but we can allow users to opt into it since all of our code should be compatible. These changes expand the allowed version range of rxjs and add an integration test to verify that we don't get compilation errors. Note that we also have a test that runs the AIO examples against rxjs 7 already (angular#42660). Fixes angular#41897.
We can't update the framework to rxjs7 until version 13, because it contains breaking changes, but we can allow users to opt into it since all of our code should be compatible. These changes expand the allowed version range of rxjs and add an integration test to verify that we don't get compilation errors. Note that we also have a test that runs the AIO examples against rxjs 7 already (angular#42660). Fixes angular#41897.
We can't update the framework to rxjs7 until version 13, because it contains breaking changes, but we can allow users to opt into it since all of our code should be compatible. These changes expand the allowed version range of rxjs and add an integration test to verify that we don't get compilation errors. Note that we also have a test that runs the AIO examples against rxjs 7 already (#42660). Fixes #41897. PR Close #42991
I'm still getting incompatible peer dependency errors for @angular/cdk and @angular/material when using RxJS 7:
|
Ah, we never bumped the allowed version on the non-core packages. I'll do it now. |
If you simply update angular packages then install rxjs 7, it would just work fine. Given that you are still on node 14 and npm 6. It would probably have issues on npm 7 |
@princemaple |
This issue has been automatically locked due to inactivity. Read more about our automatic conversation locking policy. This action has been performed automatically by a bot. |
We can't update the framework to rxjs7 until version 13, because it contains breaking changes, but we can allow users to opt into it since all of our code should be compatible. These changes expand the allowed version range of rxjs and add an integration test to verify that we don't get compilation errors. Note that we also have a test that runs the AIO examples against rxjs 7 already (angular#42660). Fixes angular#41897. PR Close angular#42991
We can't update the framework to rxjs7 until version 13, because it contains breaking changes, but we can allow users to opt into it since all of our code should be compatible. These changes expand the allowed version range of rxjs and add an integration test to verify that we don't get compilation errors. Note that we also have a test that runs the AIO examples against rxjs 7 already (angular#42660). Fixes angular#41897. PR Close angular#42991
Description
Angular 12 workspace comes bundled with rxjs
6.6.0
❯ npx @angular/cli@12.0.0-rc.1 new web-apps --create-application false --skip-install
Describe the solution you'd like
Angular 12 workspace should come bundled with rxjs 7
RxJS 7 Slides: https://docs.google.com/presentation/d/1-LU7YE3NWw8jHeAgdmLu4CBfG7osCx6MsSIeFs16k60
I see pull request angular/angular-cli#20669 was closed recently.
The text was updated successfully, but these errors were encountered: