Accept firebase 13 in @angular/fire 22

未關閉
  • 哪裡不對？
#3,830 0 則留言 0 個 reaction 已指派 0 人 在 GitHub 檢視

維護者通常 3 天內回覆

@armando-navarro 已經在處理了。

開始於 2026年10月30日。

  • #3831 來自 @armando-navarro —— 未關閉

評估

難度
4/5
預估耗時
3-5 天
新手友好度
25/100
Issue 類型
功能
描述清晰度
基本清楚
活躍度
停滯
技術堆疊
angular, typescript
領域
tooling

研究方向

A linked pull request is already open, so check its status before starting. The proposal identifies the package peer dependencies, the ng add and v22 ng update migration, generated wrappers, and CI specs as the areas to review; done means Firebase 12 remains supported, Firebase 13 is accepted and tested, and migrations write the installed major's range.

由索引模型根據 Issue 內容生成。

描述

comp: core comp: schematics type: feature

firebase 13.1.0 is now npm latest, and @angular/fire 22.0.0-rc.0 declares firebase ^12.18.0 as a peer dependency (#3805). So on a new Angular 22 app, running npm install firebase before ng add @angular/fire@next fails:

npm error ERESOLVE unable to resolve dependency tree
npm error peer firebase@"^12.18.0" from @angular/[email protected]
Proposal

I'd like @angular/fire 22.0.0 to accept firebase ^12.18.0 || ^13.0.0:

  • Apps on firebase 12 keep working with no change.
  • rxfire moves to ^6.3.0, the first release whose peer range includes firebase 13.
  • When ng add or the v22 ng update migration writes a firebase entry, it writes the range of the major already installed:
    • ^13.0.0 when firebase 13 is installed.
    • ^12.18.0 otherwise.
  • The package keeps building against firebase 12, because the generated wrappers import each function by name from the installed firebase. A new CI job runs the specs against firebase 13.
Why the written range follows the installed major

On npm, ng add installs a missing firebase peer before its schematic runs, at the newest version the range allows. If the schematic then wrote ^12.18.0, the reinstall would downgrade firebase and leave two @firebase/app copies, and the app would fail at startup with "No Firebase App '[DEFAULT]' has been created".

What changes for an app that moves to firebase 13
  • @angular/fire/ai re-exports firebase/ai, so VertexAIBackend and the ChatSession class are no longer available.
    • AgentPlatformBackend replaces VertexAIBackend, and the v21 ng update migration already handles it.
  • firebase 13's packages declare Node 24.12 or newer.

If you're already on firebase 13 and run into something this doesn't cover, please comment here.

主要語言
TypeScript
星號
7.8k
分支
2.2k
平均合併
2 天 12 小時
30 天內合併 PR
24

環境準備

從這裡開始

  1. 先讀完整個 Issue，再讀專案的貢獻指南。
  2. 在 Issue 下留言說明你要接手 —— 這能避免兩個人做同樣的事。
  3. Fork 儲存庫，在一個分支上完成修改。
  4. 送出 Pull Request，並在描述裡引用這個 Issue 編號。

angular/angularfire 的其他 Issue

查看 angular/angularfire 的全部 Issue

相似的 Issue

更多 TypeScript Issue

把新 issue 寄到你的電子郵件信箱

精選適合新手參與的 GitHub issue 摘要。