fix: Mark account layout as dynamic to prevent static generation
From the PR description
Problem
The account pages (including /account/api-keys) were still being statically generated at build time, causing the build to fail with "supabaseKey is required" error. The export const dynamic = "force-dynamic" on the individual page wasn't sufficient because the parent layout was still being statically generated.
Solution
Added export const dynamic = "force-dynamic" to the account layout (src/app/(pages)/account/layout.tsx) to ensure all account pages and their children are rendered dynamically at request time instead of being prerendered at build time.
Our analysis
Force dynamic rendering for account pages to unblock the build — read the full analysis →
Think the analysis missed something the PR description covers?
Commits in this PR (1)
| SHA | Subject | Author | Date | |
|---|---|---|---|---|
28a6fae3 | fix: Mark account layout as dynamic to prevent static generation | Railway Agent | 2026-06-28 | ↗ GitHub |
commit body## Problem The account pages (including `/account/api-keys`) were still being statically generated at build time, causing the build to fail with "supabaseKey is required" error. The `export const dynamic = "force-dynamic"` on the individual page wasn't sufficient because the parent layout was still being statically generated. ## Solution Added `export const dynamic = "force-dynamic"` to the account layout (`src/app/(pages)/account/layout.tsx`) to ensure all account pages and their children are rendered dynamically at request time instead of being prerendered at build time. | ||||
Capture this PR into my fork
Download a Markdown prompt that tells Claude how to port every
commit in this PR into your working tree. Run it via
claude -p < capture-pull-6.md from
inside the repo you want the changes in.