From 0ec150d703313b1fc0f88bbc4cbc6ef122f1c62e Mon Sep 17 00:00:00 2001
From: Aravind <aravind@tenext.in>
Date: Mon, 13 Jul 2026 20:09:35 +0530
Subject: [PATCH] Revert to static export output for nginx deploy pipeline

output: "standalone" (a8f4b23) produces a Node server bundle with no
server.js at the path the deploy Dockerfile expects. The deploy repo's
Dockerfile now runs nginx serving static files (d808317), which requires
a static export (out/), not a standalone server bundle.
---
 next.config.ts | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/next.config.ts b/next.config.ts
index e0db6fc..0338981 100644
--- a/next.config.ts
+++ b/next.config.ts
@@ -14,7 +14,7 @@ const nextConfig: NextConfig = {
   turbopack: {
     root: path.resolve(__dirname),
   },
-  output: "standalone",
+  output: "export",
   // Required by the How It Works 3D experience. React StrictMode double-invokes
   // mount/effects in dev, which tears down and re-creates the WebGL context of
   // the heavy 32MB scene mid-initialization — the context is lost ("THREE.