@depup/nitro 3.0.260311-beta-depup.0

package/skills/nitro/docs/deploy/index.md

@@ -0,0 +1,64 @@
+# Deploy
+
+> Learn more about Nitro deploy providers.
+
+Nitro can generate different output formats suitable for different hosting providers from the same code base.
+Using built-in presets, you can easily configure Nitro to adjust its output format with almost no additional code or configuration!
+
+## Default output
+
+The default production output preset is [Node.js server](/deploy/runtimes/node).
+
+When running Nitro in development mode, Nitro will always use a special preset called `nitro-dev` using Node.js with ESM in an isolated Worker environment with behavior as close as possible to the production environment.
+
+## Zero-Config Providers
+
+When deploying to production using CI/CD, Nitro tries to automatically detect the provider environment and set the right one without any additional configuration required. Currently, the providers below can be auto-detected with zero config.
+
+- [aws amplify](/deploy/providers/aws-amplify)
+- [azure](/deploy/providers/azure)
+- [cloudflare](/deploy/providers/cloudflare)
+- [firebase app hosting](/deploy/providers/firebase#firebase-app-hosting)
+- [netlify](/deploy/providers/netlify)
+- [stormkit](/deploy/providers/stormkit)
+- [vercel](/deploy/providers/vercel)
+- [zeabur](/deploy/providers/zeabur)
+
+<warning>
+
+For Turborepo users, zero config detection will be interferenced by its Strict Environment Mode. You may need to allowing the variables explictly or use its Loose Environment Mode (with `--env-mode=loose` flag).
+</warning>
+
+Other built-in providers are available with an explicit preset, including [zephyr](/deploy/providers/zephyr).
+
+## Changing the deployment preset
+
+If you need to build Nitro against a specific provider, you can target it by defining an environment variable named `NITRO_PRESET` or `SERVER_PRESET`, or by updating your Nitro [configuration](/docs/configuration) or using `--preset` argument.
+
+Using the environment variable approach is recommended for deployments depending on CI/CD.
+
+**Example:** Defining a `NITRO_PRESET` environment variable
+
+```bash
+nitro build --preset cloudflare_pages
+```
+
+**Example:** Updating the `nitro.config.ts` file
+
+```ts
+import { defineNitroConfig } from "nitro/config";
+
+export default defineNitroConfig({
+  preset: 'cloudflare_pages'
+})
+```
+
+## Compatibility date
+
+Deployment providers regularly update their runtime behavior. Nitro presets are updated to support these new features.
+
+To prevent breaking existing deployments, Nitro uses compatibility dates. These dates let you lock in behavior at the project creation time. You can also opt in to future updates when ready.
+
+When you create a new project, the `compatibilityDate` is set to the current date. This setting is saved in your project's configuration.
+
+You should update the compatibility date periodically. Always test your deployment thoroughly after updating. Below is a list of key dates and their effects.

package/skills/nitro/docs/deploy/providers/alwaysdata.md

@@ -0,0 +1,50 @@
+# Alwaysdata
+
+> Deploy Nitro apps to alwaysdata.
+
+**Preset:** `alwaysdata`
+
+<read-more></read-more>
+
+## Set up application
+
+### Pre-requisites
+
+1. [Register a new profile](https://www.alwaysdata.com/en/register/) on alwaysdata platform if you don't have one.
+
+2. Get a free 100Mb plan to host your app.
+
+
+> [!NOTE]
+> Keep in mind your *account name* will be used to provide you a default URL in the form of `account_name.alwaysdata.net`, so choose it wisely. You can also link your existing domains to your account later or register as many accounts under your profile as you need.
+
+### Local deployment
+
+1. Build your project locally with `npm run build -- preset alwaysdata`
+
+2. [Upload your app](https://help.alwaysdata.com/en/remote-access/) to your account in its own directory (e.g. `$HOME/www/my-app`). You can use any protocol you prefer (SSH/FTP/WebDAV…) to do so.
+
+3. On your admin panel, [create a new site](https://admin.alwaysdata.com/site/add/) for your app with the following features:
+  - *Addresses*: `[account_name].alwaysdata.net`
+
+  - *Type*: Node.js
+
+  - *Command*: `node .output/server/index.mjs`
+
+  - *Working directory*: `www/my-app` (adapt it to your deployment path)
+
+  - *Environment*:
+
+    ```ini
+    NITRO_PRESET=alwaysdata
+    ```
+
+  - *Node.js version*: `Default version` is fine; pick no less than `20.0.0` (you can also [set your Node.js version globally](https://help.alwaysdata.com/en/languages/nodejs/configuration/#supported-versions))
+
+  - *Hot restart*: `SIGHUP`
+
+
+  <read-more></read-more>
+
+- Your app is now live at `http(s)://[account_name].alwaysdata.net`.
+

package/skills/nitro/docs/deploy/providers/aws-amplify.md

@@ -0,0 +1,81 @@
+# AWS Amplify
+
+> Deploy Nitro apps to AWS Amplify Hosting.
+
+**Preset:** `aws_amplify`
+
+<read-more></read-more>
+
+## Deploy to AWS Amplify Hosting
+
+<tip>
+
+Integration with this provider is possible with [zero configuration](/deploy/#zero-config-providers).
+</tip>
+
+1. Login to the [AWS Amplify Hosting Console](https://console.aws.amazon.com/amplify/)
+2. Click on "Get Started" > Amplify Hosting (Host your web app)
+3. Select and authorize access to your Git repository provider and select the main branch
+4. Choose a name for your app, make sure build settings are auto-detected and optionally set requirement environment variables under the advanced section
+5. Optionally, select Enable SSR logging to enable server-side logging to your Amazon CloudWatch account
+6. Confirm configuration and click on "Save and Deploy"
+
+## Advanced Configuration
+You can configure advanced options of this preset using `awsAmplify` option.
+
+```ts [nitro.config.ts]
+import { defineNitroConfig } from "nitro/config";
+
+export default defineNitroConfig({
+  awsAmplify: {
+      // catchAllStaticFallback: true,
+      // imageOptimization: { path: "/_image", cacheControl: "public, max-age=3600, immutable" },
+      // imageSettings: { ... },
+      // runtime: "nodejs18.x", // default: "nodejs18.x" | "nodejs16.x" | "nodejs20.x"
+  }
+})
+```
+
+### `amplify.yml`
+
+You might need a custom `amplify.yml` file for advanced configuration. Here are two template examples:
+
+<code-group>
+
+```yml [amplify.yml]
+version: 1
+frontend:
+  phases:
+    preBuild:
+      commands:
+        - nvm use 18 && node --version
+        - corepack enable && npx --yes nypm install
+    build:
+      commands:
+        - pnpm build
+  artifacts:
+    baseDirectory: .amplify-hosting
+    files:
+      - "**/*"
+```
+
+```yml [amplify.yml (monorepo)]
+version: 1
+applications:
+  - frontend:
+      phases:
+        preBuild:
+          commands:
+          - nvm use 18 && node --version
+          - corepack enable && npx --yes nypm install
+        build:
+          commands:
+            - pnpm --filter website1 build
+      artifacts:
+        baseDirectory: apps/website1/.amplify-hosting
+        files:
+          - '**/*'
+      buildPath: /
+    appRoot: apps/website1
+```
+</code-group>

package/skills/nitro/docs/deploy/providers/aws.md

@@ -0,0 +1,47 @@
+# AWS Lambda
+
+> Deploy Nitro apps to AWS Lambda.
+
+**Preset:** `aws_lambda`
+
+<read-more></read-more>
+
+Nitro provides a built-in preset to generate output format compatible with [AWS Lambda](https://aws.amazon.com/lambda/).
+The output entrypoint in `.output/server/index.mjs` is compatible with [AWS Lambda format](https://docs.aws.amazon.com/lex/latest/dg/lambda-input-response-format.html).
+
+It can be used programmatically or as part of a deployment.
+
+```ts
+import { handler } from './.output/server'
+
+// Use programmatically
+const { statusCode, headers, body } = handler({ rawPath: '/' })
+```
+
+## Inlining chunks
+
+Nitro output, by default uses dynamic chunks for lazy loading code only when needed. However this sometimes can not be ideal for performance. (See discussions in [nitrojs/nitro#650](https://github.com/nitrojs/nitro/pull/650)). You can enabling chunk inlining behavior using [`inlineDynamicImports`](/config#inlinedynamicimports) config.
+
+```ts [nitro.config.ts]
+import { defineNitroConfig } from "nitro/config";
+
+export default defineNitroConfig({
+  inlineDynamicImports: true
+});
+```
+
+## Response streaming
+
+<read-more></read-more>
+
+In order to enable response streaming, enable `awsLambda.streaming` flag:
+
+```ts [nitro.config.ts]
+import { defineNitroConfig } from "nitro/config";
+
+export default defineNitroConfig({
+  awsLambda: {
+    streaming: true
+  }
+});
+```

package/skills/nitro/docs/deploy/providers/azure.md

@@ -0,0 +1,72 @@
+# Azure
+
+> Deploy Nitro apps to Azure Static Web apps or functions.
+
+## Azure static web apps
+
+**Preset:** `azure-swa`
+
+<read-more></read-more>
+
+<note>
+
+Integration with this provider is possible with [zero configuration](/deploy/#zero-config-providers).
+</note>
+
+[Azure Static Web Apps](https://azure.microsoft.com/en-us/products/app-service/static) are designed to be deployed continuously in a [GitHub Actions workflow](https://docs.microsoft.com/en-us/azure/static-web-apps/github-actions-workflow). By default, Nitro will detect this deployment environment and enable the `azure` preset.
+
+### 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 to preview before deploying.
+
+```bash
+NITRO_PRESET=azure npx nypm@latest build
+npx @azure/static-web-apps-cli start .output/public --api-location .output/server
+```
+
+### Configuration
+
+Azure Static Web Apps are [configured](https://learn.microsoft.com/en-us/azure/static-web-apps/configuration) using the `staticwebapp.config.json` file.
+
+Nitro automatically generates this configuration file whenever the application is built with the `azure` preset.
+
+Nitro will automatically add the following properties based on the following criteria:
+| Property | Criteria | Default |
+| --- | --- | --- |
+| **[platform.apiRuntime](https://learn.microsoft.com/en-us/azure/static-web-apps/configuration#platform)** | Will automatically set to `node:16` or `node:14` depending on your package configuration. | `node:16` |
+| **[navigationFallback.rewrite](https://learn.microsoft.com/en-us/azure/static-web-apps/configuration#fallback-routes)** | Is always `/api/server` | `/api/server` |
+| **[routes](https://learn.microsoft.com/en-us/azure/static-web-apps/configuration#routes)** | All prerendered routes are added. Additionally, if you do not have an `index.html` file an empty one is created for you for compatibility purposes and also requests to `/index.html` are redirected to the root directory which is handled by `/api/server`.  | `[]` |
+
+### Custom configuration
+
+You can alter the Nitro generated configuration using `azure.config` option.
+
+Custom routes will be added and matched first. In the case of a conflict (determined if an object has the same route property), custom routes will override generated ones.
+
+### Deploy from CI/CD via GitHub actions
+
+When you link your GitHub repository to Azure Static Web Apps, a workflow file is added to the repository.
+
+When you are asked to select your framework, select custom and provide the following information:
+
+| Input | Value |
+| --- | --- |
+| **app_location** | '/' |
+| **api_location** | '.output/server' |
+| **output_location** | '.output/public' |
+
+If you miss this step, you can always find the build configuration section in your workflow and update the build configuration:
+
+```yaml [.github/workflows/azure-static-web-apps-<RANDOM_NAME>.yml]
+###### Repository/Build Configurations ######
+app_location: '/'
+api_location: '.output/server'
+output_location: '.output/public'
+###### End of Repository/Build Configurations ######
+```
+
+That's it! Now Azure Static Web Apps will automatically deploy your Nitro-powered application on push.
+
+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).

package/skills/nitro/docs/deploy/providers/cleavr.md

@@ -0,0 +1,33 @@
+# Cleavr
+
+> Deploy Nitro apps to Cleavr.
+
+**Preset:** `cleavr`
+
+<read-more></read-more>
+
+<note>
+
+Integration with this provider is possible with [zero configuration](/deploy/#zero-config-providers).
+</note>
+
+## Set up your web app
+
+In your project, set Nitro preset to `cleavr`.
+
+```js
+export default {
+  nitro: {
+    preset: 'cleavr'
+  }
+}
+```
+
+Push changes to your code repository.
+
+**In your Cleavr panel:**
+
+1. Provision a new server
+2. Add a website, selecting **Nuxt 3** as the app type
+3. In web app > settings > Code Repo, point to your project's code repository
+You're now all set to deploy your project!