AngularFire Files

What's Changed

Installing and setting up

• fix: remove the unused optional @angular/platform-server peer dependency, which made npm install and ng add @angular/fire fail with ERESOLVE on an app one Angular patch behind the newest release. by @armando-navarro in https://github.com/angular/angularfire/pull/3792
• fix: ng add @angular/fire no longer stops with Invalid project id: myApp. for a project whose name has capital letters. It and ng deploy also no longer crash with Cannot read properties of undefined (reading 'email') on firebase-tools 15.26 or later when run without a terminal, for example by an AI agent. by @armando-navarro in https://github.com/angular/angularfire/pull/3769

Compiling

• fix: the @angular/fire/compat/storage typings no longer import firebase/compat, which failed the build with TS2307 under moduleResolution: "bundler". by @armando-navarro in https://github.com/angular/angularfire/pull/3796

Server-side rendering

• fix: beforeAuthStateChanged from @angular/fire/auth no longer keeps the app from ever becoming stable for a visitor who never signs in or out. Its callback still runs inside Angular's zone and injection context. by @armando-navarro in https://github.com/angular/angularfire/pull/3770

Deploying (ng deploy)

• fix: ng deploy stops when a gcloud step fails. Before, a failure with any exit code other than 1 was ignored and the deploy went on to Firebase Hosting as if it had worked. It also passes gcloud arguments as an array, so a space in the workspace path or in GOOGLE_APPLICATION_CREDENTIALS no longer splits them. by @herdiyana256 in https://github.com/angular/angularfire/pull/3726
• fix: ng deploy runs its commands without a shell. A workspace path containing a space no longer breaks the Cloud Functions deploy, and values read from angular.json no longer reach a shell. by @herdiyana256 in https://github.com/angular/angularfire/pull/3738
• fix: the code and Dockerfile that ng deploy generates for SSR now escape or validate the angular.json values they use (output path, function name, Node.js version). A crafted value could previously place arbitrary code in the generated files. by @herdiyana256 in https://github.com/angular/angularfire/pull/3739
• fix: ng deploy writes the generated Cloud Run entry paths with forward slashes on every machine. Running it from Windows wrote backslash paths, which the Linux-based Cloud Run runtime cannot resolve. by @fr-esco in https://github.com/angular/angularfire/pull/3274

Release process

• fix: a 20.x release tagged after 21.0.0 publishes to the v20-lts npm tag instead of latest, so it can't replace 21 as the version npm install @angular/fire installs. by @armando-navarro in https://github.com/angular/angularfire/pull/3794

Check your angular.json before ng deploy

ng deploy now checks some angular.json values before it starts, and refuses ones that 20.1.0 let through.

One of these checks can stop a deploy that worked on 20.1.0:

• The outputPath of your build and server targets can't contain a backslash, $, a quote, a backtick or a line break, or start with -. A hand-edited Windows-style path such as dist\app\browser is the likely case. Use forward slashes, as the Angular CLI writes them.

Full Changelog: https://github.com/angular/angularfire/compare/20.1.0...20.1.1