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>
32 lines
960 B
TypeScript
32 lines
960 B
TypeScript
import { Metadata } from 'next'
|
|
import { Link } from '~/i18n/navigation'
|
|
import { getTranslations } from 'next-intl/server'
|
|
|
|
// Force dynamic rendering to avoid useContext issues during static generation
|
|
export const dynamic = 'force-dynamic'
|
|
|
|
export const metadata: Metadata = {
|
|
title: 'Page not found / granblue.team',
|
|
description: 'The page you were looking for could not be found'
|
|
}
|
|
|
|
export default async function NotFound() {
|
|
const t = await getTranslations('common')
|
|
|
|
return (
|
|
<div className="error-container">
|
|
<div className="error-content">
|
|
<h1>Not Found</h1>
|
|
<p>The page you're looking for couldn't be found</p>
|
|
<div className="error-actions">
|
|
<Link href="/new" className="button primary">
|
|
Create a new party
|
|
</Link>
|
|
<Link href="/teams" className="button secondary">
|
|
Browse teams
|
|
</Link>
|
|
</div>
|
|
</div>
|
|
</div>
|
|
)
|
|
}
|