Error map
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 · 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)
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.
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: Node Sass does not yet support your current environment
node-sass (deprecated) has no binary for your Node version/OS.
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…
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.
Bitbucket Pipelines: Container 'Build' exceeded memory limit / Docker container exited with code 137
A Bitbucket Pipelines step used more memory than the step allows (4 GB by default, 1 GB for service containers) and was killed.
RangeError: Invalid string length
A string grew beyond the engine’s maximum length — usually runaway concatenation or huge JSON.stringify output.
Error: @prisma/client did not initialize yet. Please run "prisma generate"
The generated Prisma Client is missing or out of date.
GitHub Actions: Error: Process completed with exit code 137 (Killed — out of memory)
The command was killed by the system with SIGKILL (128 + 9), almost always because the runner ran out of memory.
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.
Two steps away (36)
Kubernetes: OOMKilled (exit code 137)
The container used more memory than its limit, and the kernel killed it.
java.lang.OutOfMemoryError: Java heap space
The JVM ran out of heap memory and garbage collection couldn’t free enough.
Blue Screen: MEMORY_MANAGEMENT (Stop code 0x0000001A)
Windows detected a severe memory-management error — commonly faulty RAM, unstable memory settings or a bad driver.
Error: listen EADDRINUSE: address already in use :::3000
Another process is already listening on that port.
Error: Could not find or load main class org.gradle.wrapper.GradleWrapperMain
The Gradle wrapper JAR (gradle/wrapper/gradle-wrapper.jar) is missing or corrupt.
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.
ModuleNotFoundError: No module named 'x'
Python can’t find the module you import — it isn’t installed in the interpreter/virtualenv that’s running, or the import path is…
gyp: No Xcode or CLT version detected!
node-gyp on macOS can’t find the Xcode Command Line Tools to compile native modules.
Error: Could not load the "sharp" module using the linux-x64 runtime
sharp’s native binary for this OS/CPU isn’t installed — usually node_modules installed on another platform (Mac → Linux/Docker).
Error: Cannot find module 'x' (MODULE_NOT_FOUND)
Node can’t resolve the module path — the package isn’t installed, or a relative path/extension is wrong.
COPY failed: file not found in build context / "/app/x": not found
The Dockerfile COPY refers to a path outside the build context, excluded by .dockerignore, or relative to the wrong directory.
Error [ERR_PACKAGE_PATH_NOT_EXPORTED]: Package subpath './x' is not defined by "exports"
You imported a deep path inside a package that its package.json "exports" field doesn’t expose.
ChunkLoadError: Loading chunk 123 failed.
A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.
Module not found: Can't resolve 'fs' (Next.js / webpack 5)
A Node.js built-in (fs, path, crypto, net) is imported into code that runs in the browser bundle.
Dockerfile parse error line N: unknown instruction
A line in the Dockerfile doesn’t start with a valid instruction — usually a broken line continuation or a typo.
Error: Hydration failed because the initial UI does not match what was rendered on the server
The HTML rendered on the server differs from the first client render, so React (Next.js/Remix) can’t attach to it.
You're importing a component that needs useState. It only works in a Client Component but none of its parents are marked with "use client"
In the Next.js App Router, a component using hooks or browser APIs is rendered as a Server Component.
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).
bash: command not found
The shell can’t find an executable with that name in any directory on your PATH.
npm ERR! could not determine executable to run
npx couldn’t find a binary to run for that package.
sh: vite: command not found (npm script)
A tool used in an npm script isn’t installed in node_modules/.bin.
GitLab CI: Cannot connect to the Docker daemon at tcp://docker:2375. Is the docker daemon running?
A docker-in-docker job could not reach the `docker:dind` service — it is not started, not privileged, or the TLS/host settings do…
Jenkins: Still waiting to schedule task — Waiting for next available executor / 'agent1' is offline
A Jenkins build is queued because no executor with the required label is free or the agent is offline.
CircleCI: Too long with no output (exceeded 10m0s): context deadline exceeded
A CircleCI step printed nothing for 10 minutes, so CircleCI assumed it hung and cancelled it.
Segmentation fault (core dumped)
A program accessed memory it wasn’t allowed to, and the kernel killed it with SIGSEGV (exit code 139).
Killed / Out of memory: Killed process (Linux OOM killer)
The kernel ran out of memory and killed a process to recover — the program just prints “Killed” (exit code 137).
java.lang.StringIndexOutOfBoundsException: begin 0, end 10, length 5
substring()/charAt() used an index outside the string.
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.
dial tcp: lookup registry-1.docker.io: no such host / Temporary failure in name resolution during docker build
DNS isn’t working for the Docker daemon or inside build containers, so pulls and package downloads fail.
GitHub Actions: Error: Process completed with exit code 1.
A `run:` command returned a non-zero status, so the step (and job) failed — the real cause is printed in the log lines above.
GitHub Actions: Error: Process completed with exit code 127 — command not found
The shell could not find the command you tried to run: it is not installed on the runner, not on PATH, or misspelled.
GitHub Actions: The runner has received a shutdown signal. This can happen when the runner service is stopped, or a manually started runner is canceled
The machine running your job was shut down or reclaimed while the job was running — a self-hosted runner stopped, a spot instance…
FATAL: the database system is in recovery mode
PostgreSQL crashed (often OOM-killed) and is replaying WAL to recover.
MemoryError (Unable to allocate X GiB for an array)
Python couldn’t allocate memory — the data is larger than available RAM or address space.
The kernel appears to have died. It will restart automatically.
The Jupyter kernel process crashed — usually out of memory or a native library crash.
Map another error
Popular: 500403400ORA-009331064Critical errorFileNotFoundException assemblyTypeError