All Errors

This error occurs when node-gyp can't find the G++ C++ compiler. Native npm modules with C++ code require g++ for compilation, and this fails if it's not installed.

This error occurs when Git cannot sign a commit using GPG. Common causes include an expired GPG key, misconfigured TTY, or wrong GPG program. Fixing typically involves setting GPG_TTY, restarting gpg-agent, or reconfiguring your signing key.

The EBADPLATFORM error occurs when a package doesn't support your operating system or CPU architecture. This is common with native binaries that aren't built for all platforms.

This Git error occurs when you try to delete, checkout, or reference a branch that doesn't exist in your repository. The branch may have been deleted, renamed, misspelled, or never fetched from the remote. Fix it by verifying the branch name and ensuring you've fetched the latest remote references.

The EEXIST error occurs when npm tries to create a file or directory that already exists. This often indicates a corrupted state that can be resolved by clearing the affected files.

This warning occurs when prebuild-install can't find prebuilt binaries for your platform/Node.js combination. It falls back to compiling from source, which requires build tools.

The ELIFECYCLE exit code 1 error indicates a npm script failed with an error. The actual error is typically shown before this message and relates to your script's code, not npm itself.

This error occurs when Git cannot add a file to its staging index. Common causes include file locks from other applications, permission issues, antivirus interference, or a corrupted index file. The fix usually involves closing programs that lock the file or resetting the Git index.

This error occurs when create-react-app or similar npm init commands fail during execution. Often caused by Node.js version issues, corrupted cache, or the fact that Create React App is now deprecated.

Exit code 137 indicates the process was killed by signal 9 (SIGKILL), usually by the OOM killer due to memory exhaustion. Increase available memory or optimize your build process.

This error occurs when using an outdated Git version (typically 1.8.x on CentOS 7) that doesn't properly support shallow clone operations. The fix is to upgrade Git to version 2.x or disable shallow cloning in your CI/CD configuration.

The 'Path does not exist in HEAD' error occurs when Git cannot find a specified file in the current commit. This happens with new untracked files, incorrect paths, or case sensitivity mismatches.

The ESHRINKWRAP error indicates that your npm-shrinkwrap.json file and package.json are out of sync, usually because package.json was modified without updating the shrinkwrap file.

CrashLoopBackOff indicates a container is repeatedly crashing and restarting. Kubernetes applies exponential backoff delays between restarts while you diagnose the underlying application or configuration issue.

The git describe command fails when used with --match or --exact-match options and no tags match the specified pattern or commit. This occurs when trying to find a specific tag that describes the current commit.

This Git error occurs when Git cannot determine whether an argument is a branch name, commit reference, or file path. The specified reference doesn't exist locally, often because it was never fetched, was deleted, is misspelled, or the repository is a shallow clone. Fix it by verifying the branch exists and fetching from the remote.

ErrImagePull is the initial failure when Kubernetes cannot pull a container image. It immediately precedes ImagePullBackOff and indicates authentication, network, or image reference problems.

This Git error occurs when HEAD cannot reference a valid commit, typically in a newly initialized repository with no commits, or when the HEAD reference has become corrupted. The fix usually involves making an initial commit or resetting HEAD to a valid branch.

This PowerShell error occurs when Windows' execution policy is set to Restricted, preventing npm scripts from running. The fix involves changing the execution policy to RemoteSigned using Set-ExecutionPolicy.

OOMKilled (exit code 137) means the Linux kernel terminated your container for exceeding its memory limit. Increase memory limits or optimize your application memory usage.