framework
Next.js Errors
Next.js errors: 'Hydration failed', 'Module not found', 'getServerSideProps' failures, ISR revalidation errors, 'Image Optimization' errors, 'Failed to compile', 'Error: Connection terminated'.
Next.js error sources: hydration mismatches (server vs client HTML), App Router server/client component boundaries, ISR fetch failures, edge runtime constraints (no Node APIs), Image Optimization remote pattern denials. Hydration errors are usually `Date.now()`, `Math.random()`, browser-only APIs, or mismatched HTML tags between server and client renders.
Runtime (2)
-
FUNCTION_INVOCATION_TIMEOUT504Timed OutA Vercel serverless function (a Next.js API route, server action, or `getServerSideProps`) didn't return a response within the plan's max execution time — 10s on Hobby, 60s on Pro, 900s on Enterprise. Vercel kills the invocation and returns 504. -
hydration_failedHydration FailedThe HTML React rendered on the server doesn't match what React tries to render on the client during hydration. The two trees disagree about a node, so React throws and falls back to a full client re-render.
Build (1)
Official docs
https://nextjs.org/docs/messages
Support
https://nextjs.org/docs