Prisma.Website reference
Source:
src/Prisma/Website/Astro.ts
Astro SSR and prerendered pages on Prisma Compute. The Node target owns the adapter; omit adapter from astro.config.*. Set astro.output to “static” to prerender every page.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Astro: Creating a Website
Section titled “Astro: Creating a Website”const site = yield* Prisma.Website.Astro("Web", { rootDir: "./app",});Astro: Deployment Configuration
Section titled “Astro: Deployment Configuration”const site = yield* Prisma.Website.Astro("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});Astro: Static Output
Section titled “Astro: Static Output”const docs = yield* Prisma.Website.Astro("Docs", { rootDir: "./docs", astro: { output: "static" }, assets: { notFoundHandling: "404-page" },});Foldkit
Section titled “Foldkit”Source:
src/Prisma/Website/Foldkit.ts
Deploy a Foldkit Vite application to Prisma Compute with SPA routing. The project’s Foldkit Vite plugin drives the build; native Vite HMR runs during development without creating cloud resources.
Foldkit: Creating a Website
Section titled “Foldkit: Creating a Website”const site = yield* Prisma.Website.Foldkit("Web", { rootDir: "./app",});Foldkit: Multi-Page Routing
Section titled “Foldkit: Multi-Page Routing”const site = yield* Prisma.Website.Foldkit("Web", { assets: { notFoundHandling: "404-page" },});Nextjs
Section titled “Nextjs”Source:
src/Prisma/Website/Nextjs.ts
Next.js on Prisma Compute using next build and the existing Node custom-server target, not OpenNext. The artifact contains .next, public, configuration, and traced runtime dependencies, preserving installed package versions.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Nextjs: Creating a Website
Section titled “Nextjs: Creating a Website”const site = yield* Prisma.Website.Nextjs("Web", { rootDir: "./app",});Nextjs: Deployment Configuration
Section titled “Nextjs: Deployment Configuration”const site = yield* Prisma.Website.Nextjs("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});Source:
src/Prisma/Website/Nuxt.ts
Nuxt SSR and prerendered assets on Prisma Compute. The Node target owns Nitro’s node preset; do not override nitro.preset.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Nuxt: Creating a Website
Section titled “Nuxt: Creating a Website”const site = yield* Prisma.Website.Nuxt("Web", { rootDir: "./app",});Nuxt: Deployment Configuration
Section titled “Nuxt: Deployment Configuration”const site = yield* Prisma.Website.Nuxt("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});Octane
Section titled “Octane”Source:
src/Prisma/Website/Octane.ts
Octane SSR and client assets on Prisma Compute.
Prisma.Website.Octane selects hosting and automatically wraps Octane’s
default native Node output for Bun on Compute. Keep compiler and route
settings in octane.config.ts without an adapter. The legacy Node marker
adapter remains optional for existing projects.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Octane: Creating a Website
Section titled “Octane: Creating a Website”const site = yield* Prisma.Website.Octane("Web", { rootDir: "./app",});Octane: Deployment Configuration
Section titled “Octane: Deployment Configuration”const site = yield* Prisma.Website.Octane("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});ReactRouter
Section titled “ReactRouter”Source:
src/Prisma/Website/ReactRouter.ts
React Router SSR and browser assets on Prisma Compute using the existing Node framework target.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
ReactRouter: Creating a Website
Section titled “ReactRouter: Creating a Website”const site = yield* Prisma.Website.ReactRouter("Web", { rootDir: "./app",});ReactRouter: Deployment Configuration
Section titled “ReactRouter: Deployment Configuration”const site = yield* Prisma.Website.ReactRouter("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});SolidStart
Section titled “SolidStart”Source:
src/Prisma/Website/SolidStart.ts
SolidStart SSR and prerendered assets on Prisma Compute. The integration owns the Nitro plugin; omit nitroV2Plugin() from vite.config.* and configure prerendering through nitro.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
SolidStart: Creating a Website
Section titled “SolidStart: Creating a Website”const site = yield* Prisma.Website.SolidStart("Web", { rootDir: "./app",});SolidStart: Deployment Configuration
Section titled “SolidStart: Deployment Configuration”const site = yield* Prisma.Website.SolidStart("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});StaticSite
Section titled “StaticSite”Source:
src/Prisma/Website/StaticSite.ts
Build a static website with a shell command and serve it on Prisma Compute.
Only the output directory is packaged; the repository is never uploaded.
Native development declares no Prisma Project, Compute, or custom domain.
Alchemy.remote() opts into the live deployment during development.
StaticSite: Creating a Static Website
Section titled “StaticSite: Creating a Static Website”const site = yield* Prisma.Website.StaticSite("Blog", { command: "hugo --minify", outdir: "public",});StaticSite: Monorepos and Development
Section titled “StaticSite: Monorepos and Development”const site = yield* Prisma.Website.StaticSite("Web", { cwd: "apps/web", command: "npm run build", outdir: "dist", spa: true, dev: { command: "npm run dev" },});SvelteKit
Section titled “SvelteKit”Source:
src/Prisma/Website/SvelteKit.ts
SvelteKit SSR and prerendered assets on Prisma Compute. The Node target injects the adapter. For Kit v3, pass configuration through kit rather than a svelte.config.js file.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
SvelteKit: Creating a Website
Section titled “SvelteKit: Creating a Website”const site = yield* Prisma.Website.SvelteKit("Web", { rootDir: "./app",});SvelteKit: Deployment Configuration
Section titled “SvelteKit: Deployment Configuration”const site = yield* Prisma.Website.SvelteKit("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});TanStackStart
Section titled “TanStackStart”Source:
src/Prisma/Website/TanStackStart.ts
TanStack Start SSR and browser assets on Prisma Compute using the existing Node framework target.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
TanStackStart: Creating a Website
Section titled “TanStackStart: Creating a Website”const site = yield* Prisma.Website.TanStackStart("Web", { rootDir: "./app",});TanStackStart: Deployment Configuration
Section titled “TanStackStart: Deployment Configuration”const site = yield* Prisma.Website.TanStackStart("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});Vinext
Section titled “Vinext”Source:
src/Prisma/Website/Vinext.ts
Deploy a vinext application to Prisma Compute using vinext’s Vite build and vinext’s production Node server on Compute’s Bun runtime. Alchemy packages the build output and traced, locally installed runtime dependencies; no Dockerfile, registry, Wrangler, or OpenNext is required.
Native vinext dev development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use a live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Vinext: Creating a Website
Section titled “Vinext: Creating a Website”const site = yield* Prisma.Website.Vinext("Web", { rootDir: "./app", env: { GREETING: "Hello from vinext on Prisma!" },});Vinext: Deployment Configuration
Section titled “Vinext: Deployment Configuration”const site = yield* Prisma.Website.Vinext("Web", { project, domain: "www.example.com", compute: { destroyOldDeployment: true },});Vinext: Persistent Data Cache
Section titled “Vinext: Persistent Data Cache”The resource injects the data-cache adapter automatically. Set env.REDIS_URL
to use Redis; otherwise the cache is process-local
and is lost on restart. Prisma Compute does not provision a Redis store.
const site = yield* Prisma.Website.Vinext("Web", { env: { REDIS_URL: Redacted.make("rediss://user:password@cache.example.com:6379") },});Source:
src/Prisma/Website/Vite.ts
Static Vite assets served on Prisma Compute. The project’s Vite plugins and configuration drive the build; native Vite HMR runs during development.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Vite: Creating a Website
Section titled “Vite: Creating a Website”const site = yield* Prisma.Website.Vite("Web", { rootDir: "./app",});Vite: Deployment Configuration
Section titled “Vite: Deployment Configuration”const site = yield* Prisma.Website.Vite("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});Source:
src/Prisma/Website/Vocs.ts
Vocs documentation and its Waku RSC handler on Prisma Compute. Install Vocs and its Waku peers alongside the framework integration.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Vocs: Creating a Website
Section titled “Vocs: Creating a Website”const site = yield* Prisma.Website.Vocs("Web", { rootDir: "./app",});Vocs: Deployment Configuration
Section titled “Vocs: Deployment Configuration”const site = yield* Prisma.Website.Vocs("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});Source:
src/Prisma/Website/Waku.ts
Waku RSC and static pages on Prisma Compute. The Node target selects Waku’s node adapter; do not set unstable_adapter.
Native framework development and HMR run without Prisma cloud resources.
Apply Alchemy.remote() to use the live Compute deployment during dev.
Packaging requires the optional @vercel/nft peer dependency.
Waku: Creating a Website
Section titled “Waku: Creating a Website”const site = yield* Prisma.Website.Waku("Web", { rootDir: "./app",});Waku: Deployment Configuration
Section titled “Waku: Deployment Configuration”const site = yield* Prisma.Website.Waku("Web", { project, domain: "www.example.com", env: { API_BASE: "https://api.example.com" }, compute: { destroyOldDeployment: true },});