Error map
Vercel: Command "npm run build" exited with 1 Vercel: Error: Command "npm run build" exited with 1
Next.js · layer 1, On your device
Centre: this error. First ring: errors it is linked with (12). 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.
Directly related (12)
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.
Vue: [Vue warn]: Component is missing template or render function.
A component object has neither `template` nor `render`, or an SFC import resolved wrongly.
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.
Next.js: Failed to compile. ./src/app/page.tsx:15:9 Type error: Type 'string | undefined' is not assignable to type 'string'
TypeScript type checking failed during `next build`, which blocks the deployment.
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).
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.
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.
Vue: [Vue warn]: Component provided template option but runtime compilation is not supported in this build of Vue. Configure your bundler to alias "vue" to "vue/dist/vue.esm-bundler.js"
A component uses a string `template` but the runtime-only Vue build has no compiler.
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.
Vercel: 413 FUNCTION_PAYLOAD_TOO_LARGE — Request Entity Too Large (4.5 MB limit)
A request or response exceeded Vercel's 4.5 MB serverless function payload limit.
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.
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 (32)
TypeError: x is not a function
You called something as a function, but its value is not a function (it’s undefined, a string, an object…).
TypeError: x is not a constructor
new was used with something that isn’t a class/constructor — usually a wrong import.
ReferenceError: Cannot access 'x' before initialization
A let/const/class was used before its declaration line ran (temporal dead zone) — often a circular import.
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! 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.
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.
React Hook useEffect has a missing dependency (react-hooks/exhaustive-deps)
ESLint warns that the effect reads a value that isn’t in its dependency array, so it may use a stale value.
Error: @prisma/client did not initialize yet. Please run "prisma generate"
The generated Prisma Client is missing or out of date.
Error: Node Sass does not yet support your current environment
node-sass (deprecated) has no binary for your Node version/OS.
TypeError [ERR_UNKNOWN_FILE_EXTENSION]: Unknown file extension ".ts"
Node tried to run a TypeScript file as ESM without a TypeScript loader.
TS2307: Cannot find module 'x' or its corresponding type declarations.
TypeScript can’t resolve the import — the package isn’t installed, the path alias isn’t configured, or there are no types.
TS7016: Could not find a declaration file for module 'x'. 'x.js' implicitly has an 'any' type.
The JavaScript package has no TypeScript types bundled and no @types package installed.
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
The V8 heap hit its limit — a large build (webpack, tsc, Next.js) needs more memory, or the app leaks.
RangeError: Invalid string length
A string grew beyond the engine’s maximum length — usually runaway concatenation or huge JSON.stringify output.
MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 listeners added
More than 10 listeners were added to one event — often a leak where listeners are added repeatedly.
Error: Dynamic server usage: Route /x couldn't be rendered statically because it used `cookies`
Next.js tried to statically render a route that reads request-specific data (cookies, headers, searchParams).
Error occurred prerendering page "/x". Read more: https://nextjs.org/docs/messages/prerender-error
A page threw an error while Next.js was rendering it at build time.
'react-scripts' is not recognized as an internal or external command / react-scripts: command not found
node_modules is missing or broken, so the react-scripts binary isn’t available.
HTTP 504 Gateway Timeout
A proxy or gateway waited too long for the upstream server to respond and gave up.
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.
Module parse failed: Unexpected token. You may need an appropriate loader to handle this file type
Webpack found syntax it can’t parse because no loader is configured for that file (JSX, TypeScript, CSS, or modern syntax in node…
Vue: [Vue warn]: Failed to resolve component: x
The template uses a component tag that isn’t registered or imported where it’s used.
Next.js: useSearchParams() should be wrapped in a suspense boundary at page "/". Read more: https://nextjs.org/docs/messages/missing-suspense-with-csr-bailout
A Client Component using `useSearchParams` is statically rendered, so the build needs a Suspense boundary for the client-only par…
Next.js: TypeError: Failed to parse URL from /api/posts (fetch in a Server Component)
`fetch('/api/x')` with a relative URL works in browsers but not on the server, which has no base URL.
Next.js: Error: You cannot use different slug names for the same dynamic path ('id' !== 'slug')
Sibling dynamic folders at the same level use different parameter names.
Next.js: ⨯ Failed to download `Inter` from Google Fonts. Using fallback font instead / FetchError: request to https://fonts.googleapis.com failed
`next/font/google` couldn't download the font at build/dev time (offline, firewall or proxy).
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.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.
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.
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.
PrismaClientKnownRequestError P2002: Unique constraint failed on the fields: (`email`)
A Prisma create/update violated a unique constraint.
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