Firebase App Hosting is designed specifically to support framework-centered modern web app development. Use this page as a reference to the tooling and frameworks that App Hosting directly supports, as well as a jumping off point to learn about related frameworks and tooling.
Web frameworks and App Hosting
App Hosting provides two broad levels of support for modern web frameworks: pre-configured build and deploy support, and community-level support through open source contributions conforming to the output bundle specification. In both cases, a framework adapter component enables the integration of a specific framework with App Hosting.
Frameworks with preconfigured build and deploy support
With pre-configured build and deploy support, Firebase identifies which
framework you're using by inspecting the package-lock.json file or other lock
file, and optimizes build and deployment processes for your app. Google is
committed to maintaining support for these frameworks, and the Firebase support
team can accept issue reports and feature requests.
This level of support is provided for Next.js and Angular. See the support schedules for details on specific versions and levels of support.
If you try to deploy a Node.js app that is missing a lock file, App Hosting
will fail to build and run your app. You can create package-lock.json by
running npm install in your root directory.
Community-supported frameworks
In addition to Nextjs and Angular, App Hosting also supports any web framework that is able to provide a build output that matches our output bundle specification. Framework authors can take advantage of the output bundle specification to ensure their framework is supported by App Hosting. For example, the popular Nuxt framework is supported by the Nitro team, who built a Firebase adapter to enable Nuxt app deployment on App Hosting.
If you would like to see additional frameworks supported by App Hosting, you can create a framework adapter, or reach out to the framework's maintainers to convert build outputs into the App Hosting format. The Next.js and Angular adapters are good reference examples for anyone creating an adapter.
Information on community-supported frameworks can be found on Firebase Open Source. Issues and feature requests for community-supported frameworks should be directed to the open source community or framework authors. In some cases Google may be able to assist, but the community is the first line of support for these adapters.
App Hosting framework adapters
In App Hosting, support for both pre-configured and community-supported frameworks is provided through framework adapters. App Hosting framework adapters have two key roles:
- They parse your source code and any framework-specific config files (such as
next.config.js) and generate an output bundle that can be processed by the rest of the App Hosting infrastructure. - They run your app's build command to generate static assets and create an optimized version of your app for production.
Framework adapters build your Node.js app with npm run build, working best
with the default build scripts for each framework: next build for Next.js and
ng build for Angular. App Hosting will attempt builds with custom build
commands, but cannot dependably guarantee success.
The source for Next.js and Angular adapters is available in firebase-framework-tools.
Runtimes for App Hosting
After it is built and rolled out by App Hosting, your Node.js app runs in a Cloud Run revision. Accordingly, the runtime version for your app should be within both Cloud Run's supported range and the range of your chosen web framework. For the preconfigured support for Angular and Next.js, this means that the following Node.js versions are supported:
- Next.js 13.5.x and higher
- Angular 18.2.x and higher
- Node.js 18 and higher
App Hosting does not automatically provide active support for newly released framework versions. Versions newer than our currently designated 'active' version will be considered in a 'preview' state until officially marked as 'active' for App Hosting.
App Hosting supports long-term support (LTS) for the latest minor version of a major release for one year from its active support period, provided that you consistently update to the latest patch releases within that minor version. Refer to the following tables for details for Next.js and Angular.
Next.js support schedule
| Version | Status | Deprecation |
|---|---|---|
| 13.5.x | lts | 2026-10-9 |
| 14.2.x | lts | 2026-10-9 |
| 15.0.x | active | not before 2025-10-9 |
| 15.1.x | active | not before 2025-10-9 |
| 15.2.x | active | - |
Angular support schedule
| Version | Status | Deprecation |
|---|---|---|
| 18.2.x | lts | 2026-10-9 |
| 19.0.x | active | not before 2025-10-9 |
| 19.1.x | active | not before 2025-10-9 |
| 19.2.x | active | - |
Package managers
App Hosting uses Cloud Native Buildpacks to execute the installation of dependencies and builds the app using npm, yarn, or pnpm. Other package managers such as JSR are not supported.
NPM
- NPM is the default package manager.
- Non-production dependencies are pruned after the build is successful.
- You can specify the npm version section using the
engines.npmfield in yourpackage.jsonfile.
Yarn
- Yarn is used instead when you include the
yarn.lockfile in your project. - You can specify the yarn version to use in the
engines.yarnorpackageManagerfield of yourpackage.jsonfile. - App Hosting supports Yarn2 PnP mode.
Pnpm
- Pnpm is used instead when you include the
pnpm-lock.yamlfile in your project. - You can specify a version of pnpm in the
engines.pnpmorpackageManagerfield of yourpackage.jsonfile. - For a working example, see the sample-node-pnpm. app.
Monorepos for App Hosting
App Hosting supports Nx-based apps. See Use monorepos with App Hosting for detailed guidance.
The following Nx versions are supported:
| Version | Status | Deprecation |
|---|---|---|
| 19.5.x | maintenance | 2025-10-9 |
| 19.6.x | maintenance | 2025-10-9 |
| 19.7.x | maintenance | 2025-10-9 |
| 19.8.x | lts | 2026-10-9 |
| 20.0.x | active | not before 2025-10-9 |
| 20.1.x | active | not before 2025-10-9 |
| 20.2.x | active | not before 2025-10-9 |
| 20.3.x | active | not before 2025-10-9 |
| 20.4.x | active | not before 2025-10-9 |
| 20.5.x | active | not before 2025-10-9 |
| 20.6.x | active | not before 2025-10-9 |
| 20.7.x | active | — |
If you need support for other types of monorepo workspaces, let us know at Firebase UserVoice.