// the find
angular/angularfire
Angular + Firebase = ❤️
AngularFire is the official Angular wrapper around the Firebase JS SDK, giving you DI-based providers, RxJS streams instead of callbacks, and Angular-idiomatic APIs for every Firebase product (Firestore, Auth, Storage, Functions, etc.). It's for Angular teams already committed to Firebase who want to skip writing their own zone/DI glue code.
Every Firebase product gets its own tree-shakable entry point (src/firestore, src/auth, src/storage, and so on), so you only ship what you import instead of the whole SDK. The zone.js wrappers are a real, non-obvious fix — without them things like service workers and SSR silently misbehave with raw Firebase calls. It stays current with Angular's own direction: signals-friendly APIs, zoneless SSR support, and a dedicated doc calling out the 'silent SSR-to-CSR fallback' trap on Firebase App Hosting, which is the kind of thing that normally costs a day of debugging to discover yourself. Route guards and NgRx action-based auth APIs cut real boilerplate if you're already in that ecosystem.
It's a second layer over an SDK that's already complex, and the README admits it: if your bug is actually in firebase-js-sdk, you get bounced there, so debugging sometimes means diagnosing across two repos and two issue trackers. Support is explicitly best-effort despite living under the angular GitHub org, not an SLA-backed integration. The zone.js dependency is legacy weight during Angular's zoneless migration, and the docs on zoneless SSR feel like they're still catching up rather than being the default path. You're also fully locked into Firebase's pricing and query model — this doesn't make Firestore's limited querying or Firebase's costs any better, it just makes them easier to reach from Angular.