import type { InputProps } from "alchemy/Input";
import * as Namespace from "alchemy/Namespace";
import { makeFrameworkSite, type FrameworkSiteProps } from "./FrameworkSite.ts";
/** The framework-integration package that drives the Nuxt build. */
export const NUXT_FRAMEWORK_SPECIFIER = "@alchemy.run/frontend-frameworks/nuxt";
/** The AWS Lambda deploy target for the Nuxt build. */
export const NUXT_AWS_TARGET_SPECIFIER = "@alchemy.run/frontend-frameworks/nuxt/aws";
/** The Node deploy target for the Lambda Web Function server (the default). */
export const NUXT_WEB_TARGET_SPECIFIER = "@alchemy.run/frontend-frameworks/nuxt/node";
export type NuxtProps = FrameworkSiteProps<{
/**
* Nuxt config overrides merged over the project's own `nuxt.config.ts`
* (the highest-priority c12 layer — a value here wins over the file).
* Use it for deploy-time values the config file can't express, e.g.
* per-stage `runtimeConfig`; `nuxt.config.ts` remains the primary home
* for everything else.
*
* Must be JSON-serializable — no functions, plugins, or modules (the
* value persists in state and participates in the rebuild hash).
* `nitro.preset` is always owned by the deploy target and cannot be
* overridden here.
*/
nuxt?: Record<string, unknown>;
}>;
/**
* Deploy a Nuxt application to AWS: the nitro server on a Lambda Web
* Function, static assets (prerendered pages included) in S3, and a
* CloudFront distribution whose edge router serves uploaded files from S3
* and forwards everything else to the server.
*
* The server runs on a Lambda Web Function: the framework's Node server
* (built with the `@alchemy.run/frontend-frameworks/nuxt/node` deploy
* target) serves many requests per environment and streams responses. Set
* `server: "function"` to use a Lambda Function behind a streaming Function
* URL instead, built with the `/aws` target below, for Regions without Web
* Functions.
*
* The build runs through `@alchemy.run/frontend-frameworks/nuxt` with the
* `@alchemy.run/frontend-frameworks/nuxt/aws` deploy target (nitro's `aws-lambda` preset,
* streaming enabled) — both must be installed in your project.
*
* ### Creating Nuxt Sites
* **Example:** Basic Nuxt App
* ```typescript
* const site = yield* AWS.Website.Nuxt("Web", {
* rootDir: "./app",
* });
* ```
*
* **Example:** Custom Domain
* ```typescript
* const site = yield* AWS.Website.Nuxt("Web", {
* rootDir: "./app",
* domain: {
* name: "app.example.com",
* hostedZoneId: zone.hostedZoneId,
* },
* });
* ```
*
* ### Server Configuration
* **Example:** Tune The Server Function
* ```typescript
* const site = yield* AWS.Website.Nuxt("Web", {
* rootDir: "./app",
* memorySize: 2048,
* env: {
* NUXT_PUBLIC_API_BASE: api.url,
* },
* });
* ```
*
* ### Config Overrides
* `nuxt.config.ts` is the primary home for Nuxt configuration — it loads
* natively. The `nuxt` prop layers deploy-time overrides on top (the
* highest-priority c12 layer) for values the file can't express, like
* per-stage settings. The bag must be JSON-serializable — no functions,
* plugins, or modules — and `nitro.preset` stays owned by the deploy
* target.
*
* **Example:** Deploy-time config overrides
* ```typescript
* const site = yield* AWS.Website.Nuxt("Web", {
* rootDir: "./app",
* nuxt: {
* app: { baseURL: "/docs/" },
* runtimeConfig: {
* public: { apiBase: "https://api.example.com" },
* },
* },
* });
* ```
*
* @resource
*/
export const Nuxt = (id: string, props: InputProps<NuxtProps, "server"> = {}) => {
const p = props as NuxtProps;
return makeFrameworkSite(id, props, {
name: "Nuxt",
framework: NUXT_FRAMEWORK_SPECIFIER,
target: NUXT_AWS_TARGET_SPECIFIER,
webTarget: NUXT_WEB_TARGET_SPECIFIER,
options: p.nuxt !== undefined ? { nuxt: p.nuxt } : undefined,
}).pipe(Namespace.push(id));
};