All Errors

This error occurs when attempting to register multiple PerformanceObserver instances for the same entry type in Node.js. Only one observer can monitor a specific entry type at a time, and duplicate registrations trigger an assertion failure that can crash the process.

Node.js shows a deprecation warning when code uses the built-in punycode module. This module has been deprecated since Node.js v7 and became a runtime deprecation in v21, warning that it will be removed in a future major version.

This error occurs in Node.js cluster mode when a worker process fails to exit within the expected timeout period after disconnect() is called. It typically indicates that the worker has open connections or pending operations preventing graceful shutdown.

This error occurs when a Transform stream's _flush() method encounters an error during stream finalization. The flush method is called after all data has been processed but before the stream ends, and errors here indicate failed cleanup operations or final transformations.

This error occurs when the Content-Length header value does not match the actual size of the response body received. It typically happens when the server sends an incorrect header, a proxy modifies the response without updating headers, or compression is applied inconsistently.

This error occurs when a web application tries to make a cross-origin HTTP request, but the server does not allow requests from the requesting origin. Browsers enforce CORS (Cross-Origin Resource Sharing) to protect users from potentially malicious cross-origin requests.

This SSH warning appears when the host key for a remote server doesn't match the stored fingerprint in your known_hosts file, which can indicate DNS spoofing, server changes, or IP address reuse. Usually this is benign but requires verification.

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.