All Errors

This error occurs when Node.js receives HTTP response headers that contain invalid characters or do not comply with strict HTTP/1.1 standards. Node.js v12+ uses a stricter HTTP parser that rejects malformed headers that browsers might accept.

This error occurs when attempting to allocate a buffer that exceeds Node.js maximum buffer size limits. On 32-bit systems the limit is ~1GB, while 64-bit systems allow up to ~2GB.

This error occurs when you attempt to set an HTTP header with a value containing characters that violate HTTP header specifications. Node.js strictly validates header values to prevent header injection attacks and protocol violations.

This error occurs when the Inter-Process Communication (IPC) channel between a parent and child process created with child_process.fork() fails or closes unexpectedly, preventing message passing between processes.

This error occurs when Node.js runs out of memory while executing your application. By default, Node.js limits heap memory to approximately 1.5GB on 64-bit systems, which may be insufficient for memory-intensive operations like processing large files or building complex applications.

This error occurs when you call server.listen() more than once on the same server instance. Once a server is listening on a port, you cannot call listen() again without closing it first, as the port binding is already established.

This error occurs when Node.js detects conflicting or invalid HTTP trailer headers in a chunked transfer encoding response. Trailers can only be used with chunked encoding, but certain conditions prevent their proper use or declaration.

This error occurs when your Node.js application attempts to write data to a network socket that has already been destroyed or closed. The socket is no longer available for communication and cannot accept new data.

This error occurs when Node.js fails to compile native C/C++ addons during package installation. It indicates a problem with the compilation environment, missing build tools, or incompatible dependencies required by node-gyp.

This error occurs when your npm authentication token has expired and can no longer authenticate requests to private registries. As of 2025, npm has strengthened security by enforcing token expiration limits.

This error occurs when attempting to use HTTP trailer headers incorrectly with chunked transfer encoding. Trailer headers can only be sent after the message body when chunked encoding is properly enabled and the Trailer header is declared upfront.

This error occurs when Node.js detects corrupted or invalid V8 code cache data. The V8 engine uses code caching to speed up script compilation, but when the cached data becomes corrupted or incompatible, validation fails and Node.js must recompile the affected modules.

This error occurs when a Node.js worker thread exits unexpectedly due to an unhandled exception, memory limit, or forced termination. The main thread loses communication with the worker, leaving operations incomplete.

Occurs when attempting to use CommonJS require() to import an ES module, which only supports import statements.

Occurs when Node.js cannot resolve a module path from the project root, typically due to incorrect package.json configuration, missing dependencies, or path resolution issues.

Occurs when Node.js attempts to perform I/O operations on a file descriptor that is closed, invalid, or doesn't exist.

Occurs when Node.js cannot find an npm package that should be installed in node_modules, typically due to missing installation or corrupted node_modules.

Occurs when Node.js cannot establish a TCP connection to MySQL server because the server is not running, not listening on the specified port, or blocked by firewall.

Occurs when Node.js application attempts to open more MySQL connections than allowed by the max_connections server setting.

This error occurs when attempting to write data to a writable stream after it has been closed with end() or destroy(). Once a stream is ended, it cannot accept any additional data.