Skip to content

Nuxt

Neon.Website.Nuxt builds Nuxt with Nitro’s Node target, then replaces the listening wrapper with a Node 24 Fetch entry for Neon Functions. SSR and public assets ship in the Function ZIP, not a container or S3 website.

Prepare the app

Section titled “Prepare the app”

Use an existing Nuxt app or the runnable Nuxt example. Configure deployment credentials, then install in the app directory:

Install Alchemy and its matching Effect dependencies first; use Node 24 for this build toolchain.

Terminal window
pnpm add -D @alchemy.run/frontend-frameworks @vercel/nft

Keep modules and application settings in nuxt.config.*. Do not override nitro.preset: the target owns it. The nuxt resource prop accepts serializable config overrides; keep functions and plugin instances in the config file.

Define the stack

Section titled “Define the stack”
alchemy.run.ts
import * as Alchemy from "alchemy";
import * as Neon from "alchemy/Neon";
import * as Effect from "effect/Effect";


export default Alchemy.Stack(
  "NeonNuxt",
  { providers: Neon.providers(), state: Alchemy.localState() },
  Effect.gen(function* () {
    const site = yield* Neon.Website.Nuxt("Web", {
      rootDir: ".",
    });
    return { url: site.url };
  }),
);

Nitro handles server routes; built public files are served from the same Function. Use Nuxt’s runtimeConfig for application configuration and its normal NUXT_* environment mapping. Values in runtimeConfig.public are browser-visible. The Website’s env is also available during build and native development.

Develop and attempt deployment

Section titled “Develop and attempt deployment”
Terminal window
pnpm exec alchemy dev
pnpm exec alchemy deploy
pnpm exec alchemy destroy

Run separately, destroying when finished. Dev uses Nuxt’s native server and HMR, returns a local URL, and creates no implicit Project or Function. Append .pipe(Alchemy.remote()) to the Website Effect to opt into live deployment during dev.

Live deployment creates an Ohio Project when scope is omitted. Set either project or branch for an existing backend; choose Ohio when adding storage. Read scope and credentials before passing backend tokens to application code.

No CDN, durable Nitro cache, or image-optimization service is provisioned. Domain registration does not validate TLS. See the shared deployment limits.

Reference

Section titled “Reference”