docs: the documented install and upgrade commands do not work with 21.0.0-rc.1

Offen

#3,764 erstellt am 22.9.2026 0 Kommentare 0 Reaktionen 0 zugewiesene Personen Auf GitHub ansehen

Dieses Issue hat noch niemand übernommen.

Bewertung

Schwierigkeit: 4/5
Geschätzter Aufwand: 3-5 Tage
Anfängerfreundlichkeit: 58/100

Issue-Typ: Dokumentation
Klarheit: Größtenteils klar
Aktivitätsstatus: Aktiv
Tech-Stack: angular, typescript
Bereich: documentation

Rechercherichtung

Locate the Quickstart, the v21 upgrade guide, and the twelve per-product pages that repeat the AngularFire install command. Compare their documented commands with the reported Angular 22, AngularFire 21.0.0-rc.1, and firebase-tools 15 behavior, keeping the firebase-tools crash out of scope. Done means the documentation gets users to a working app and the repeated version-sensitive instructions are consistent.

Vom Indexierungsmodell aus dem Issue-Text verfasst.

Beschreibung

comp: docs type: chore version: current (v17+)

With 21.0.0-rc.1 on npm next and Angular 22 on npm latest, the commands in the Quickstart and the v21 upgrade guide no longer get anyone to a working app.

What I found

The upgrade guide's first command fails:
- ng update @angular/core @angular/cli targets Angular 22, and the CLI refuses the two-major jump from Angular 20: "Updating multiple major versions of '@angular/core' at once is not supported."
The upgrade guide's second command does nothing:
- ng update @angular/fire reports "Package '@angular/fire' is already up to date", because latest is still 20.1.0.
The Quickstart cannot reach a working app at all:
- Step 1 creates a project on the newest Angular, which is 22, and step 2 then installs AngularFire from latest.
- Neither @angular/fire nor @angular/fire@next resolves against Angular 22.
Setup stops on firebase-tools 15:
- After the features question, ng add fails with Cannot read properties of undefined (reading 'email').
- firebaseTools.login() returns an object with email in firebase-tools 14 and returns undefined in 15.
- The peer range accepts 15 (#3701), and npm installs 15 by default.
Thirteen pages repeat the same install command:
- The Quickstart and twelve per-product pages each carry their own ng add @angular/fire, so every version change has to be made in thirteen places.

Scope

Documentation only. The firebase-tools 15 crash will go in its own issue/PR.

Vorherrschende Sprache: TypeScript
Sterne: 7.8k
Forks: 2.2k
Ø Merge: 3 T. 6 Std.
Gemergte PRs (30 T.): 5

Beitragsleitfaden

Beitragsleitfaden öffnen

Erste Schritte

Lesen Sie das ganze Issue und danach den Beitragsleitfaden des Projekts.
Schreiben Sie ins Issue, dass Sie es übernehmen — das erspart doppelte Arbeit.
Forken Sie das Repository und arbeiten Sie in einem Branch.
Öffnen Sie einen Pull Request, der die Issue-Nummer nennt.

Mehr aus angular/angularfire

Canary builds are named after the release candidate, so npm ranks them above it Offen

comp: build/pipeline type: bug version: current (v17+)

Schwierigkeit 2/5 1-3 Stunden Anfängerfreundlichkeit 74/100

angular/angularfire#3766 · Erstellt am 23.9.2026
`ng add @angular/fire` stops with `Cannot read properties of undefined (reading 'email')` on firebase-tools 15 Offen

comp: schematics type: bug version: current (v17+)

Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 76/100

angular/angularfire#3768 · Erstellt am 23.9.2026
Use `TransferState` to hand server-rendered Firestore data to the browser, instead of reading every document twice Offen

comp: firestore comp: ssr priority: P0 (critical) type: feature version: current (v17+)

angular/angularfire#3757 · 1 zugewiesene Person · Erstellt am 31.8.2026
Six `firebase` entry points have no `@angular/fire` equivalent, so their exports are unreachable Offen

comp: core type: feature

angular/angularfire#3755 · 1 zugewiesene Person · Erstellt am 31.8.2026
`beforeAuthStateChanged` imported from `@angular/fire/auth` makes `ng build` fail during route extraction Offen

comp: auth comp: ssr comp: zones type: bug

Schwierigkeit 3/5 1-2 Tage Anfängerfreundlichkeit 76/100

angular/angularfire#3748 · Erstellt am 17.8.2026

Alle Issues in angular/angularfire