fix(whitelabel): force dynamic rendering for landing segment

waleedlatif1 · waleedlatif1 · commit b0602a29ecd4 · 2026-05-05T17:41:57.000-07:00
Client components in (landing) (e.g. Navbar) read NEXT_PUBLIC_BRAND_* via getEnv. Without this, SSR prerender would bake the build-time process.env values into HTML, mismatching window.__ENV after hydration in Docker runtime-env deployments. Cascades to all landing routes via the layout.
diff --git a/apps/sim/app/(landing)/layout.tsx b/apps/sim/app/(landing)/layout.tsx
@@ -16,6 +16,11 @@ export const metadata: Metadata = {
   },
 }
 
+/** Opt the landing segment out of static prerendering so client components like
+ * Navbar render with the live runtime env (e.g. Docker-injected `NEXT_PUBLIC_BRAND_*`)
+ * during SSR, avoiding hydration mismatches against `window.__ENV`. */
+export const dynamic = 'force-dynamic'
+
 /**
  * Landing page route-group layout.
  *

Original file line number	Diff line number	Diff line change
`@@ -16,6 +16,11 @@ export const metadata: Metadata = {`
`16`	`16`	`},`
`17`	`17`	`}`
`18`	`18`
	`19`	`+/** Opt the landing segment out of static prerendering so client components like`
	`20`	+ * Navbar render with the live runtime env (e.g. Docker-injected `NEXT_PUBLIC_BRAND_*`)
	`21`	+ * during SSR, avoiding hydration mismatches against `window.__ENV`. */
	`22`	`+export const dynamic = 'force-dynamic'`
	`23`	`+`
`19`	`24`	`/**`
`20`	`25`	`* Landing page route-group layout.`
`21`	`26`	`*`