What happened to @angular/fire v21?

I noticed that @angular/fire 21.0.0-rc.0 was released about seven months ago, but there haven't been any updates since then.

Could you provide an update on the current status of the project? Is it still actively maintained, or has development been put on hold or abandoned?

Hi folks, I've been tasked with getting AngularFire back in sync with the latest Angular versions. I'm starting with v21, and will move to v22 after that.

Wrapping the Firebase SDK for zone.js change detection was an important feature of AngularFire. AngularFire’s zone wrapper has already been rebuilt on Angular's zoneless-era primitives. Even though Zoneless is now the default in Angular, AngularFire still solves a number of other common use cases.

That includes integration with PendingTasks so SSR/hydration wait for your data, preservation of injection context across Firebase’s async callbacks, dependency injection and lazy loading of Firebase SDKs, observable bindings, router auth guar…

it turns out you no longer need angularfire after v20 (zoneless) of Angular

use the firebase js sdk directly, here's a PR showing how I did this recently markgoho/doula-cooperative#89

it turns out you no longer need angularfire after v20 (zoneless) of Angular

use the firebase js sdk directly, here's a PR showing how I did this recently markgoho/doula-cooperative#89

Thank you very much for your reply and for sharing the guide with me.

However, I'm curious about the reasons behind this decision. More importantly, since this is an official library, I'm wondering why there hasn't been any official announcement, explanation, or migration guide to inform the developer community.

Was the project simply abandoned without any communication?!

It's not an official decision, unfortunately, I think based on the idea that Angular Fire was created to allow Firebase to be used on top of Angular's Zone.js + observable system and Angular has gone zoneless and is shifting (almost entirely?) to signals, this library is no longer needed.

I've reached out to all of the people I know who've supported this project over the years and did hear back from Minko who mentioned someone from the Angular team would be checking in. But, again, for anyone using Angular 20 and can use zoneless, this library is unnecessary. So from a resourcing standpoint, we're asking the Angular team to support a library that's only needed for Angular 19 and below. That's Angular from late 2024 and earlier.

My gut tells me folks on Angular 19 and below are going to be fine because they have a fully supported version of Angular fire and folks on Angular 20 and above need to drop this library and use the Firebase SDK.

@markgoho

It's not an official decision, unfortunately, I think based on the idea that Angular Fire was created to allow Firebase to be used on top of Angular's Zone.js + observable system and Angular has gone zoneless and is shifting (almost entirely?) to signals, this library is no longer needed.

I've reached out to all of the people I know who've supported this project over the years and did hear back from Minko who mentioned someone from the Angular team would be checking in. But, again, for anyone using Angular 20 and can use zoneless, this library is unnecessary. So from a resourcing standpoint, we're asking the Angular team to support a library that's only needed for Angular 19 and below. That's Angular from late 2024 and earlier.

My gut tells me folks on Angular 19 and below are going to be fine because they have a fully supported version of Angular fire and folks on Angular 20 and above need to drop this library and use the Firebase SDK.

Thank you again so much for your rep @markgoho , and for taking the time to reach out to the Angular team and get feedback directly from them.

Beyond the technical aspects—which I find very interesting and would love to learn more about—what left me somewhat puzzled was the lack of transparency. That's something I might expect from a library maintained by a hobbyist team, but not from the Angular team itself.

Hi folks, I've been tasked with getting AngularFire back in sync with the latest Angular versions. I'm starting with v21, and will move to v22 after that.

Wrapping the Firebase SDK for zone.js change detection was an important feature of AngularFire. AngularFire’s zone wrapper has already been rebuilt on Angular's zoneless-era primitives. Even though Zoneless is now the default in Angular, AngularFire still solves a number of other common use cases.

That includes integration with PendingTasks so SSR/hydration wait for your data, preservation of injection context across Firebase’s async callbacks, dependency injection and lazy loading of Firebase SDKs, observable bindings, router auth guards, analytics integration with Angular’s router, Angular CLI integration, and more.

I appreciate your patience as I work on getting this library back up to date.

@armando-navarro

Thank you @armando-navarro for the response and the detailed explanation.
I greatly appreciate the time and effort you are investing to ensure compatibility with the latest versions of the framework.
Keep up the great work!

Hi folks, I've been tasked with getting AngularFire back in sync with the latest Angular versions. I'm starting with v21, and will move to v22 after that.

Wrapping the Firebase SDK for zone.js change detection was an important feature of AngularFire. AngularFire’s zone wrapper has already been rebuilt on Angular's zoneless-era primitives. Even though Zoneless is now the default in Angular, AngularFire still solves a number of other common use cases.

That includes integration with PendingTasks so SSR/hydration wait for your data, preservation of injection context across Firebase’s async callbacks, dependency injection and lazy loading of Firebase SDKs, observable bindings, router auth guards, analytics integration with Angular’s router, Angular CLI integration, and more.

