refactor!: remove legacy presets and aliases (#3202)

Author: pi0

docs/1.guide/00.migration.md

@@ -80,6 +80,27 @@ This feature had been removed.
 
 Use a regular `.ts` file in your server directory and import it directly.
 
+## Preset updates
+
+Nitro presets have been updated for the latest compatibility.
+
+Some (legacy) presets have been removed or renamed.
+
+| Old Preset                   | New Preset                    |
+|------------------------------|-------------------------------|
+| `node`                       | `node-middleware` (export changed to `middleware`) |
+| `cloudflare`, `cloudflare_worker`, `cloudflare_module_legacy` | `cloudflare_module`           |
+| `deno-server-legacy`         | `deno_server` with Deno v2    |
+| `netlify-builder`            | `netlify_functions` or `netlify_edge` |
+| `vercel-edge`                | `vercel` with Fluid compute enabled |
+| `azure`, `azure_functions`   | `azure_swa`                   |
+| `firebase`                   | `firebase-functions`          |
+| `iis`                        | `iis-handler`                 |
+| `deno`                       | `deno-deploy`                 |
+| `edgio`                      | `layer0`                      |
+| `cli`                        | Removed due to lack of use |
+| `service_worker`             | Removed due to instability |
+
 ## Removed Subpath Exports
 
 Nitro v2 introduced multiple subpath exports, some of which have been removed:

docs/2.deploy/20.providers/azure.md

@@ -4,7 +4,7 @@
 
 ## Azure static web apps
 
-**Preset:** `azure`
+**Preset:** `azure-swa`
 
 :read-more{title="Azure Static Web Apps" to="https://azure.microsoft.com/en-us/products/app-service/static"}
 
@@ -70,99 +70,3 @@ That's it! Now Azure Static Web Apps will automatically deploy your Nitro-powere
 
 If you are using runtimeConfig, you will likely want to configure the corresponding [environment variables on Azure](https://docs.microsoft.com/en-us/azure/static-web-apps/application-settings).
 
-## Azure functions
-
-**Preset:** `azure_functions`
-
-::important
-If you encounter any issues, please ensure you're using a Node.js 16+ runtime. You can find more information about [how to set the Node version in the Azure docs](https://docs.microsoft.com/en-us/azure/azure-functions/functions-reference-node?tabs=v2#setting-the-node-version).
-Please see [nitrojs/nitro#2114](https://github.com/nitrojs/nitro/issues/2114) for some common issues.
-::
-
-### Local preview
-
-Install [Azure Functions Core Tools](https://docs.microsoft.com/en-us/azure/azure-functions/functions-run-local) if you want to test locally.
-
-You can invoke a development environment from the serverless directory.
-
-```bash
-NITRO_PRESET=azure_functions npx nypm@latest build
-cd .output
-func start
-```
-
-You can now visit `http://localhost:7071/` in your browser and browse your site running locally on Azure Functions.
-
-### Deploy from your local machine
-
-To deploy, just run the following command:
-
-```bash
-# To publish the bundled zip file
-az functionapp deployment source config-zip -g <resource-group> -n <app-name> --src dist/deploy.zip
-# Alternatively you can publish from source
-cd dist && func azure functionapp publish --javascript <app-name>
-```
-
-### Deploy from CI/CD via GitHub actions
-
-First, obtain your Azure Functions Publish Profile and add it as a secret to your GitHub repository settings following [these instructions](https://github.com/Azure/functions-action#using-publish-profile-as-deployment-credential-recommended).
-
-Then create the following file as a workflow:
-
-```yaml [.github/workflows/azure.yml]
-name: azure
-on:
-  push:
-    branches:
-      - main
-  pull_request:
-    branches:
-      - main
-jobs:
-  deploy:
-    runs-on: ${{ matrix.os }}
-    strategy:
-      matrix:
-        os: [ ubuntu-latest ]
-        node: [ 14 ]
-    steps:
-      - uses: actions/setup-node@v2
-        with:
-          node-version: ${{ matrix.node }}
-
-      - name: Checkout
-        uses: actions/checkout@master
-
-      - name: Get yarn cache directory path
-        id: yarn-cache-dir-path
-        run: echo "::set-output name=dir::$(yarn cache dir)"
-
-      - uses: actions/cache@v2
-        id: yarn-cache
-        with:
-          path: ${{ steps.yarn-cache-dir-path.outputs.dir }}
-          key: ${{ runner.os }}-yarn-${{ hashFiles('**/yarn.lock') }}
-          restore-keys: |
-            ${{ runner.os }}-yarn-azure
-
-      - name: Install Dependencies
-        if: steps.cache.outputs.cache-hit != 'true'
-        run: yarn
-
-      - name: Build
-        run: npm run build
-        env:
-          NITRO_PRESET: azure_functions
-
-      - name: 'Deploy to Azure Functions'
-        uses: Azure/functions-action@v1
-        with:
-          app-name: <your-app-name>
-          package: .output/deploy.zip
-          publish-profile: ${{ secrets.AZURE_FUNCTIONAPP_PUBLISH_PROFILE }}
-```
-
-### Optimizing Azure functions
-
-Consider [turning on immutable packages](https://docs.microsoft.com/en-us/azure/app-service/deploy-run-package) to support running your app from the zip file. This can speed up cold starts.

docs/2.deploy/20.providers/cloudflare.md

@@ -1,17 +1,28 @@
 # Cloudflare
 
-> Deploy Nitro apps to Cloudflare.
+> Deploy Nitro apps to Cloudflare Workers and Pages.
 
-## Cloudflare Pages
+## Cloudflare Worker
 
-**Preset:** `cloudflare_pages`
+**Preset:** `cloudflare_module`
 
-:read-more{title="Cloudflare Pages" to="https://pages.cloudflare.com/"}
+:read-more{title="Cloudflare Workers" to="https://developers.cloudflare.com/workers/"}
+
+::note
+This preset uses the [module worker syntax](https://developers.cloudflare.com/workers/learning/migrating-to-module-workers/) for deployment.
+::
 
 ::note
-This is the recommended preset for Cloudflare deployments, please consider using the alternative ones if you need special features.
+This preset benefits [Static Assets](https://developers.cloudflare.com/workers/static-assets/) by default.
 ::
 
+
+## Cloudflare Pages
+
+**Preset:** `cloudflare_pages`
+
+:read-more{title="Cloudflare Pages" to="https://pages.cloudflare.com/"}
+
 ::note
 Integration with this provider is possible with [zero configuration](/deploy#zero-config-providers).
 ::
@@ -65,43 +76,6 @@ Then you can deploy the application with:
 
 :pm-x{command="wrangler pages deploy dist"}
 
-## Cloudflare Module Workers
-
-**Preset:** `cloudflare_module`
-
-::note
-**Note:** This preset uses the [module worker syntax](https://developers.cloudflare.com/workers/learning/migrating-to-module-workers/) for deployment.
-::
-
-When using Workers you will need a `wrangler.toml` file, in your root directory. To using Workers with [Static Assets](https://developers.cloudflare.com/workers/static-assets/) (BETA with [limitations](https://developers.cloudflare.com/workers/static-assets/#limitations)), you also need a compatibility date set to `2024-09-19` or later, in your `wrangler.toml` file and nitro configuration file.
-
-The following shows a typical `wrangler.toml` file and a `nitro.config.ts` file for a Nitro application:
-
-::code-group
-
-```ts [nitro.config.ts]
-export default defineNitroConfig({
-    compatibilityDate: "2024-09-19",
-})
-```
-
-```ts [nuxt.config.ts]
-export default defineNuxtConfig({
-    compatibilityDate: "2024-09-19",
-})
-```
-
-::
-
-```ini [wrangler.toml]
-name = "nitro-app"
-compatibility_date = "2024-09-19"
-main = "./.output/server/index.mjs"
-assets = { directory = "./.output/public/", binding = "ASSETS" }
-```
-
-
-
 ## Runtime hooks
 
 You can use [runtime hooks](/guide/plugins#nitro-runtime-hooks) below in order to extend [worker handlers](https://developers.cloudflare.com/workers/runtime-apis/handlers/).
@@ -158,19 +132,6 @@ and publish it:
 
 :pm-x{command="wrangler deploy"}
 
-## Cloudflare Service Workers
-
-**Preset:** `cloudflare`
-
-::note
-**Note:** This preset uses the [service worker syntax](https://developers.cloudflare.com/workers/learning/service-worker/) for deployment.
-::
-
-::warning
-**Note:** This preset is deprecated.
-::
-
-The way this preset works is identical to that of the `cloudflare_module` one presented above, with the only difference being that such preset inherits all the [disadvantages](https://developers.cloudflare.com/workers/reference/migrate-to-module-workers/#advantages-of-migrating) that such syntax brings.
 
 ## Deploy within CI/CD using GitHub Actions
 

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

@@ -2,10 +2,6 @@
 
 > Deploy Nitro apps to Firebase hosting.
 
-::note
-You will need to be on the [**Blaze plan**](https://firebase.google.com/pricing) (Pay as you go) to get started.
-::
-
 <!--
 
 ## Firebase app hosting <sup>(beta)</sup>
@@ -42,9 +38,8 @@ You can integrate with this provider using [zero configuration](/deploy/#zero-co
 
 :read-more{title="Firebase Hosting" to="https://firebase.google.com/docs/hosting"}
 
-::important
-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).
-::
+> [!NOTE]
+> This preset uses [2nd gen](https://firebase.google.com/docs/functions/version-comparison#new-in-2nd-gen) firebase cloud functions
 
 ### Project Setup
 
@@ -144,78 +139,6 @@ If you installed the Firebase CLI globally, you can also run:
 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
-      // ...
-    }
-  }
-})
-```
-
-::
-
-::note
-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,
-    httpsOptions: {
-      region: 'europe-west1',
-      maxInstances: 3,
-    },
-  },
-});
-```
-
-```ts [nuxt.config.ts]
-export default defineNuxtConfig({
-  nitro: {
-    firebase: {
-      gen: 2,
-      httpsOptions: {
-        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:

docs/2.deploy/20.providers/iis.md

@@ -14,7 +14,7 @@
 
 ## Using IIS handler
 
-**Preset:** `iis_handler` / `iis`
+**Preset:** `iis_handler`
 
 You can use IIS http handler directly.
 

docs/2.deploy/20.providers/netlify.md

@@ -39,18 +39,6 @@ Nitro output can directly run the server at the edge. Closer to your users.
 Make sure the publish directory is set to `dist` when creating a new project.
 ::
 
-## On-demand builders
-
-**Preset:** `netlify_builder`
-
-::warning
-**Note:** This preset is deprecated. Instead, use the `netlify` preset with the `isr` route rule.
-::
-
-On-demand Builders are serverless functions used to generate web content as needed that’s automatically cached on Netlify’s Edge CDN. They enable you to build pages for your site when a user visits them for the first time and then cache them at the edge for subsequent visits.
-
-:read-more{title="Netlify On-demand Builders" to="https://docs.netlify.com/configure-builds/on-demand-builders/"}
-
 ## Custom deploy configuration
 
 You can provide additional deploy configuration using the `netlify` key inside `nitro.config`. It will be merged with built-in auto-generated config. Currently the only supported value is `images.remote_images`, for [configuring Netlify Image CDN](https://docs.netlify.com/image-cdn/create-integration/).

docs/2.deploy/20.providers/vercel.md

@@ -10,6 +10,10 @@
 Integration with this provider is possible with [zero configuration](/deploy/#zero-config-providers).
 ::
 
+::tip
+It is recommended to enable [Fluid compute](https://vercel.com/docs/functions/fluid-compute).
+::
+
 ## Deploy using git
 
 1. Push your code to your git repository (GitHub, GitLab, Bitbucket).
@@ -104,9 +108,3 @@ export default defineNitroConfig({
   },
 });
 ```
-
-## Vercel edge functions
-
-**Preset:** `vercel_edge` (deprecated)
-
-We recommend migrating to the default Node.js runtime and enabling [Fluid compute](https://vercel.com/docs/functions/fluid-compute).