Skip to content

docs: drop the --save-exact step for the release candidate #3778

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
armando-navarro merged 1 commit into from
Sep 30, 2026
Merged

docs: drop the --save-exact step for the release candidate #3778

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 0 additions & 6 deletions docs/install-and-setup.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -48,12 +48,6 @@ This installs AngularFire and configures your project. `ng add` will:
1. Prompt you to select the features to enable and the Firebase project to use, signing you in to Firebase if needed.
2. Add `provideFirebaseApp(...)`, along with a provider for each feature you select, to your app configuration (for example `app.config.ts`), with your Firebase configuration inlined. No environment files are created.

`ng add` writes the version it installed into your `package.json`, and today that is a canary release such as `21.0.0-rc.1-canary.95b3de1` rather than the release candidate. To replace it with the release candidate, `21.0.0-rc.1`, run:

```bash
npm install --save-exact @angular/fire@next
```

### 3. Inject `Firestore`

Open `/src/app/app.ts` and make the following changes:
Expand Down
6 changes: 0 additions & 6 deletions docs/version-21-upgrade.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -10,12 +10,6 @@ The release candidate is published under the `next` tag. From an app on Angular
ng update @angular/core@21 @angular/cli@21 @angular/fire@next
```

`ng update` writes the range `^21.0.0-rc.1` into your `package.json`. That range also matches canary releases, and npm currently installs one of them, such as `21.0.0-rc.1-canary.95b3de1`, instead of the release candidate. To install the release candidate itself, and stop npm from picking a canary release on a later install, change the entry to the exact version `21.0.0-rc.1` by running:

```bash
npm install --save-exact @angular/fire@next
```

The AngularFire update runs a migration that:

- **Aligns your `firebase` dependency to `^12.18.0`.** AngularFire 21 requires Firebase JS SDK 12, at 12.18 or later. If your app requested an older `firebase`, whether that is 11 or an earlier 12, npm would install both that copy and the one AngularFire needs side by side, and the two copies reject each other's objects at runtime. The migration updates the dependency and reinstalls so you end up with a single copy. Verify with `npm ls firebase`.
Expand Down
Loading