I appreciate your patience as I work on getting this library back up to date.

Great news, especially since firebaseui-web depends on this. Are you going to sync releases?

A production-use detail from an Angular 22 migration evaluation: our application uses provideAnalytics(() => getAnalytics()) and registers ScreenTrackingService and UserTrackingService.

The currently published @angular/fire@21.0.0-rc.0 still references ComponentFactoryResolver from @angular/core in its analytics declarations and generated provider metadata. Angular 22 removed that symbol, so the suggested workaround of dropping Analytics is not viable for us.

We completed an isolated Angular 22 / Nx 23 migration with the other stale peer ranges bridged by narrowly scoped npm overrides. The deterministic test/build suite passed, but TypeScript skipLibCheck means that result does not prove this Analytics runtime path safe.

Could the Angular 22 update include both an official ^22 peer range and a replacement for the Analytics screen-tracking dependency on ComponentFactoryResolver? This is the remaining blocker for us to adopt Angular 22 without knowingly carrying an unsupported runtime path.

Great news, especially since firebaseui-web depends on this. Are you going to sync releases?

Yes, firebaseui-web will pick up new versions of AngularFire once we publish them.

@armando-navarro

LTS EOL for Angular V20 is coming. Do you still think that you will be able to deliver an AngularFire V21 before @armando-navarro ?

I don't want to put any rush, just want to facilitate communication with the community so everybody can prepare their schedule 😉

@RignonNoel

@RignonNoel I do expect AngularFire v21 will be ready before the Angular 20 LTS-end date.

The AngularFire 21.0.0-rc.1 is mostly ready. Once #3763 and #3751 are merged, we'll tag it.

In the meantime, feel free to try out the published canary builds, which contain everything currently on main. I believe the latest canary build is reliable, but if you find any problems, please create an issue.

Please let me know of any issues or deficiencies. My goal is to get this repo back in shape again.

Also, I've updated docs (though they do need more updating), to include an AngularFire 21 Upgrade Guide

@armando-navarro

Thank you very much @armando-navarro :-)

@armando-navarro

@armando-navarro Sorry for the ping, but I am looking forward towards improving the docs, do we have some discussion (the tab in this repo) to checkout what needs to be reworked or made from zero? I don't want to open a issue for that 👍

@santonini82

@santonini82 AngularFire 21.0.0-rc.1 has been released. View the release notes for details on what's changed.

I've updated the AngularFire 21 Upgrade Guide to show the commands to upgrade to the release candidate. It also explains a few changes that may impact you when you upgrade. If you have any trouble upgrading, please let me know.

Create an issue for any bugs found in this release candidate.

@KingDarBoja I'm also looking forward to improving the docs. There are a number of doc-related PRs that went into 21.0.0-rc.1, but there's so much more to do. There is no open issue or discussion about this currently. Feel free to start one, or I can also start it once I've gathered the information I have regarding what I've observed that needs updating. The Discussions tab is enabled, though it is very stale, but since we are working to get this repo back in shape, I think the Discussions tab would be the proper place to start a discussion about this.

@armando-navarro

@armando-navarro Thanks for the response! I am looking forward as well to improve the docs. I was thinking about re-writting from zero the docs using Angular AnalogJS along with AI tools (like Gemini and such) to setup and start providing new docs as proof-of-concept with better markdown support and latest Angular best practices (via SKILLS and MCP) so we can iterate over these before integrating it into this repo.

I haven't had time this week to complete the setup and haven't published it but surely this is a better approach for anyone wanting to be involved in this in the short term.

By the way, only maintainers and such can create new discussions ;)

@KingDarBoja

@KingDarBoja I've created a discussion thread for AngularFire docs.

AngularFire 21.0.0-rc.2 has been released. View the release notes for details on what's changed, including one breaking change for apps that use App Check with server rendering.

If you're on 21.0.0-rc.1, update with ng update @angular/fire@21.0.0-rc.2. The AngularFire 21 Upgrade Guide covers upgrading from AngularFire 20.

Navigation Menu

Repository navigation

What happened to @angular/fire v21? #3699

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

What happened to @angular/fire v21? #3699

Description

Activity

markgoho commented on Jul 8, 2026

santonini82 commented on Jul 8, 2026

markgoho commented on Jul 8, 2026

santonini82 commented on Jul 9, 2026

armando-navarro commented on Jul 9, 2026

santonini82 commented on Jul 9, 2026

bezysoftware commented on Jul 14, 2026

EthanSK commented on Jul 20, 2026

jhuleatt commented on Jul 21, 2026

RignonNoel commented on Sep 14, 2026

armando-navarro commented on Sep 17, 2026

santonini82 commented on Sep 17, 2026

KingDarBoja commented on Sep 17, 2026

armando-navarro commented on Sep 24, 2026

KingDarBoja commented on Sep 25, 2026

armando-navarro commented on Sep 28, 2026

armando-navarro commented on Oct 10, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions