You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
AngularFire needed a lot of work. v21 rc.1 release candidate is released. I'm now working in on v22. I wish I could give you a date on that, but I can say that most of the hard work on getting AngularFire in shape has been done, so I think v22 should be coming sooner rather than later.
I'm particularly looking forward to finishing the proper TransferState wiring by default in AngularFire-wrapped functions. That clearly needs to happen.
I apologize for the lack of communication since I've taken over as a maintainer recently, for various reasons. I expect to be more communicative going forward.
Angular 22 support is currently available in our canary builds. See the AngularFire 22 canary upgrade guide if you'd like to try this out before the first release candidate.
I expect the first 22 release candidate by the end of next week, assuming all goes well. I'm hoping to put out 22 release candidates out every week or so after that.
The goal is to get out proper Angular 22 support in the first release candidate, with all necessary and beneficial breaking changes in the second release candidate (since breaking changes should generally be avoided outside of a major release).
Once those are in, and the second release candidate has been available for the public to try out for a couple weeks, we'll cut the AngularFire 22.0.0 release.
At that point, I intend to focus on both bug fixes and new features. For example, offering signal-based APIs, improving SSR support, and getting the docs into shape, to say the least. I'm looking forward to community input on what non-breaking features people would like to see.
AngularFire 22.0.0-rc.0 is out, the first AngularFire 22 release candidate. It supports Angular 22 and is on npm's next tag. View the release notes for what changed, including two breaking changes: Angular 22 and TypeScript 6 are required, and your app now owns the firebase dependency.
To upgrade an app on Angular 21 and AngularFire 21, run:
ng update @angular/core@22 @angular/cli@22 @angular/fire@next
On a new Angular 22 app, run ng add @angular/fire@next. The AngularFire 22 Upgrade Guide covers the details, including which command to run if you are on a 22 canary build.
As I said above, the remaining breaking changes are planned for the second release candidate. Create an issue for anything that breaks on this one. I'll keep this issue open until 22.0.0 ships.
Activity
armando-navarro commentedon Sep 17, 2026
AngularFire needed a lot of work. v21 rc.1 release candidate is released. I'm now working in on v22. I wish I could give you a date on that, but I can say that most of the hard work on getting AngularFire in shape has been done, so I think v22 should be coming sooner rather than later.
I'm particularly looking forward to finishing the proper TransferState wiring by default in AngularFire-wrapped functions. That clearly needs to happen.
I apologize for the lack of communication since I've taken over as a maintainer recently, for various reasons. I expect to be more communicative going forward.
Related: #3699 (comment)
rubenheymans commentedon Sep 25, 2026
if you can go zoneless it's not difficult to go with native firebase now, using claude code I managed to do it on a medium sized project
build!: require Angular 22 and compile with TypeScript 6 (#3801)
armando-navarro commentedon Oct 24, 2026
Angular 22 support is currently available in our canary builds. See the AngularFire 22 canary upgrade guide if you'd like to try this out before the first release candidate.
I expect the first 22 release candidate by the end of next week, assuming all goes well. I'm hoping to put out 22 release candidates out every week or so after that.
The goal is to get out proper Angular 22 support in the first release candidate, with all necessary and beneficial breaking changes in the second release candidate (since breaking changes should generally be avoided outside of a major release).
Once those are in, and the second release candidate has been available for the public to try out for a couple weeks, we'll cut the AngularFire 22.0.0 release.
At that point, I intend to focus on both bug fixes and new features. For example, offering signal-based APIs, improving SSR support, and getting the docs into shape, to say the least. I'm looking forward to community input on what non-breaking features people would like to see.
docs: split the canary upgrade note by canary version
docs: write the v22 upgrade guide for the release candidate (#3824)
armando-navarro commentedon Oct 29, 2026
AngularFire
22.0.0-rc.0is out, the first AngularFire 22 release candidate. It supports Angular 22 and is on npm'snexttag. View the release notes for what changed, including two breaking changes: Angular 22 and TypeScript 6 are required, and your app now owns thefirebasedependency.To upgrade an app on Angular 21 and AngularFire 21, run:
On a new Angular 22 app, run
ng add @angular/fire@next. The AngularFire 22 Upgrade Guide covers the details, including which command to run if you are on a 22 canary build.As I said above, the remaining breaking changes are planned for the second release candidate. Create an issue for anything that breaks on this one. I'll keep this issue open until 22.0.0 ships.