Error map

Vercel FUNCTION_PAYLOAD_TOO_LARGE (413) Vercel: 413 FUNCTION_PAYLOAD_TOO_LARGE — Request Entity Too Large (4.5 MB limit)

Next.js · layer 1, On your device

Open the full error page →

Centre: this error. First ring: errors it is linked with (7). Outer ring: what those are linked with. Colours show the layer of a request each error belongs to. Click any dot to re-centre the map on it; hover to follow its connections. The centre dot opens the error page.

1 · On your device 2 · Network 4 · Application & API 7 · Build & delivery
Vercel FUNCTION_PAYLOAD_TOO_LARGE (413) — Vercel: 413 FUNCTION_PAYLOAD_TOO_LARGE — Request Entity Too Large (4.5 MB limit) (Next.js)Vercel FUNC…413 — HTTP 413 Content Too Large (Request Entity Too Large) (HTTP)413next build: fetch failed ECONNREFUSED (build-time API) — Next.js: Error occurred prerendering page "/blog" TypeError: fetch failed { cause: Error: connect ECONNREFUSED 127.0.0.1:3000 } (Next.js)next build: fetch f…Body exceeded 1 MB limit (Server Actions) — Next.js: Error: Body exceeded 1 MB limit. To configure the body size limit for Server Actions, see: https://nextjs.org/docs/app/api-reference/next-config-js/serverActions#bodysizelimit (Next.js)Body exceeded 1 MB …Vercel FUNCTION_INVOCATION_TIMEOUT (504) — Vercel: 504 GATEWAY_TIMEOUT — FUNCTION_INVOCATION_TIMEOUT: An error occurred with your deployment (Next.js)Vercel FUNCTION_INV…Vercel: Command "npm run build" exited with 1 — Vercel: Error: Command "npm run build" exited with 1 (Next.js)Vercel: Command "np…Edge Function size limit exceeded — Vercel: The Edge Function "middleware" size is 1.2 MB and your plan size limit is 1 MB. Learn More: https://vercel.link/edge-function-size (Next.js)Edge Function size …Prisma Client out of date on Vercel (prisma generate) — Vercel: PrismaClientInitializationError: Prisma has detected that this project was built on Vercel, which caches dependencies. This leads to an outdated Prisma Client (Next.js)Prisma Client out o…400 — HTTP 400 Bad Request (HTTP)400408 — HTTP 408 Request Timeout (HTTP)408411 — HTTP 411 Length Required (HTTP)411ELIFECYCLE — npm ERR! code ELIFECYCLE / Command failed with exit code 1 (npm)ELIFECYCLEgyp ERR! — gyp ERR! build error / node-gyp rebuild failed (npm)gyp ERR!ERR_OSSL_EVP_UNSUPPORTED — Error: error:0308010C:digital envelope routines::unsupported (Node.js)ERR_OSSL_EVP_UNSUPP…next build: JavaScript heap out of memory — Next.js: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (during next build) (Next.js)next build: JavaScr…Server actions must be async functions — Next.js: Error: Server actions must be async functions (Next.js)Server actions must…Failed to find Server Action — Next.js: Error: Failed to find Server Action "abc123". This request might be from an older or newer deployment (Next.js)Failed to find Serv…504 — HTTP 504 Gateway Timeout (HTTP)504Page is missing generateStaticParams() (output: export) — Next.js: Page "/blog/[slug]" is missing "generateStaticParams()" so it cannot be used with "output: export" config (Next.js)Page is missing gen…Module not found: Can't resolve 'x' (Next.js build) — Next.js: Module not found: Can't resolve '@/components/Button' / 'lodash' in '/app/src' (Next.js)Module not found: C…Failed to compile: ESLint errors during next build — Next.js: Failed to compile. ./src/app/page.tsx 12:7 Error: 'x' is assigned a value but never used. @typescript-eslint/no-unused-vars (Next.js)Failed to compile: …Dynamic Code Evaluation not allowed in Edge Runtime — Next.js: Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime (Next.js)Dynamic Code Evalua…The edge runtime does not support Node.js module — Next.js: The edge runtime does not support Node.js 'crypto' module / A Node.js module is loaded ('fs') which is not supported in the Edge Runtime (Next.js)The edge runtime do…Prisma P2002 — PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`) (Node.js)Prisma P2002Prisma P1001 — Error: P1001: Can't reach database server at `host`:`5432` (Node.js)Prisma P1001

Directly related (7)

413HTTP

HTTP 413 Content Too Large (Request Entity Too Large)

The request body is bigger than the server is willing to accept — usually a file upload over the configured limit.

next build: fetch failed ECONNREFUSED (build-time API)Next.js

Next.js: Error occurred prerendering page "/blog" TypeError: fetch failed { cause: Error: connect ECONNREFUSED 127.0.0.1:3000 }

