All Errors

This error occurs when the crypto.createHmac() method receives a key argument that is not a valid type. Node.js requires the HMAC key to be a string, Buffer, TypedArray, DataView, or KeyObject, and passing undefined, null, or other invalid types will cause this error.

This system-level error occurs when attempting to initiate a network operation (like a socket connection) that is already in progress. It commonly happens when reconnecting sockets too quickly or trying to bind resources that are already being accessed.

This error occurs when Node.js attempts to establish a TCP connection but the operating system cannot find a network route to the destination. The connection fails because no routing path exists between your system and the target host.

This error occurs when you attempt to call a value as a function, but that value is not actually a function. It commonly happens due to typos in function names, calling properties that hold non-function values, or issues with module loading and scope.

This Node.js error occurs when the operating system blocks a file system operation due to insufficient permissions, file locking by another process, or security restrictions. Common scenarios include writing to protected directories, accessing files opened by other applications, or operating on files locked by antivirus software.

This error occurs when Node.js file system operations attempt to read, write, or manipulate a directory as if it were a regular file. The operation expects a file path but receives a directory path instead.

This error occurs when React tries to access the "props" property on a null or undefined object, typically due to uninitialized state, missing null checks, or accessing components after they've unmounted.

This error occurs when using latin1 (ISO-8859-1) encoding in Node.js Buffer operations on versions that don't support it. The fix is to either upgrade Node.js to v6.4.0 or later, or use an alternative encoding method.

Node.js throws ERR_UNKNOWN_FILE_EXTENSION when trying to import or execute files with unrecognized extensions. This commonly occurs with TypeScript files (.ts), Python files (.py), or other non-JavaScript file types that Node.js cannot natively process.

This fatal error occurs when a Node.js process attempts to allocate more memory than the available heap size allows. The process crashes because it cannot continue execution without the requested memory allocation.

The ENODEV error occurs when Node.js attempts to read from a device that doesn't exist or is unavailable. This commonly happens with hardware devices like Bluetooth adapters, TTY devices, or when performing device-specific operations on unsupported file descriptors.

This error occurs when Node.js attempts to write data to a stream, pipe, or socket that has already been closed by the receiving end. It's a POSIX error indicating the connection was terminated before all data could be transmitted.

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.