docs: the documented install and upgrade commands do not work with 21.0.0-rc.1
Nobody has claimed this yet.
Assessment
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Newbie friendliness
- 58/100
- Issue type
- Documentation
- Clarity
- Mostly clear
- Activity status
- Active
- Tech stack
- angular, typescript
- Domain
- documentation
Research direction
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.
Written by the indexing model from the issue text.
Description
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/clitargets 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/firereports "Package '@angular/fire' is already up to date", becauselatestis 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/firenor@angular/fire@nextresolves against Angular 22.
- Step 1 creates a project on the newest Angular, which is 22, and step 2 then installs AngularFire from
- Setup stops on firebase-tools 15:
- After the features question,
ng addfails withCannot read properties of undefined (reading 'email'). firebaseTools.login()returns an object withemailin firebase-tools 14 and returnsundefinedin 15.- The peer range accepts 15 (#3701), and npm installs 15 by default.
- After the features question,
- 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.
- The Quickstart and twelve per-product pages each carry their own
Scope
Documentation only. The firebase-tools 15 crash will go in its own issue/PR.
- Dominant language
- TypeScript
- Stars
- 7.8k
- Forks
- 2.2k
- Avg merge
- 3d 6h
- Merged PRs (30d)
- 5
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from angular/angularfire
-
comp: build/pipeline type: bug version: current (v17+)
Difficulty 2/5 1-3 hours Newbie friendliness 74/100
angular/angularfire#3766 ·
-
comp: schematics type: bug version: current (v17+)
Difficulty 3/5 1-2 days Newbie friendliness 76/100
angular/angularfire#3768 ·
-
comp: firestore comp: ssr priority: P0 (critical) type: feature version: current (v17+)
angular/angularfire#3757 · 1 assignee ·
-
Six `firebase` entry points have no `@angular/fire` equivalent, so their exports are unreachable Opencomp: core type: feature
angular/angularfire#3755 · 1 assignee ·
-
comp: auth comp: ssr comp: zones type: bug
Difficulty 3/5 1-2 days Newbie friendliness 76/100
angular/angularfire#3748 ·
All issues in angular/angularfire
Similar issues
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
safetrustcr/dApp-SafeTrust#426 ·
-
area:workflow bug ready-for-agent
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
fil-donadoni/tolaria#4409 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
Fission-AI/OpenSpec#1960 ·
-
Add dependabot Open
Difficulty 2/5 1-3 hours Newbie friendliness 70/100
-
Difficulty 2/5 1-3 hours Newbie friendliness 75/100
corsairdev/corsair#1764 ·