GPT-5 finding
Next.js route/page props typed as Promise and awaited (type mismatch against Next conventions)
lowmaintainabilityhigh
- apps/web/app/benchmarks/page.tsx
- apps/web/app/receipts/[id]/page.tsx
- apps/web/app/receipts/[id]/page.tsx
Next.js app router provides plain objects for params/searchParams, not Promises. Awaiting them works at runtime (await returns non-promises verbatim) but it reduces type-safety, can mask real async boundaries, and diverges from Next’s documented types, making future refactors riskier.
Recommendation
Adjust types to match Next.js conventions and remove unnecessary awaits: - BenchmarksPage: `({ searchParams }: { searchParams?: SearchParams })` and use `const params = searchParams ?? {}`. - Receipt pages: `generateMetadata({ params }: { params: RouteParams })` and `ReceiptDetailPage({ params }: { params: RouteParams })`, then use params directly.