Accept firebase 13 in @angular/fire 22

Ouverte
  • Quelque chose ne va pas ?
#3,830 0 commentaires 0 réactions 0 personnes assignées Voir sur GitHub

Les mainteneurs répondent en général sous 3 jours

@armando-navarro y travaille déjà.

Depuis le 30/10/2026.

  • #3831 par @armando-navarro — ouverte

Évaluation

Difficulté
4/5
Temps estimé
3-5 jours
Accessibilité débutants
25/100
Type d'issue
Fonctionnalité
Clarté
Plutôt claire
Activité
À l'abandon
Stack technique
angular, typescript
Domaine
tooling

Piste de recherche

A linked pull request is already open, so check its status before starting. The proposal identifies the package peer dependencies, the ng add and v22 ng update migration, generated wrappers, and CI specs as the areas to review; done means Firebase 12 remains supported, Firebase 13 is accepted and tested, and migrations write the installed major's range.

Rédigé par le modèle d'indexation à partir du texte de l'issue.

Description

comp: core comp: schematics type: feature

firebase 13.1.0 is now npm latest, and @angular/fire 22.0.0-rc.0 declares firebase ^12.18.0 as a peer dependency (#3805). So on a new Angular 22 app, running npm install firebase before ng add @angular/fire@next fails:

npm error ERESOLVE unable to resolve dependency tree
npm error peer firebase@"^12.18.0" from @angular/[email protected]
Proposal

I'd like @angular/fire 22.0.0 to accept firebase ^12.18.0 || ^13.0.0:

  • Apps on firebase 12 keep working with no change.
  • rxfire moves to ^6.3.0, the first release whose peer range includes firebase 13.
  • When ng add or the v22 ng update migration writes a firebase entry, it writes the range of the major already installed:
    • ^13.0.0 when firebase 13 is installed.
    • ^12.18.0 otherwise.
  • The package keeps building against firebase 12, because the generated wrappers import each function by name from the installed firebase. A new CI job runs the specs against firebase 13.
Why the written range follows the installed major

On npm, ng add installs a missing firebase peer before its schematic runs, at the newest version the range allows. If the schematic then wrote ^12.18.0, the reinstall would downgrade firebase and leave two @firebase/app copies, and the app would fail at startup with "No Firebase App '[DEFAULT]' has been created".

What changes for an app that moves to firebase 13
  • @angular/fire/ai re-exports firebase/ai, so VertexAIBackend and the ChatSession class are no longer available.
    • AgentPlatformBackend replaces VertexAIBackend, and the v21 ng update migration already handles it.
  • firebase 13's packages declare Node 24.12 or newer.

If you're already on firebase 13 and run into something this doesn't cover, please comment here.

Langage dominant
TypeScript
Étoiles
7.8k
Forks
2.2k
Merge moyen
2 j 12 h
PR mergées (30 j)
24

Préparer son environnement

Par où commencer

  1. Lisez l'issue en entier, puis le guide de contribution du projet.
  2. Signalez en commentaire que vous la prenez — cela évite que deux personnes fassent le même travail.
  3. Forkez le dépôt et travaillez sur une branche.
  4. Ouvrez une pull request qui référence le numéro de l'issue.

Autres issues de angular/angularfire

Toutes les issues de angular/angularfire

Issues similaires

Plus d'issues TypeScript

Recevez les nouvelles issues par e-mail

Un résumé court des issues GitHub adaptées aux débutants.