fix: Mark api-keys page as dynamic to skip static generation
From the PR description
Problem
The frontend build was failing with:
Error: supabaseKey is required.
The /account/api-keys page was being statically generated at build time, which required Supabase credentials during the build process. Since this is a protected page that requires authentication, it should be rendered dynamically at request time instead.
Solution
Added export const dynamic = "force-dynamic" to the api-keys page to skip static generation and render it on-demand when users request it.
Our analysis
Force dynamic rendering on the API keys account page — read the full analysis →
Think the analysis missed something the PR description covers?
Commits in this PR (1)
| SHA | Subject | Author | Date | |
|---|---|---|---|---|
2f484791 | fix: Mark api-keys page as dynamic to skip static generation | Railway Agent | 2026-06-28 | ↗ GitHub |
commit body## Problem The frontend build was failing with: ``` Error: supabaseKey is required. ``` The `/account/api-keys` page was being statically generated at build time, which required Supabase credentials during the build process. Since this is a protected page that requires authentication, it should be rendered dynamically at request time instead. ## Solution Added `export const dynamic = "force-dynamic"` to the api-keys page to skip static generation and render it on-demand when users request it. | ||||
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-3.md from
inside the repo you want the changes in.