All Errors

Your setImmediate() callback threw an unhandled exception or failed during execution. This error occurs because exceptions in setImmediate callbacks cannot be caught with try-catch and propagate unchecked through the Node.js event loop, crashing your process.

This error occurs when Node.js cannot verify the SSL/TLS certificate of a server you are trying to connect to. It typically happens with self-signed certificates, expired certificates, or missing intermediate certificates. The fix depends on whether you are in a development environment or production.

Node.js StringDecoder throws an error when you pass an unsupported or misspelled encoding. This happens when working with streams or buffers with invalid encoding specifications.

This error occurs when Node.js receives a malformed or unrecognized timezone string from the TZ environment variable. The TZ variable expects valid IANA timezone identifiers (like "America/New_York" or "Europe/London") or POSIX timezone strings, but receives an invalid or misspelled value instead. This causes date and time operations to fail or behave unpredictably.

A TLS handshake timeout occurs when the client and server fail to complete the SSL/TLS negotiation within the timeout period (default 120 seconds). This typically indicates network delays, server resource constraints, or infrastructure issues.

This error occurs when the hostname sent during TLS handshake (Server Name Indication) does not match the hostname on the SSL/TLS certificate. The server receives a different SNI name than what the certificate is valid for, causing verification to fail.

This error occurs when attempting to call cluster.fork() from a worker process instead of the primary (master) process. The cluster module enforces a strict master-worker hierarchy where only the primary process can spawn new workers.

This error occurs when Node.js receives an HTTP response with malformed chunked transfer encoding. The HTTP parser cannot properly decode the response body because the chunk format violates HTTP/1.1 specifications.

This error occurs when an exception is thrown inside a deferred callback (setTimeout, setImmediate, or process.nextTick) without proper error handling, potentially crashing the Node.js process.

The EAGAIN error indicates that a requested I/O operation cannot be completed immediately because the resource is temporarily unavailable. This is a recoverable error that signals Node.js to retry the operation later rather than failing permanently.

This error occurs when a TCP connection is forcibly closed by the remote server or peer before the operation completes. It typically happens during HTTP requests when the server closes the connection unexpectedly, often due to timeout mismatches, keep-alive issues, or network problems.

This error occurs when a file or directory name exceeds the maximum length allowed by the operating system's filesystem. Most filesystems limit individual filename components to 255 bytes, and Node.js throws ENAMETOOLONG when attempting filesystem operations with paths that exceed this limit.

Occurs when using require() or import with relative paths (./ or ../) to modules that don't exist or have incorrect paths.

PostgreSQL does not support nesting aggregate functions directly (such as AVG(MAX(column))). Use subqueries or Common Table Expressions (CTEs) to perform multi-level aggregations.

This error occurs when you pass an invalid depth value to Node.js util.inspect() function. The depth parameter must be a non-negative integer (0 or greater), null, or Infinity—passing a negative number triggers this RangeError.

This cryptographic error occurs when using Node.js v17+ with Vite, caused by OpenSSL 3.0 dropping support for legacy hash algorithms like MD4 that older build tools depend on.

Create React App build scripts fail on Node.js 17+ due to OpenSSL 3.0 changes that deprecated certain cryptographic algorithms used by Webpack 4. The build works fine on Node 16 but crashes with ERR_OSSL_EVP_UNSUPPORTED on newer versions.

The Next.js Image component requires the alt attribute to be a string for accessibility compliance. This error occurs when the alt prop is missing or explicitly set to undefined, preventing proper screen reader support and fallback text display.

This error occurs when using TypeScript project references but the referenced projects don't have 'composite: true' in their tsconfig.json. Project references require each referenced project to be marked as composite to enable fast incremental builds and proper type resolution.

This error occurs when a Promise is rejected without passing an error object or reason. Instead of a meaningful error message, Node.js displays "undefined", making debugging extremely difficult.