feat(firebase): add support for 2nd generation functions

.gitignore

@@ -68,5 +68,6 @@ Temporary Items
 .vercel
 staticwebapp.config.json
 .eslintcache
+playground/firebase.json
 
 test/fixture/functions

build.config.ts

@@ -9,13 +9,5 @@ export default defineBuildConfig({
     "src/cli/cli",
     { input: "src/runtime/", outDir: "dist/runtime", format: "esm" },
   ],
-  dependencies: [
-    "@cloudflare/kv-asset-handler",
-    "@netlify/functions",
-    "@nuxt/devalue",
-    "destr",
-    "ofetch",
-    "ora",
-  ],
-  externals: ["@nuxt/schema"],
+  externals: ["@nuxt/schema", "firebase-functions"],
 });

docs/content/2.deploy/providers/firebase.md

@@ -6,47 +6,35 @@ Deploy Nitro apps to Firebase.
 
 Nitro supports [Firebase Hosting](https://firebase.google.com/docs/hosting) with Cloud Functions out of the box.
 
+::alert{type=""}
 **Note**: You need to be on the **Blaze plan** to use Nitro with Cloud Functions.
+::
 
-If you don't already have a `firebase.json` in your root directory, Nitro will create one the first time you run it. In this file, you will need to replace `<your_project_id>` with the ID of your Firebase project.
+::alert
+**Note**: This preset will deploy to firebase functions 1st gen by default. If you want to deploy to firebase functions 2nd gen, see the [instructions below](#using-2nd-generation-firebase-functions).
+::
 
-This file should then be committed to version control. You can also create a `.firebaserc` file if you don't want to manually pass your project ID to your `firebase` commands (with `--project <your_project_id>`):
+::alert{type="warning"}
+**Note:** Firebase preset is under development. Consider using [Edge Release Channel](/guide/getting-started#edge-release-channel) in order to use latest updates and gen 2.
+::
 
-```json [.firebaserc]
-{
-  "projects": {
-    "default": "<your_project_id>"
-  }
-}
-```
-
-Then, just add Firebase dependencies to your project:
-
-```bash
-# yarn
-yarn add --dev firebase-admin firebase-functions firebase-functions-test
+## Project Setup
 
-# npm
-npm install -D firebase-admin firebase-functions firebase-functions-test
-```
+### Using Firebase CLI (recommended)
 
-### Using Firebase CLI
+You may instead prefer to set up your project with the Firebase CLI, which will fetch your project ID for you, add required dependencies (see above) and even set up automated deployments via GitHub Actions (for hosting only). [Learn about installing the firebase CLI](https://firebase.google.com/docs/cli#windows-npm).
 
-You may instead prefer to set up your project with the Firebase CLI, which will fetch your project ID for you, add required dependencies (see above) and even set up automated deployments via GitHub Actions.
+#### 1. Install Firebase CLI Globally
 
-#### Install Firebase CLI globally
+Always try to use the latest version of the Firebase CLI.
 
 ```bash
-# yarn
-yarn global add firebase-tools
-
-# npm
-npm install -g firebase-tools
+npm install -g firebase-tools@latest
 ```
 
-**Note**: You need to be on [^11.18.0](https://github.com/firebase/firebase-tools/releases/tag/v11.18.0) to deploy a nodejs18 function.
+**Note**: You need to be on [^11.18.0](https://github.com/firebase/firebase-tools/releases/tag/v11.18.0) to deploy a `nodejs18` function.
 
-#### Initialize your Firebase project
+#### 2. Initialize your Firebase Project
 
 ```bash
 firebase login
@@ -73,20 +61,186 @@ Once complete, add the following to your `firebase.json` to enable server render
 
 You can find more details in the [Firebase documentation](https://firebase.google.com/docs/hosting/quickstart).
 
-## Local preview
+### Alternative Method
+
+If you don't already have a `firebase.json` in your root directory, Nitro will create one the first time you run it. In this file, you will need to replace `<your_project_id>` with the ID of your Firebase project. This file should then be committed to the git.
+
+#### 1. Create a `.firebaserc` file
+
+It is recommended to create a `.firebaserc` file so you don't need to manually pass your project ID to your `firebase` commands (with `--project <your_project_id>`):
+
+```json [.firebaserc]
+{
+  "projects": {
+    "default": "<your_project_id>"
+  }
+}
+```
+
+This file is usually generated when you initialize your project with the Firebase CLI. But if you don't have one, you can create it manually.
+
+#### 2. Install Firebase Dependencies
+
+Then, add Firebase dependencies to your project:
+
+::code-group
+```bash [npm]
+npm install -D firebase-admin firebase-functions firebase-functions-test
+```
+```bash [yarn]
+yarn add --dev firebase-admin firebase-functions firebase-functions-test
+```
+```bash [pnpm]
+pnpm install -D firebase-admin firebase-functions firebase-functions-test
+```
+::
+
+#### 3. Log Into the Firebase CLI
+
+Make sure you are authenticated with the firebase cli. Run this command and follow the prompts:
+
+```bash
+npx firebase-tools login
+```
+
+
+## Local Preview
 
 You can preview a local version of your site if you need to test things out without deploying.
 
 ```bash
-NITRO_PRESET=firebase yarn build
+NITRO_PRESET=firebase npm run build
 firebase emulators:start
 ```
 
-## Deploy to Firebase Hosting via CLI
+## Build and Deploy
+
+Deploy to Firebase Hosting by running a Nitro build and then running the `firebase deploy` command.
+
+```bash
+NITRO_PRESET=firebase npm run build
+```
+
+```bash
+npx firebase-tools deploy
+```
 
-Deploying to Firebase Hosting is a simple matter of just running the `firebase deploy` command.
+If you installed the Firebase CLI globally, you can also run:
 
 ```bash
-NITRO_PRESET=firebase yarn build
 firebase deploy
 ```
+
+## Using 2nd Generation Firebase Functions
+
+- [Comparison between 1st and 2nd generation functions](https://firebase.google.com/docs/functions/version-comparison)
+
+To switch to the more recent and, recommended generation of firebase functions, set the `firebase.gen` option to `2`:
+
+::code-group
+```ts{3} [nitro.config.ts]
+export default defineNitroConfig({
+  firebase: {
+    gen: 2
+    // ...
+  }
+})
+```
+```ts{4} [nuxt.config.ts]
+export default defineNuxtConfig({
+  nitro: {
+    firebase: {
+      gen: 2
+      // ...
+    }
+  }
+})
+```
+::
+
+::alert
+If you cannot use configuration for any reason, alternatively you can use `NITRO_FIREBASE_GEN` environment variable.
+::
+
+If you already have a deployed version of your website and want to upgrade to 2nd gen, [see the Migration process on Firebase docs](https://firebase.google.com/docs/functions/2nd-gen-upgrade). Namely, the CLI will ask you to delete your existing functions before deploying the new ones.
+
+## Options
+
+You can set options for the firebase functions in your `nitro.config.ts` file:
+
+::code-group
+```ts [nitro.config.ts]
+export default defineNitroConfig({
+  firebase: {
+    gen: 2,
+    httpOptions: {
+      region: 'europe-west1',
+      maxInstances: 3,
+    },
+  },
+});
+```
+
+```ts [nuxt.config.ts]
+export default defineNuxtConfig({
+  nitro: {
+    firebase: {
+      gen: 2,
+      httpOptions: {
+        region: 'europe-west1',
+        maxInstances: 3,
+      },
+    },
+  },
+});
+```
+::
+
+You can also set options for 1st generation Cloud Functions if the `gen` option is set to `1`. Note these are different from the options for 2nd generation Cloud Functions.
+
+### Runtime Node.js Version
+
+You can set custom Node.js version in configuration:
+
+::code-group
+```ts [nitro.config.ts]
+export default defineNitroConfig({
+  firebase: {
+    nodeVersion: 18 // Can be 16 or 18 or 20
+  },
+});
+```
+
+```ts [nuxt.config.ts]
+export default defineNuxtConfig({
+  nitro: {
+    firebase: {
+      nodeVersion: 18 // Can be 16 or 18 or 20
+    },
+  },
+});
+```
+::
+
+Firebase tools use the `engines.node` version in  `package.json` to determine which node version to use for your functions. Nitro automatically writes to the `.output/server/package.json` with configured Node.js version.
+
+You might also need to add a runtime key to your `firebase.json` file:
+
+```json [firebase.json]
+{
+  "functions": {
+    "source": ".output/server",
+    "runtime": "nodejs18"
+  }
+}
+```
+
+You can read more about this in [Firebase Docs](https://firebase.google.com/docs/functions/manage-functions?gen=2nd#set_nodejs_version).
+
+## If your firebase project has other cloud functions
+
+You may be warned that other cloud functions will be deleted when you deploy your nitro project. This is because nitro will deploy your entire project to firebase functions. If you want to deploy only your nitro project, you can use the `--only` flag:
+
+```bash
+firebase deploy --only functions:server,hosting
+```

docs/content/3.config.md

@@ -128,12 +128,11 @@ It's possible to set Cache-Control headers for assets using the `maxAge` option:
     },
   ],
 ```
+
 The config above generates the following header in the assets under `public/images/` folder:
 
 `cache-control: public, max-age=604800, immutable`
 
-
-
 ### `compressPublicAssets`
 
 - Default: `{ gzip: false, brotli: false }`{lang=ts}
@@ -464,3 +463,17 @@ Rollup specific option.
 ### `commonJS`
 
 Rollup specific option. Specifies additional configuration for the rollup CommonJS plugin.
+
+## Preset options
+
+### `firebase`
+
+The options for the firebase functions preset. See [Preset Docs](/deploy/providers/firebase#options)
+
+### `vercel`
+
+The options for the vercel preset. See [Preset Docs](/deploy/providers/vercel)
+
+### `cloudflare`
+
+The options for the cloudflare preset. See [Preset Docs](/deploy/providers/cloudflare)