During `next build` a page tried to fetch data from a server (often your own app or an API) that isn't running yet.

Body exceeded 1 MB limit (Server Actions)Next.js

Next.js: Error: Body exceeded 1 MB limit. To configure the body size limit for Server Actions, see: https://nextjs.org/docs/app/api-reference/next-config-js/serverActions#bodysizelimit

A Server Action (often a file upload) sent more than the default 1 MB request body.

Vercel FUNCTION_INVOCATION_TIMEOUT (504)Next.js

Vercel: 504 GATEWAY_TIMEOUT — FUNCTION_INVOCATION_TIMEOUT: An error occurred with your deployment

A Vercel Serverless Function ran longer than its max duration, so Vercel killed it.

Vercel: Command "npm run build" exited with 1Next.js

Vercel: Error: Command "npm run build" exited with 1

The Vercel build step failed; the real reason is printed in the build log above this line.

Edge Function size limit exceededNext.js

Vercel: The Edge Function "middleware" size is 1.2 MB and your plan size limit is 1 MB. Learn More: https://vercel.link/edge-function-size

Your middleware/Edge Function bundle is larger than the plan's size limit.

Prisma Client out of date on Vercel (prisma generate)Next.js

Vercel: PrismaClientInitializationError: Prisma has detected that this project was built on Vercel, which caches dependencies. This leads to an outdated Prisma Client

Vercel cached `node_modules`, so `prisma generate` didn't run and the generated client is stale or missing.

Two steps away (17)

400HTTP

HTTP 400 Bad Request

The server could not understand the request because its syntax, headers or body are malformed or invalid.

408HTTP

HTTP 408 Request Timeout

The server closed the connection because the client took too long to send the complete request.

411HTTP

HTTP 411 Length Required

The server refuses a request with a body but no Content-Length header.

ELIFECYCLEnpm

npm ERR! code ELIFECYCLE / Command failed with exit code 1

An npm script (build, start, test, postinstall) exited with an error. ELIFECYCLE is only the wrapper — the real error is printed…

gyp ERR!npm

gyp ERR! build error / node-gyp rebuild failed

A dependency with native C/C++ code couldn’t compile — missing build tools, Python, or an unsupported Node version.

ERR_OSSL_EVP_UNSUPPORTEDNode.js

Error: error:0308010C:digital envelope routines::unsupported

An old build tool (webpack 4, old react-scripts) uses a hash algorithm that OpenSSL 3 in Node 17+ disables.

next build: JavaScript heap out of memoryNext.js

Next.js: FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory (during next build)

Node ran out of memory while building a large Next.js app (or on a small CI/Vercel runner).

Server actions must be async functionsNext.js

Next.js: Error: Server actions must be async functions

A function marked `"use server"` isn't declared `async`.

Failed to find Server ActionNext.js

Next.js: Error: Failed to find Server Action "abc123". This request might be from an older or newer deployment

The browser called a Server Action ID the current server build doesn't know — usually a version skew after a deploy.

504HTTP

HTTP 504 Gateway Timeout

A proxy or gateway waited too long for the upstream server to respond and gave up.

Page is missing generateStaticParams() (output: export)Next.js

Next.js: Page "/blog/[slug]" is missing "generateStaticParams()" so it cannot be used with "output: export" config

A dynamic route can't be statically exported without telling Next.js which paths to generate.

Module not found: Can't resolve 'x' (Next.js build)Next.js

Next.js: Module not found: Can't resolve '@/components/Button' / 'lodash' in '/app/src'

Webpack/Turbopack couldn't resolve an import — wrong path/alias, missing dependency or case mismatch.

Failed to compile: ESLint errors during next buildNext.js

Next.js: Failed to compile. ./src/app/page.tsx 12:7 Error: 'x' is assigned a value but never used. @typescript-eslint/no-unused-vars

`next build` runs ESLint and fails the build on lint errors.

Dynamic Code Evaluation not allowed in Edge RuntimeNext.js

Next.js: Dynamic Code Evaluation (e. g. 'eval', 'new Function', 'WebAssembly.compile') not allowed in Edge Runtime

Code in middleware or an Edge route uses `eval`/`new Function`, which the Edge Runtime forbids.

The edge runtime does not support Node.js moduleNext.js

Next.js: The edge runtime does not support Node.js 'crypto' module / A Node.js module is loaded ('fs') which is not supported in the Edge Runtime

Middleware or an Edge route imported a Node.js built-in (`fs`, `crypto`, `path`, `net`) that isn't available on the Edge.

Prisma P2002Node.js

PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`)

A Prisma create/update violated a unique constraint.

Prisma P1001Node.js

Error: P1001: Can't reach database server at `host`:`5432`

Prisma couldn’t connect to the database in DATABASE_URL.

Map another error

Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError