Firebase Release Notes

Raw content:
Version 7.0.0 of the
Firebase SDK for
Cloud Functions
contains
breaking changes
as well as new features and enhancements.

This release drops support for Node.js 16, requires TypeScript v5, and removes the deprecated
functions.config()
API.

Review these release notes carefully to avoid issues or outages.

Breaking changes

Minimum Node.js version is now 18. As of v7.0.0, the SDK requires a Node.js runtime of version 18 or newer. Support for Node.js 14 and 16 has been removed.

• Impact: Functions using this SDK version fail to deploy or run on Node.js runtimes older than v18.
• Action Required: Before upgrading the SDK, you must
  set the Node.js version
  to update your function's runtime environment to Node.js 18 or higher. We recommend using the latest Node.js LTS version supported by Cloud Functions.
  The
  functions.config()
  API has been removed. Following the deprecation schedule announced in v6.0.0, runtime configuration with
  functions.config()
  has been removed entirely.
• Impact: Calling this API now throws a runtime error and causes build time errors if you are using TypeScript. Any function relying on
  functions.config()
  fails at runtime.
• Action Required: You must
  migrate from runtime configuration
  to environment variables using the params module.
  TypeScript v5 is now required. The SDK has been upgraded from TypeScript v4.3 to v5.9 and now targets ES2022.
• Impact: This may introduce new type-checking errors in your project if you are using an older version of TypeScript or if your code relies on older type definitions.
• Action Required: Update your project's TypeScript version to v5.x and resolve any resulting type errors.
  The
  Event
  interface, which defines the wire format for an event, has been changed to
  LegacyEvent
  . This change mitigates an api-extractor conflict caused by an open issue with Rushstack (#3581).
• Impact: Very few users are likely to be affected, as this type represents the internal state of function triggers.
• Action: If you rely on this type, update your code to use
  LegacyEvent
  instead.
  Improved error handling for async handlers in the Emulator. We have improved how unhandled errors are processed in the Local Emulator Suite. Previously, an unhandled error or rejected Promise in an async
  onRequest
  handler would cause the request to hang until a platform timeout.
• Impact: As of v7.0.0, these unhandled errors now correctly and immediately return a 500 Internal Server Error.
• Action Required: This is a technical breaking change, as it changes error handling behavior. This provides faster, more accurate error feedback during local development. Ensure your error handling logic is correct and not reliant on the old timeout behavior.
  The SDK is now published as both CommonJS (CJS) and ECMAScript Modules (ESM). This provides first-class support for modern bundlers (like Vite and esbuild) and native import syntax, which can lead to optimized function sources and smaller bundle sizes. The
  package.json
  exports map now properly resolves for both
  require
  and
  import
  .
  This release adds a new function trigger for Firebase Data Connect (FDC),
  onMutationExecuted()
  . This allows you to execute functions in response to data mutations.