Justin Edmund
2f757fc2a4
- Add 'force-dynamic' export to API routes using cookies/searchParams - Add 'force-dynamic' export to page components using dynamic features - Create proper error pages without i18n complexity - Fix "Dynamic server usage" errors during static generation Routes now properly marked as dynamic will render at request time instead of failing during build-time static generation. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com>
35 lines
No EOL
1.1 KiB
TypeScript
35 lines
No EOL
1.1 KiB
TypeScript
import { Metadata } from 'next'
|
|
import Link from 'next/link'
|
|
|
|
// Force dynamic rendering to avoid useContext issues during static generation
|
|
export const dynamic = 'force-dynamic'
|
|
|
|
export const metadata: Metadata = {
|
|
title: 'Server Error / granblue.team',
|
|
description: 'The server encountered an internal error and was unable to complete your request'
|
|
}
|
|
|
|
export default function ServerErrorPage() {
|
|
return (
|
|
<div className="error-container">
|
|
<div className="error-content">
|
|
<h1>Internal Server Error</h1>
|
|
<p>The server encountered an internal error and was unable to complete your request.</p>
|
|
<p>Our team has been notified and is working to fix the issue.</p>
|
|
<div className="error-actions">
|
|
<Link href="/teams" className="button primary">
|
|
Browse teams
|
|
</Link>
|
|
<a
|
|
href="https://discord.gg/qyZ5hGdPC8"
|
|
target="_blank"
|
|
rel="noreferrer noopener"
|
|
className="button secondary"
|
|
>
|
|
Report on Discord
|
|
</a>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
)
|
|
} |