## 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>
35 lines
No EOL
1 KiB
TypeScript
35 lines
No EOL
1 KiB
TypeScript
import { NextRequest, NextResponse } from 'next/server';
|
|
import { postToApi, revalidate } from '~/app/lib/api-utils';
|
|
|
|
// Force dynamic rendering because postToApi uses cookies
|
|
export const dynamic = 'force-dynamic';
|
|
|
|
// POST handler for remixing a party
|
|
export async function POST(
|
|
request: NextRequest,
|
|
{ params }: { params: { shortcode: string } }
|
|
) {
|
|
try {
|
|
const { shortcode } = params;
|
|
const body = await request.json();
|
|
|
|
// Remix the party
|
|
const response = await postToApi(`/parties/${shortcode}/remix`, body || {});
|
|
|
|
// Revalidate the teams page since a new party was created
|
|
revalidate('/teams');
|
|
|
|
if (response.shortcode) {
|
|
// Revalidate the new party page
|
|
revalidate(`/p/${response.shortcode}`);
|
|
}
|
|
|
|
return NextResponse.json(response);
|
|
} catch (error: any) {
|
|
console.error(`Error remixing party with shortcode ${params.shortcode}`, error);
|
|
return NextResponse.json(
|
|
{ error: error.message || 'Failed to remix party' },
|
|
{ status: error.response?.status || 500 }
|
|
);
|
|
}
|
|
} |