## Summary - Fixes Railway deployment build failures caused by dynamic server usage errors - Marks routes that use runtime features as `force-dynamic` to prevent static generation attempts - Creates proper error pages to handle 404/500 scenarios ## Problem The build was failing with "Dynamic server usage" errors because Next.js was trying to statically generate pages that use runtime features like: - `cookies()` for authentication - `searchParams` for filtering - Dynamic data fetching that requires request-time context ## Solution Added `export const dynamic = 'force-dynamic'` to: ### API Routes - `/api/jobs/route.ts` - uses searchParams - `/api/jobs/skills/route.ts` - uses cookies via fetchFromApi - `/api/version/route.ts` - uses cookies via fetchFromApi - `/api/raids/groups/route.ts` - uses cookies via fetchFromApi - `/api/parties/route.ts` - uses searchParams and cookies - `/api/parties/[shortcode]/route.ts` - uses cookies - `/api/parties/[shortcode]/remix/route.ts` - uses cookies ### Page Components - `/app/[locale]/teams/page.tsx` - uses searchParams - `/app/[locale]/new/page.tsx` - fetches dynamic data - `/app/[locale]/saved/page.tsx` - uses cookies and searchParams - Additional pages to avoid useContext errors during static generation ### Error Handling - Created `/pages/_error.tsx` - Simple error page without i18n complexity - Created `/app/not-found.tsx` - App Router 404 page ## Test plan - [x] Build completes successfully locally with `npm run build` - [ ] Deploy to Railway staging environment - [ ] Verify all dynamic routes work correctly - [ ] Check error pages display properly 🤖 Generated with [Claude Code](https://claude.ai/code) Co-authored-by: Claude <noreply@anthropic.com>
68 lines
No EOL
2.1 KiB
TypeScript
68 lines
No EOL
2.1 KiB
TypeScript
import { Metadata } from 'next'
|
|
import React from 'react'
|
|
import { getTeams as fetchTeams, getRaidGroups } from '~/app/lib/data'
|
|
import TeamsPageClient from './TeamsPageClient'
|
|
|
|
// Force dynamic rendering because we use searchParams
|
|
export const dynamic = 'force-dynamic'
|
|
|
|
// Metadata
|
|
export const metadata: Metadata = {
|
|
title: 'Discover teams / granblue.team',
|
|
description: 'Save and discover teams to use in Granblue Fantasy and search by raid, element or recency',
|
|
}
|
|
|
|
export default async function TeamsPage({
|
|
searchParams
|
|
}: {
|
|
searchParams: { element?: string; raid?: string; recency?: string; page?: string }
|
|
}) {
|
|
try {
|
|
// Extract query parameters with type safety
|
|
const element = searchParams.element ? parseInt(searchParams.element, 10) : undefined;
|
|
const raid = searchParams.raid;
|
|
const recency = searchParams.recency;
|
|
const page = searchParams.page ? parseInt(searchParams.page, 10) : 1;
|
|
|
|
// Parallel fetch data with Promise.all for better performance
|
|
const [teamsData, raidGroupsData] = await Promise.all([
|
|
fetchTeams({ element, raid, recency, page }),
|
|
getRaidGroups()
|
|
]);
|
|
|
|
// Prepare data for client component
|
|
const initialData = {
|
|
teams: teamsData.results || [],
|
|
raidGroups: raidGroupsData || [],
|
|
pagination: {
|
|
current_page: page,
|
|
total_pages: teamsData.meta?.total_pages || 1,
|
|
record_count: teamsData.meta?.count || 0
|
|
}
|
|
};
|
|
|
|
return (
|
|
<div className="teams">
|
|
{/* Pass server data to client component */}
|
|
<TeamsPageClient
|
|
initialData={initialData}
|
|
initialElement={element}
|
|
initialRaid={raid}
|
|
initialRecency={recency}
|
|
/>
|
|
</div>
|
|
);
|
|
} catch (error) {
|
|
console.error("Error fetching teams data:", error);
|
|
|
|
// Fallback data for error case
|
|
return (
|
|
<div className="teams">
|
|
<TeamsPageClient
|
|
initialData={{ teams: [], raidGroups: [], pagination: { current_page: 1, total_pages: 1, record_count: 0 } }}
|
|
error={true}
|
|
/>
|
|
</div>
|
|
);
|
|
}
|
|
} |