[[["易于理解","easyToUnderstand","thumb-up"],["解决了我的问题","solvedMyProblem","thumb-up"],["其他","otherUp","thumb-up"]],[["没有我需要的信息","missingTheInformationINeed","thumb-down"],["太复杂/步骤太多","tooComplicatedTooManySteps","thumb-down"],["内容需要更新","outOfDate","thumb-down"],["翻译问题","translationIssue","thumb-down"],["示例/代码问题","samplesCodeIssue","thumb-down"],["其他","otherDown","thumb-down"]],["最后更新时间 (UTC)：2025-08-31。"],[],[],null,["\u003cbr /\u003e\n\nFirebase App Hosting is designed specifically to support framework-centered\nmodern web app development. Use this page as a reference to the tooling and\nframeworks that App Hosting directly supports, as well as a jumping off\npoint to learn about related frameworks and tooling.\n\nWeb frameworks and App Hosting\n\nApp Hosting provides two broad levels of support for modern web frameworks:\npre-configured build and deploy support, and community-level support through\nopen source contributions conforming to the output bundle specification. In both\ncases, a *framework adapter* component enables the integration of a specific\nframework with App Hosting.\n\nFrameworks with preconfigured build and deploy support\n\nWith pre-configured build and deploy support, Firebase identifies which\nframework you're using by inspecting the `package-lock.json` file or other lock\nfile, and optimizes build and deployment processes for your app. Google is\ncommitted to maintaining support for these frameworks, and the Firebase support\nteam can accept issue reports and feature requests.\n\nThis level of support is provided for:\n\n- Next.js\n- Angular\n\nSee the\n[support schedules](#next.js-support) for details on specific versions\nand levels of support.\n\nIf you try to deploy a Node.js app that is missing a lock file, App Hosting\nwill fail to build and run your app. You can create `package-lock.json` by\nrunning `npm install` in your root directory.\n| **Note:** Express apps with a \"start\" and \"build\" script configured generally work in App Hosting, but support is not guaranteed. If there is a more specific adapter available, we recommend setting your project up with that adapter.\n\nCommunity-supported frameworks\n\nIn addition to Next.js and Angular, App Hosting also supports any web\nframework that is able to provide a build output that matches our\n[output bundle specification](https://github.com/FirebaseExtended/firebase-framework-tools#app-hosting-output-bundle).\nFramework authors can take advantage of the output bundle specification to\nensure their framework is supported by App Hosting. For example, the popular\nNuxt framework is supported by the Nitro team, who built a\n[Firebase adapter](https://nitro.build/deploy/providers/firebase)\nto enable Nuxt app deployment on App Hosting.\n\nIf you would like to see additional frameworks supported by App Hosting, you\ncan create a framework adapter, or reach out to the framework's maintainers to\nconvert build outputs into the App Hosting format. The Next.js and Angular\nadapters are good reference examples for anyone creating an adapter.\n\nInformation on community-supported frameworks can be found on\n[Firebase Open Source](https://firebaseopensource.com/platform/app_hosting).\nIssues and feature requests for community-supported frameworks\nshould be directed to the open source community or framework authors. In some\ncases Google may be able to assist, but the community is the first line of\nsupport for these adapters.\n\nApp Hosting framework adapters\n\nIn App Hosting, support for both pre-configured and community-supported\nframeworks is provided through *framework adapters* . App Hosting framework\nadapters have two key roles:\n\n- 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.\n- They run your app's build command to generate static assets and create an optimized version of your app for production.\n\nFramework adapters build your Node.js app with `npm run build`, working best\nwith the default build scripts for each framework: `next build` for Next.js and\n`ng build` for Angular. App Hosting will attempt builds with custom build\ncommands, but cannot dependably guarantee success. You can\n[override build and run scripts](/docs/app-hosting/configure#override-scripts)\nin `apphosting.yaml`.\n\nThe source for Next.js and Angular adapters is available in\n[firebase-framework-tools](https://github.com/FirebaseExtended/firebase-framework-tools).\n\nRuntimes for App Hosting\n\nAfter it is built and rolled out by App Hosting, your Node.js app runs in a\nCloud Run revision. Accordingly, the runtime version for your app\nshould be within both Cloud Run's\nsupported range and the range of your chosen web framework. For the\npreconfigured support for Angular and Next.js, this means that the\nfollowing Node.js versions are supported:\n\n- Next.js 13.5.x and higher\n- Angular 18.2.x and higher\n- Node.js 18 and higher\n\nApp Hosting does not automatically provide active support for newly released\nframework versions. Versions newer than our currently designated 'active'\nversion will be considered in a 'preview' state until officially marked as\n'active' for App Hosting.\n\nApp Hosting supports long-term support (LTS) for the latest minor version of\na major release for one year from its active support period, provided that you\nconsistently update to the latest patch releases within that minor version.\nRefer to the following tables for details for Next.js and Angular.\n| **Note:** Framework releases must abide by [semantic versioning](https://semver.org/). A framework release that violates semantic versioning is subject to a best-effort level of support.\n\nNext.js support schedule\n\n| Version | Status | Deprecation |\n|---------|--------|----------------------|\n| 13.5.x | lts | 2026-10-9 |\n| 14.2.x | lts | 2026-10-9 |\n| 15.0.x | active | not before 2025-10-9 |\n| 15.1.x | active | not before 2025-10-9 |\n| 15.2.x | active | - |\n\nAngular support schedule\n\n| Version | Status | Deprecation |\n|---------|--------|----------------------|\n| 18.2.x | lts | 2026-10-9 |\n| 19.0.x | active | not before 2025-10-9 |\n| 19.1.x | active | not before 2025-10-9 |\n| 19.2.x | active | - |\n\n| **Note:** versions outside of these ranges may work but are not offically supported.\n\nPackage managers\n\nApp Hosting uses [Cloud Native\nBuildpacks](https://cloud.google.com/docs/buildpacks/overview) to execute the\ninstallation of dependencies and builds the app using npm, yarn, or pnpm. Other\npackage managers such as JSR are not supported.\n\nNPM\n\n- NPM is the default package manager.\n- Non-production dependencies are pruned after the build is successful.\n- You can specify the npm version section using the `engines.npm` field in your `package.json` file.\n\nYarn\n\n- Yarn is used instead when you include the `yarn.lock` file in your project.\n- You can specify the yarn version to use in the `engines.yarn` or `packageManager` field of your `package.json` file.\n- App Hosting supports Yarn2 PnP mode.\n\nPnpm\n\n- Pnpm is used instead when you include the `pnpm-lock.yaml` file in your project.\n- You can specify a version of pnpm in the `engines.pnpm` or `packageManager` field of your `package.json` file.\n- For a working example, see the [sample-node-pnpm](https://github.com/GoogleCloudPlatform/buildpack-samples/tree/master/sample-node-pnpm). app.\n\nMonorepos for App Hosting\n\nApp Hosting supports Nx-based apps. See [Use monorepos with\nApp Hosting](/docs/app-hosting/monorepos) for detailed guidance.\n\nThe following Nx versions are supported:\n\n| Version | Status | Deprecation |\n|---------|-------------|----------------------|\n| 19.5.x | maintenance | 2025-10-9 |\n| 19.6.x | maintenance | 2025-10-9 |\n| 19.7.x | maintenance | 2025-10-9 |\n| 19.8.x | lts | 2026-10-9 |\n| 20.0.x | active | not before 2025-10-9 |\n| 20.1.x | active | not before 2025-10-9 |\n| 20.2.x | active | not before 2025-10-9 |\n| 20.3.x | active | not before 2025-10-9 |\n| 20.4.x | active | not before 2025-10-9 |\n| 20.5.x | active | not before 2025-10-9 |\n| 20.6.x | active | not before 2025-10-9 |\n| 20.7.x | active | --- |\n\nIf you need support for other types of monorepo workspaces, let us know at\n[Firebase UserVoice](https://firebase.uservoice.com/forums/948424-general)."]]
