Skip to content

Waku

Prisma.Website.Waku builds a Waku React Server Components app with the shared Node target. Its RSC server, client assets, and SSG pages run on Bun in Prisma Compute after a tar.gz upload. There is no Docker image or registry.

Install

Section titled “Install”

Install the build-time integration in your project; the resource loads its /waku and /waku/node exports:

Terminal window
pnpm add -D https://pkg.alchemy.run/@alchemy.run/frontend-frameworks/pr:2930:a10573e @vercel/nft

Configure Waku

Section titled “Configure Waku”

A fresh project needs no deployment config. If present, waku.config.ts loads natively, including plugins in its vite field:

waku.config.ts
import tailwindcss from "@tailwindcss/vite";
import { defineConfig } from "waku/config";


export default defineConfig({
  basePath: "/",
  vite: { plugins: [tailwindcss()] },
});

Waku does not load a standalone vite.config.ts. Put Vite config in waku.config.ts. Don’t set unstable_adapter: the shared Node target owns it and rejects a conflicting adapter.

The resource’s waku bag overrides srcDir, distDir, or basePath from the file:

export const Website = Prisma.Website.Waku("Website", {
  waku: { basePath: "/docs/" },
});

Declare the Website

Section titled “Declare the Website”
alchemy.run.ts
import * as Prisma from "@alchemy.run/prisma";


export const Website = Prisma.Website.Waku("Website");

rootDir defaults to ".". A live deployment creates a database-less Prisma project if project is omitted; pass an existing project to share it with other apps.

Add it to the Stack

Section titled “Add it to the Stack”
alchemy.run.ts
import * as Alchemy from "alchemy";
import * as Effect from "effect/Effect";


export default Alchemy.Stack(
  "MyWakuSite",
  { providers: Prisma.providers(), state: Alchemy.localState() },
  Effect.gen(function* () {
    const site = yield* Website;
    return { url: site.url };
  }),
);

Pages configured with render: "static" are generated at build time and served at extensionless URLs such as /about. Dynamic pages and API routes run in Compute. site.url is the live endpoint.

Add environment variables

Section titled “Add environment variables”
export const Website = Prisma.Website.Waku("Website", {
  env: {
    GREETING: "Hello from Alchemy!",
    API_BASE: "https://api.example.com",
  },
});

env accepts strings or Redacted values. It is applied before build and dev, and passed to Compute. Client inlining follows the framework’s rules; do not expose secrets in public keys.

Read the environment in server code

Section titled “Read the environment in server code”
src/pages/index.tsx
export default async function HomePage() {
  return <h1>{process.env.GREETING ?? "hello"}</h1>;
}


export const getConfig = async () => ({ render: "dynamic" }) as const;

The RSC server runs on Bun. Server components and API routes can read process.env; static pages capture those values during prerendering.

Local dev

Section titled “Local dev”

alchemy dev runs Waku’s own server with HMR instead of deploying. The Website creates no Prisma resources. Opt into the live path with:

export const Website = Prisma.Website.Waku("Website").pipe(
  Alchemy.remote(),
);

Custom domain

Section titled “Custom domain”
const site = yield* Prisma.Website.Waku("Web", {
  domain: "app.example.com",
});

domain creates Prisma.CustomDomain and makes site.url the HTTPS hostname. Configure returned DNS records yourself and verify status before cutover; see Custom domains.

Where next

Section titled “Where next”