Error code search

Not currently implemented.

The MS-Logoff digest header has been returned from the website. This header specifically instructs the digest package to purge credentials for the associated realm. This error will only be returned if INTERNET_ERROR_MASK_LOGIN_FAILURE_DISPLAY_ENTITY_BODY option has been set; otherwise, ERROR_INTERNET_LOGIN_FAILURE is returned.

WinINet failed to perform content decoding on the response. For more information, see the Content Encoding topic.

Used when an operation has been aborted (typically using an AbortController). APIs not using AbortSignals typically do not raise an error with this code. This code does not use the regular ERR_* convention Node.js errors use in order to be compatible with the web platform's AbortError.

EACCES (Permission denied): An attempt was made to access a file in a way forbidden by its file access permissions.

EADDRINUSE (Address already in use): An attempt to bind a server (net, http, or https) to a local address failed due to another server on the local system already occupying that address.

ECONNREFUSED (Connection refused): No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host.

ECONNRESET (Connection reset by peer): A connection was forcibly closed by a peer. This normally results from a loss of the connection on the remote socket due to a timeout or reboot. Commonly encountered via the http and net modules.

EEXIST (File exists): An existing file was the target of an operation that required that the target not exist.

EISDIR (Is a directory): An operation expected a file, but the given pathname was a directory.

EMFILE (Too many open files in system): Maximum number of file descriptors allowable on the system has been reached, and requests for another descriptor cannot be fulfilled until at least one has been closed. This is encountered when opening many files at once in parallel, especially on systems (in particular, macOS) where there is a low file descriptor limit for processes. To remedy a low limit, run ulimit -n 2048 in the same shell that will run the Node.js process.

ENOENT (No such file or directory): Commonly raised by fs operations to indicate that a component of the specified pathname does not exist. No entity (file or directory) could be found by the given path.

ENOTDIR (Not a directory): A component of the given pathname existed, but was not a directory as expected. Commonly raised by fs.readdir.

ENOTEMPTY (Directory not empty): A directory with entries was the target of an operation that requires an empty directory, usually fs.unlink.

ENOTFOUND (DNS lookup failed): Indicates a DNS failure of either EAI_NODATA or EAI_NONAME. This is not a standard POSIX error.

EPERM (Operation not permitted): An attempt was made to perform an operation that requires elevated privileges.

EPIPE (Broken pipe): A write on a pipe, socket, or FIFO for which there is no process to read the data. Commonly encountered at the net and http layers, indicative that the remote side of the stream being written to has been closed.

A special type of error that is triggered whenever Node.js tries to get access to a resource restricted by the Permission Model.

A function argument is being used in a way that suggests that the function signature may be misunderstood. This is thrown by the node:assert module when the message parameter in assert.throws(block, message) matches the error message thrown by block because that usage suggests that the user believes message is the expected message rather than the message the AssertionError will display if block does not throw.

An iterable argument (i.e. a value that works with for...of loops) was required, but not provided to a Node.js API.

A special type of error that can be triggered whenever Node.js detects an exceptional logic violation that should never occur. These are raised typically by the node:assert module.

An attempt was made to register something that is not a function as an AsyncHooks callback.

An operation related to module loading is customized by an asynchronous loader hook that never settled the promise before the loader thread exits.

The type of an asynchronous resource was invalid. Users are also able to define their own types if using the public embedder API.

Data passed to a Brotli stream was not successfully compressed.

An invalid parameter key was passed during construction of a Brotli stream.

An attempt was made to create a Node.js Buffer instance from addon or embedder code, while in a JS engine Context that is not associated with a Node.js instance. The data passed to the Buffer method will have been released by the time the method returns. When encountering this error, a possible alternative to creating a Buffer instance is to create a normal Uint8Array, which only differs in the prototype of the resulting object. Uint8Arrays are generally accepted in all Node.js core APIs where Buffers are; they are available in all Contexts.

An operation outside the bounds of a Buffer was attempted.

An attempt has been made to create a Buffer larger than the maximum allowed size.

The value passed to postMessage() contained an object that is not supported for transferring.

Node.js was unable to watch for the SIGINT signal.

A child process was closed before the parent received a reply.

Used when a child process is being forked without specifying an IPC channel.

Used when the main process is trying to read data from the child process's STDERR/STDOUT, and the data's length is longer than the maxBuffer option.

There was an attempt to use a MessagePort instance in a closed state, usually after .close() has been called.

Console was instantiated without stdout stream, or Console has a non-writable stdout or stderr stream.

A class constructor was called that is not callable.

A constructor for a class was called without new.

The vm context passed into the API is not yet initialized. This could happen when an error occurs (and is caught) during the creation of the context, for example, when the allocation fails or the maximum call stack size is reached when the context is created.

The CPU profile with the given name is already started.