angular/angularfire 20.0.3

on GitHub

What's Changed

• fix: remove the @angular/platform-browser-dynamic peer dependency, which made ng add @angular/fire fail with ERESOLVE on Angular 20.1 and newer. It forced npm toward a version whose own requirements clashed with the app's, and nothing in the published package imports it. by @armando-navarro in #3718
• fix: ng add now writes only accepted keys into the app config, which previously did not compile. The whole Firebase CLI response was inlined into initializeApp(), including management fields such as projectNumber that FirebaseOptions rejects, producing TS2769. by @armando-navarro in #3707
• fix: accept firebase-tools 15. The optional peer dependency was capped at ^14.0.0, which excluded the current major, so anyone on the current Firebase CLI saw peer dependency warnings on every install. The range is now ^14.0.0 || ^15.0.0. by @armando-navarro in #3702
• fix: the firebase-tools version check now asks for the version it enforces. It said 13.0.0 or newer while actually requiring 14.0.0 or newer. by @Muneersahel in #3662
• fix: the Cloud Function generated for SSR now uses a public firebase-functions logger entry point, instead of an internal path that crashed the function at startup. by @armando-navarro in #3730
• fix: the package.json generated for SSR deployments now carries real version ranges for firebase-admin and firebase-functions. Both were pinned to the placeholder 0.0.0, so npm install could not resolve them and failed with ETARGET. by @armando-navarro in #3745
• fix: the generated Cloud Function now asks for Node 22, instead of Node 14, a runtime Cloud Functions decommissioned in early 2025. by @armando-navarro in #3743
• fix: the generated Cloud Function now imports region from the firebase-functions/v1 subpath, where firebase-functions 6 moved it. Calling it from the package root threw on the function's first request. by @armando-navarro in #3743
• ci: upgrade the Java version used by the test emulators from 11 to 21 by @mwilman in #3687

New Contributors

• @Muneersahel made their first contribution in #3662
• @mwilman made their first contribution in #3687

A note on ng deploy with SSR

The last three fixes repair defects in the Cloud Function that ng deploy generates, but they do not make SSR deployment to Cloud Functions work end to end on a project created with Angular 17 or newer. That command still looks for a server build target which the current Angular application builder does not create.

If you are deploying a server-side rendered Angular app to Firebase today, App Hosting is the supported path. Plain ng deploy without SSR is unaffected.

Full Changelog: 20.0.1...20.0.3