Error map
Output directory not found Cloudflare Pages build: Error: Output directory "dist" not found / Failed: build output directory not found
Cloudflare · layer 3, Edge & web server
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)
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…
failed to solve: process "/bin/sh -c ..." did not complete successfully: exit code: 1
A RUN step in your Dockerfile failed. The real error is printed in the lines just above this message.
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.
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.
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: subprocess-exited-with-error / Failed building wheel for x
pip had to compile a package from source and the build failed — missing compiler, headers or system libraries.
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.
Elastic Beanstalk: Environment health has transitioned from Ok to Severe
Most instances in the Elastic Beanstalk environment are failing health checks or returning errors.
ARM/Bicep: DeploymentFailed / InvalidTemplateDeployment / InvalidTemplate
An Azure Resource Manager (ARM/Bicep/Terraform) deployment failed; the inner error under “details” has the real cause.
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.
npm ERR! enoent ENOENT: no such file or directory, open '/path/package.json'
npm ran in a directory without a package.json.
error NETSDK1045: The current .NET SDK does not support targeting .NET 8.0. Either target .NET 7.0 or lower, or use a version of the .NET SDK that supports .NET 8.0
The installed .NET SDK is older than the project’s TargetFramework.
Two steps away (36)
ChunkLoadError: Loading chunk 123 failed.
A lazily loaded JavaScript chunk couldn’t be downloaded — usually because a new deployment removed the old hashed files.
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.
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.
failed to solve: failed to read dockerfile: open Dockerfile: no such file or directory
docker build can’t find a Dockerfile in the build context you passed.
Error response from daemon: max depth exceeded (too many image layers)
The image has more layers than the storage driver allows (127 for overlay2), usually from repeatedly committing containers or ver…
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.
PHP Parse error: syntax error, unexpected …
PHP can’t parse the file because of a syntax mistake — the real error is often on the line before the one reported.
IndentationError: unexpected indent / expected an indented block
Python’s block structure is broken — inconsistent indentation or mixed tabs and spaces.
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…
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…
Error: Node Sass does not yet support your current environment
node-sass (deprecated) has no binary for your Node version/OS.
gyp: No Xcode or CLT version detected!
node-gyp on macOS can’t find the Xcode Command Line Tools to compile native modules.
fatal: not a git repository (or any of the parent directories): .git
You ran a Git command outside a Git working tree.
Error: ENOENT: no such file or directory
A file or directory the program tried to open doesn’t exist at that path.
exec /usr/local/bin/docker-entrypoint.sh: exec format error
The container tried to run a binary built for a different CPU architecture (arm64 vs amd64) — or a script with a broken shebang /…
error: externally-managed-environment
Your system Python (Debian 12+, Ubuntu 23.04+, Homebrew) refuses pip installs into the OS-managed environment (PEP 668).
ERROR: Could not find a version that satisfies the requirement x (from versions: none)
pip found no installable version of the package for your Python version, OS or index.
Docker build slow: "Sending build context to Docker daemon 2.5GB" / transferring context takes forever
docker build is uploading your whole project folder — node_modules, .git, data files — before building, because there’s no (or a…
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).
HTTP 502 Bad Gateway
A proxy or gateway (Nginx, load balancer, CDN) got an invalid response — or no response — from the upstream server behind it.
HTTP 503 Service Unavailable
The server is temporarily unable to handle the request — overloaded, in maintenance, or has no healthy backends.
Stack is in ROLLBACK_COMPLETE state and can not be updated
The stack’s first creation failed and rolled back; a stack in ROLLBACK_COMPLETE can only be deleted, not updated.
Azure: SkuNotAvailable / QuotaExceeded when creating a VM or resource
The VM size isn’t offered in that region/zone for your subscription, or you’ve hit the vCPU quota.
CloudFormation stack in UPDATE_ROLLBACK_FAILED
An update failed, and then the rollback also failed, leaving the stack stuck until you continue the rollback.
Multi-Attach error for volume: Volume is already exclusively attached to one node and can't be attached to another
A ReadWriteOnce volume (EBS, Azure Disk, PD) is still attached to another node, so the new pod on a different node can’t use it.
Gradle: Could not resolve all files for configuration / Could not resolve dependency
Gradle couldn’t download a dependency — wrong coordinates/version, missing repository, offline mode, or network/proxy issues.
java.lang.ClassNotFoundException / NoClassDefFoundError
The JVM couldn’t find a class on the classpath at runtime.
Manifest merger failed: android:exported needs to be explicitly specified
Targeting Android 12 (API 31)+ requires `android:exported` on every activity, service or receiver that has an intent-filter.
error: pathspec 'x' did not match any file(s) known to git
Git couldn’t find the file or branch name you referenced.
Author identity unknown *** Please tell me who you are.
Git doesn’t know your name and email for commits.
error: unable to create file x: Filename too long (Windows)
Windows’ 260-character path limit blocked Git from creating a file.
Could not load file or assembly 'X, Version=…' or one of its dependencies
The runtime couldn’t find or load a referenced DLL — missing from the output, wrong version, or wrong platform (x86/x64).
Error: @prisma/client did not initialize yet. Please run "prisma generate"
The generated Prisma Client is missing or out of date.
Laravel: Vite manifest not found at: public/build/manifest.json
Laravel’s @vite directive can’t find the compiled asset manifest because assets weren’t built.
Map another error
Popular: 4035004000xC000007BTypeErrorCritical error404NullPointerException