Skip to content

fix(deploy): opt out of standalone output on Vercel #2

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
SupaOhm merged 1 commit into from
Aug 5, 2026
Merged

fix(deploy): opt out of standalone output on Vercel #2

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 4 additions & 1 deletion next.config.ts
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,10 @@
import type { NextConfig } from "next";

const nextConfig: NextConfig = {
output: "standalone",
// `standalone` exists for the Docker image, which copies `.next/standalone`
// and runs `node server.js`. Vercel builds its own output and does not want
// it, so opt out there via the `VERCEL` build env var.
output: process.env.VERCEL ? undefined : "standalone",
Comment on lines +4 to +7
reactStrictMode: true,
typedRoutes: true,
// Pin the workspace root so it can never be inferred outside this repo.
Expand Down