Accept firebase 13 in @angular/fire 22
维护者通常 3 天内回复
评估
- 难度
- 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 内容生成。
描述
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.
rxfiremoves to^6.3.0, the first release whose peer range includes firebase 13.- When
ng addor the v22ng updatemigration writes afirebaseentry, it writes the range of the major already installed:^13.0.0when firebase 13 is installed.^12.18.0otherwise.
- 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/aire-exportsfirebase/ai, soVertexAIBackendand theChatSessionclass are no longer available.AgentPlatformBackendreplacesVertexAIBackend, and the v21ng updatemigration 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
环境准备
- 没有 Dockerfile 或 Docker Compose 文件
- 有 Pull Request 模板
- 阅读贡献指南
从这里开始
- 先读完整个 Issue，再读项目的贡献指南。
- 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
- Fork 仓库，在一个分支上完成修改。
- 提交 Pull Request，并在描述里引用这个 Issue 编号。
angular/angularfire 的其他 Issue
-
Document the 22.0.0-rc.1 changes可能已有人在做 @armando-navarro 于 2 天前认领。 未关闭comp: docs type: chore
难度 3/5 半天 新手友好度 18/100
angular/angularfire#3834 ·
维护者通常 3 天内回复
-
comp: compat comp: ssr comp: zones type: feature version: current (v17+)
难度 3/5 1-2 天 新手友好度 74/100
angular/angularfire#3832 ·
维护者通常 3 天内回复
-
`ɵzoneWrap` ignores a handler passed as an observer object, and holds a wrapped promise forever once its injector is destroyed可能已有人在做 @armando-navarro 于 2 天前认领。 未关闭comp: app-check comp: core comp: firestore comp: remote-config comp: zones type: bug version: current (v17+)
难度 4/5 3-5 天 新手友好度 25/100
angular/angularfire#3828 ·
维护者通常 3 天内回复
-
Eleven wrapped callbacks and remote-config `isSupported` hold the app unstable until something that may never happen可能已有人在做 @armando-navarro 于 3 天前认领。 未关闭comp: app-check comp: core comp: database comp: remote-config comp: ssr comp: zones type: bug version: current (v17+)
难度 4/5 3-5 天 新手友好度 48/100
angular/angularfire#3826 ·
维护者通常 3 天内回复
-
comp: compat comp: firestore comp: storage type: chore
难度 4/5 3-5 天 新手友好度 48/100
angular/angularfire#3822 ·
维护者通常 3 天内回复
查看 angular/angularfire 的全部 Issue
相似的 Issue
-
难度 2/5 1-3 小时 新手友好度 68/100
JuliusBrussee/caveman#1449 ·
维护者通常 1 天内回复
-
难度 1/5 1 小时以内 新手友好度 78/100
linagora/twake-calendar-frontend#1924 ·
维护者通常 1 天内回复
-
check:passed streams:add
难度 1/5 1 小时以内 新手友好度 65/100
维护者通常 1 天内回复
-
难度 2/5 1-3 小时 新手友好度 70/100
libnativeapi/nativeapi#21 ·
-
难度 2/5 1-3 小时 新手友好度 62/100
GiganticMinecraft/seichi-playguide#183 ·
维护者通常 1 天内回复