What happened to @angular/fire v21?

[santonini82]

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?

[markgoho]

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

[santonini82]

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?!

[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.

[santonini82]

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.

[armando-navarro]

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.

[santonini82]

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!