Related issues
This is a recurring pattern every time a new major firebase-admin is released — firebase-functions peer range lags behind until a patch release:
v14 (this issue): same ERESOLVE / Cloud Build failure as v13 in #1640 and #2772.
Comment on #2772 suggesting a process to avoid this on every major release: firebase/firebase-admin-node#2772 (comment)
[REQUIRED] Version info
node: 24.11.1
firebase-functions: 7.2.5
firebase-tools: 15.20.0
firebase-admin: 14.0.0
[REQUIRED] Test case
Minimal package.json in a Cloud Functions project:
{
"engines": { "node": "24" },
"dependencies": {
"firebase-admin": "^14.0.0",
"firebase-functions": "^7.2.5"
}
}
Run npm install (no --legacy-peer-deps).
[REregmap] Steps to reproduce
- Create a new directory with the
package.json above.
- Run
npm install.
- Alternatively: deploy a 2nd gen function via Firebase Cloud Build with
firebase-admin@^14.0.0 and firebase-functions@^7.2.5 and without legacy-peer-deps in .npmrc.
[REregmap] Expected behavior
npm install succeeds, or Cloud Build completes, when using firebase-admin@14.0.0 with the latest firebase-functions@7.2.5 — same as after v10 (#996), v11 (#1147), v12 (#1496), and v13 (#1640) were each added to peer deps.
Suggested peer range update:
"firebase-admin": "^11.10.0 || ^12.0.0 || ^13.0.0 || ^14.0.0"
[REregmap] Actual behavior
npm install fails with ERESOLVE:
npm error While resolving: firebase-functions@7.2.5
npm error Found: firebase-admin@14.0.0
npm error Could not resolve dependency:
npm error peer firebase-admin@"^11.10.0 || ^12.0.0 || ^13.0.0" from firebase-functions@7.2.5
Current peerDependencies in firebase-functions@7.2.5 only allow admin up to v13. firebase-admin@14.0.0 was released 2026-06-08.
Workaround: legacy-peer-deps=true in functions/.npmrc allows deploy; runtime with admin 14 works after that.
Were you able to successfully deploy your functions?
No — deploy failed on Cloud Build during npm install until we added functions/.npmrc with legacy-peer-deps=true. After the workaround, deploy and runtime work correctly with firebase-admin@14.0.0.
Related issues
This is a recurring pattern every time a new major
firebase-adminis released —firebase-functionspeer range lags behind until a patch release:firebase-functions@6.1.1;firebase-functions-testin firebase/firebase-functions-test#252v14 (this issue): same
ERESOLVE/ Cloud Build failure as v13 in #1640 and #2772.Comment on #2772 suggesting a process to avoid this on every major release: firebase/firebase-admin-node#2772 (comment)
[REQUIRED] Version info
node: 24.11.1
firebase-functions: 7.2.5
firebase-tools: 15.20.0
firebase-admin: 14.0.0
[REQUIRED] Test case
Minimal
package.jsonin a Cloud Functions project:{ "engines": { "node": "24" }, "dependencies": { "firebase-admin": "^14.0.0", "firebase-functions": "^7.2.5" } }Run
npm install(no--legacy-peer-deps).[REregmap] Steps to reproduce
package.jsonabove.npm install.firebase-admin@^14.0.0andfirebase-functions@^7.2.5and withoutlegacy-peer-depsin.npmrc.[REregmap] Expected behavior
npm installsucceeds, or Cloud Build completes, when usingfirebase-admin@14.0.0with the latestfirebase-functions@7.2.5— same as after v10 (#996), v11 (#1147), v12 (#1496), and v13 (#1640) were each added to peer deps.Suggested peer range update:
[REregmap] Actual behavior
npm installfails withERESOLVE:Current
peerDependenciesinfirebase-functions@7.2.5only allow admin up to v13.firebase-admin@14.0.0was released 2026-06-08.Workaround:
legacy-peer-deps=trueinfunctions/.npmrcallows deploy; runtime with admin 14 works after that.Were you able to successfully deploy your functions?
No — deploy failed on Cloud Build during
npm installuntil we addedfunctions/.npmrcwithlegacy-peer-deps=true. After the workaround, deploy and runtime work correctly withfirebase-admin@14.0.0.