Node.js

Technologyactivesince 2026-02

Server-side JavaScript runtime used for Firebase Cloud Functions in TrustSeal and ScamCheck. Critical operational constraint: Firebase Functions defaults to Node 18, which is incompatible with the npm packages used in these projects — all Cloud Function invocations fail at runtime without explicit Node 22 declaration in firebase.json. This is a documented production failure (firebase-functions-node-version-stability). The fix is to set `"runtime": "nodejs22"` in firebase.json before first deploy — discovered during TrustSeal build, proactively applied to ScamCheck before first deploy. ESM/CJS module format must also match the Node version and Firebase Functions runtime behavior.

1 operational records1 failure

Documented failures· last 2026-02-01

Firebase Cloud Functions Crashing on Default Node Runtime2026-02-01

Depends on

firebase-functions

Used by

trustseal scamcheck

Docsnodejs.org/en/docs ↗

Operational records — 1 total

2026-02-01

FAILUREFirebase Cloud Functions Crashing on Default Node Runtime

Firebase Cloud Functions deployed and appeared active in the console but crashed on every invocation in production. Cold start succeeded but function execution failed with unhandled promise rejections and module resolution errors not present in local development. Root cause: default Node runtime version (Node 18) had known incompatibilities with the npm packages used. Migrating to Node 22 runtime resolved production crashes.

#firebase #firebase-functions #runtime #deployment

5 min read