<!-- mobian-agent-page publisher="dailydev" canonical="https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0" -->

---
title: New runtime configuration options with Cloud Functions...
description: Cloud Functions for Firebase reached general availability alongside new configuration options for developers. Node.js 8 (beta, targeting 8.11.1) is now...
canonical: https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0
twitter:card: summary_large_image
twitter:site: @dailydotdev
og:type: website
og:site_name: daily.dev
og:title: New runtime configuration options with Cloud Functions for Firebase | daily.dev
og:description: Cloud Functions for Firebase reached general availability alongside new configuration options for developers. Node.js 8 (beta, targeting 8.11.1) is now...
og:url: https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0
og:image: https://api.daily.dev/og/posts/koChtjOh0.png
og:image:alt: New runtime configuration options with Cloud Functions for Firebase
og:image:width: 1200
og:image:height: 630
og:locale: en
---

> ## Documentation Index
> Fetch the complete documentation index at: https://daily.dev/llms.txt
> Use this file to discover all available pages before exploring further.

# New runtime configuration options with Cloud Functions for Firebase

**[Firebase](https://daily.dev/sources/firebase-blog)** · 3 min read · 0 upvotes · 0 comments

## Summary

Cloud Functions for Firebase reached general availability alongside new configuration options for developers. Node.js 8 (beta, targeting 8.11.1) is now available as a runtime, offering V8 performance improvements and native async/await support without transpiling, requiring Firebase CLI 4.0.0+ and firebase-functions 2.0.1+, plus an 'engines' entry in package.json. TypeScript users can target ES2017 in tsconfig.json for tighter transpiled output. Additionally, developers can now set per-function region, memory allocation, and timeout using the new region and runWith methods.

## Full article

daily.dev links to this article rather than hosting it. Read it at the original source: <https://firebase.blog/posts/2018/08/cloud-functions-for-firebase-config-node-8-timeout-memory-region>

## Questions this post answers

### How do I enable the Node.js 8 runtime for Cloud Functions for Firebase?

Update the Firebase CLI to at least version 4.0.0 and the firebase-functions module to at least version 2.0.1, then add "engines": { "node": "8" } to the top level of package.json. Node.js 8 (beta, targeting 8.11.1) enables native async/await via ECMAScript 2017 without transpiling and brings V8 performance improvements.

_daily.dev surfaces runtime upgrade notes like this for developers rolling out Firebase Cloud Functions changes._

### How do I set a specific region, memory allocation, and timeout for a single Cloud Function in Firebase?

Chain the .region() and .runWith() methods from the firebase-functions module when defining a function, for example functions.region('europe-west1').runWith({ memory: '1GB', timeoutSeconds: 120 }).https.onRequest(...). This requires firebase-functions version 2.0.1 or later and lets each function have its own region, memory, and timeout instead of the defaults.

_Developers tuning serverless function performance track configuration changes like this on daily.dev._

### What TypeScript configuration is needed to use async/await with Node.js 8 in Cloud Functions?

Update tsconfig.json's compilerOptions so target and lib are set to 'es2017' instead of 'es6'. This stops the TypeScript compiler from converting async/await into JavaScript generators during transpilation, producing tighter and faster output for functions running on the Node.js 8 runtime.

_daily.dev helps TypeScript and Firebase developers keep up with runtime and tooling config changes._

## Similar posts on daily.dev

- [Node.js — Node.js 24.15.0 \(LTS\)](https://daily.dev/posts/node-js-node-js-24-15-0-lts--nsrp0vl5j) · Node.js · 107 upvotes · 3 comments
- [TypeScript 6.0 RC arrives as a bridge to a faster future](https://daily.dev/posts/typescript-6-0-rc-arrives-as-a-bridge-to-a-faster-future-uv04azmke) · The New Stack · 0 upvotes · 0 comments
- [Node.js 20 — Here’s What’s Actually Worth Caring About](https://daily.dev/posts/node-js-20-here-s-what-s-actually-worth-caring-about-6lpzz9vwc) · Medium · 0 upvotes · 0 comments

---

Tags: [#nodejs](https://daily.dev/tags/nodejs), [#typescript](https://daily.dev/tags/typescript), [#serverless](https://daily.dev/tags/serverless), [#firebase](https://daily.dev/tags/firebase), [#gcp-cloud-functions](https://daily.dev/tags/gcp-cloud-functions)

[View this post on daily.dev](https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0)

```json
{"@context":"https://schema.org","@graph":[{"@type":"Organization","@id":"https://daily.dev/#organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180},"sameAs":["https://twitter.com/dailydotdev","https://github.com/dailydotdev","https://www.linkedin.com/company/daily-dev-ltd"]},{"@type":"WebSite","@id":"https://daily.dev/#website","url":"https://daily.dev","name":"daily.dev","publisher":{"@id":"https://daily.dev/#organization"},"potentialAction":{"@type":"SearchAction","target":{"@type":"EntryPoint","urlTemplate":"https://daily.dev/search?q={search_term_string}"},"query-input":"required name=search_term_string"}}]}
{"@context":"https://schema.org","@type":"TechArticle","headline":"New runtime configuration options with Cloud Functions for Firebase","url":"https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0","mainEntityOfPage":{"@type":"WebPage","@id":"https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0"},"datePublished":"2026-08-23T12:17:42.118Z","dateModified":"2026-08-23T12:25:30.315Z","description":"Cloud Functions for Firebase reached general availability alongside new configuration options for developers. Node.js 8 (beta, targeting 8.11.1) is now...","image":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","thumbnailUrl":"https://media.daily.dev/image/upload/f_auto,q_auto/v1/posts/7ed721de96163685d26ab7e314be3ebc?_a=AQAEuop","isAccessibleForFree":true,"articleSection":"Firebase","inLanguage":"en","publisher":{"@type":"Organization","name":"daily.dev","url":"https://daily.dev","logo":{"@type":"ImageObject","url":"https://daily.dev/apple-touch-icon.png","width":180,"height":180}},"author":{"@type":"Organization","name":"Firebase","logo":"https://media.daily.dev/image/upload/s--i395oqZH--/f_auto,q_auto/v1787487448/logos/firebase-blog?_a=BAMAMicg0","url":"https://daily.dev/sources/firebase-blog"},"commentCount":0,"discussionUrl":"https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0","interactionStatistic":[{"@type":"InteractionCounter","interactionType":{"@type":"LikeAction"},"userInteractionCount":0},{"@type":"InteractionCounter","interactionType":{"@type":"CommentAction"},"userInteractionCount":0}],"keywords":"nodejs,typescript,serverless,firebase,gcp-cloud-functions","timeRequired":"PT3M"}
{"@context":"https://schema.org","@type":"BreadcrumbList","itemListElement":[{"@type":"ListItem","position":1,"name":"Home","item":"https://daily.dev"},{"@type":"ListItem","position":2,"name":"Firebase","item":"https://daily.dev/sources/firebase-blog"},{"@type":"ListItem","position":3,"name":"New runtime configuration options with Cloud Functions for Firebase"}]}
{"@context":"https://schema.org","@type":"FAQPage","@id":"https://daily.dev/posts/new-runtime-configuration-options-with-cloud-functions-for-firebase-kochtjoh0#faq","mainEntity":[{"@type":"Question","name":"How do I enable the Node.js 8 runtime for Cloud Functions for Firebase?","acceptedAnswer":{"@type":"Answer","text":"Update the Firebase CLI to at least version 4.0.0 and the firebase-functions module to at least version 2.0.1, then add \"engines\": { \"node\": \"8\" } to the top level of package.json. Node.js 8 (beta, targeting 8.11.1) enables native async/await via ECMAScript 2017 without transpiling and brings V8 performance improvements. daily.dev surfaces runtime upgrade notes like this for developers rolling out Firebase Cloud Functions changes."}},{"@type":"Question","name":"How do I set a specific region, memory allocation, and timeout for a single Cloud Function in Firebase?","acceptedAnswer":{"@type":"Answer","text":"Chain the .region() and .runWith() methods from the firebase-functions module when defining a function, for example functions.region('europe-west1').runWith({ memory: '1GB', timeoutSeconds: 120 }).https.onRequest(...). This requires firebase-functions version 2.0.1 or later and lets each function have its own region, memory, and timeout instead of the defaults. Developers tuning serverless function performance track configuration changes like this on daily.dev."}},{"@type":"Question","name":"What TypeScript configuration is needed to use async/await with Node.js 8 in Cloud Functions?","acceptedAnswer":{"@type":"Answer","text":"Update tsconfig.json's compilerOptions so target and lib are set to 'es2017' instead of 'es6'. This stops the TypeScript compiler from converting async/await into JavaScript generators during transpilation, producing tighter and faster output for functions running on the Node.js 8 runtime. daily.dev helps TypeScript and Firebase developers keep up with runtime and tooling config changes."}}]}
```