All Errors

This error occurs when a Node.js TLS client refuses to connect because the server offers Diffie-Hellman key exchange parameters smaller than the minimum security threshold (typically 1024 bits). Modern OpenSSL versions reject weak DH groups to protect against cryptographic attacks like Logjam.

This error occurs when Node.js's zlib module fails to decompress data due to corrupted input, incorrect compression format, or header mismatches. The decompression algorithm encounters data that doesn't conform to the expected zlib/gzip format.

This error occurs when a Node.js writable stream fails to emit the drain event after write() returns false, indicating a backpressure handling failure. The stream's internal buffer is full but never signals when it's safe to resume writing, leading to frozen writes, memory buildup, or application hangs. Proper backpressure handling requires correctly listening for and responding to the drain event.

This error appears when attempting to combine --build and --watch flags incorrectly with the TypeScript compiler. In TypeScript 3.0+, these flags should be used as 'tsc -b --watch' (or 'tsc --build --watch') for project references, not as separate conflicting options.

The "Not implemented" error occurs when attempting to use a feature, method, or API that has not been implemented in the current environment, library, or Node.js version. This can happen with custom stream implementations, platform-specific functions, or browser APIs in testing environments.

This error occurs when you attempt to use an unsupported or misspelled algorithm name with Node.js crypto module functions like createHash() or createHmac(). The algorithm name must match one of the hash algorithms available in your Node.js/OpenSSL installation.

This TypeScript error occurs when the compiler cannot locate the Next.js module or its type definitions. It typically happens due to missing installations, incorrect TypeScript configuration, or conflicts between Next.js versions and moduleResolution settings.

This error occurs when Node.js attempts to write to a file or directory that resides on a read-only filesystem. It commonly happens in Docker containers with read-only root filesystems, mounted volumes with incorrect permissions, or filesystems explicitly mounted as read-only for security reasons.

This error occurs when a Node.js application attempts to connect to a TCP port but the connection is actively refused because no service is listening on that port. It commonly happens with database connections, API calls to localhost, or inter-service communication when the target server is not running or the port configuration is incorrect.

An uncaught exception occurs when a JavaScript error is thrown but not caught by any try-catch block or error handler, causing the application to crash. This indicates the application is in an undefined state and must be properly handled to prevent data corruption.

EHOSTDOWN is a socket connection error indicating the remote host is down or unreachable at the network layer. This error occurs when Node.js receives status information from the underlying communication services that the target host is down.

This error occurs when attempting to use CommonJS require() syntax in code being treated as an ES module. Node.js uses different module systems, and require() is not available in ES module scope.

This error occurs when you specify a character encoding that Node.js does not natively support, such as "utf-16" or a misspelled encoding name. Node.js supports specific encodings like utf8, utf16le, ascii, and base64.

This error occurs when Node.js fails to complete a TLS handshake during an HTTPS or secure WebSocket connection. The client and server cannot agree on compatible encryption protocols, cipher suites, or certificate parameters, causing the secure connection to be rejected.

This error occurs when attempting to chain .then() on a value that is undefined instead of a Promise. It typically happens when a function fails to return a Promise, breaking the promise chain.

This error occurs when both sides of a Node.js duplex stream (readable and writable) fail or close prematurely before completing data transfer. It commonly happens due to improper error handling, missing event listeners, or abrupt connection terminations in network streams, transform streams, or bidirectional pipes.

The ENETUNREACH error occurs when Node.js cannot establish a network connection because the destination network is unreachable. This typically indicates routing problems, network interface issues, or firewall restrictions preventing your application from reaching the target host.

The EHOSTUNREACH error occurs when Node.js attempts to establish a TCP connection but cannot find any network route to reach the target host. This typically indicates network configuration issues, firewall blocks, or an unreachable server.

This error occurs when the operating system runs out of buffer space for network operations, typically during heavy socket operations or large data transfers. It indicates system-level resource exhaustion rather than a code-level bug.

This error occurs when you try to return an array of JSX elements from a React component without wrapping them in a Fragment or proper array syntax. React components can return arrays of elements, but they must be properly formatted with key props and array literal syntax.