Node.js error codes

A Node.js API was called in an unsupported manner, such as Buffer.write(string, encoding, offset[, length]).

An attempt was made to use features that require Temporal, but Node.js was not compiled with Temporal support or it has been disabled in the current environment (for example, when running with --no-harmony-temporal).

An attempt was made to use features that require Native TypeScript support, but Node.js was not compiled with TypeScript support.

An operation failed. This is typically used to signal the general failure of an asynchronous operation.

An attempt was made to get options before the bootstrapping was completed.

Used generically to identify that an operation caused an out of memory condition.

A given value is out of the accepted range.

The package.json "imports" field does not define the given internal package specifier mapping.

A module attempted to resolve a bare specifier using the package map, but the importing file is not located within any package defined in the map. To fix this error, ensure the importing file is inside one of the package directories listed in the package map, or add a new package entry whose url covers the importing file.

The package map configuration file is invalid. This can occur when:

A package's dependencies object in the package map references a package key that is not defined in the packages object. In this example, "nonexistent" is referenced as a dependency target but not defined in packages, which will throw this error. To fix this error, ensure all package keys referenced in dependencies values are defined in the packages object.

The package.json "exports" field does not export the requested subpath. Because exports are encapsulated, private internal modules that are not exported cannot be imported through the package resolution, unless using an absolute URL.

When strict set to true, thrown by util.parseArgs() if a <boolean> value is provided for an option of type <string>, or if a <string> value is provided for an option of type <boolean>.

Thrown by util.parseArgs(), when a positional argument is provided and allowPositionals is set to false.

When strict set to true, thrown by util.parseArgs() if an argument is not configured in options.

The node:repl module was unable to parse data from the REPL history file.

An invalid timestamp value was provided for a performance mark or measure.

Invalid options were provided for a performance measure.

Accessing Object.prototype.__proto__ has been forbidden using --disable-proto=throw. Object.getPrototypeOf and Object.setPrototypeOf should be used to get and set the prototype of an object.

Failed to proxy a request because the proxy configuration is invalid.

Failed to establish proxy tunnel when NODE_USE_ENV_PROXY or --use-env-proxy is enabled.

A QUIC application error occurred.

Establishing a QUIC connection failed.

A QUIC Endpoint closed with an error.

Opening a QUIC stream failed.

The Node.js error code for a QuicError thrown to abort a QUIC stream or session with an explicit application or transport error code.

A QUIC stream was reset by the peer. The error includes the reset code provided by the peer.

A QUIC transport error occurred.

A QUIC session failed because version negotiation is required.

When trying to require() an ES Module, the module turns out to be asynchronous. That is, it contains top-level await. When uncaught, the flag --experimental-print-required-tla prints the locations of the top-level awaits in the graph to stderr. This error has the following additional non-enumerable properties:

When trying to require() an ES Module, a CommonJS to ESM or ESM to CommonJS edge participates in an immediate cycle. This is not allowed because ES Modules cannot be evaluated while they are already being evaluated. To avoid the cycle, the require() call involved in a cycle should not happen at the top-level of either an ES Module (via createRequire()) or a CommonJS module, and should be done lazily in an inner function.

An attempt was made to require() an ES Module. This error has been deprecated since require() now supports loading synchronous ES modules. When require() encounters an ES module that contains top-level await, it will throw ERR_REQUIRE_ASYNC_MODULE instead.

An attempt was made to require() an ES Module while another import() call was already in progress to load it asynchronously.

A feature requiring runtime allocation of executable memory was used in an environment where that capability is unavailable. This includes creating an otherwise eligible FFI Fast API function, or allocating an FFI callback when libffi cannot provide a closure and executable memory is unavailable. Node.js does not guarantee a non-generated-code fallback for these operations. This error can be caught without terminating the process.

Script execution was interrupted by SIGINT (For example, Ctrl+C was pressed.)

Script execution timed out, possibly due to bugs in the script being executed.

The server.listen() method was called while a net.Server was already listening. This applies to all instances of net.Server, including HTTP, HTTPS, and HTTP/2 Server instances.

The server.close() method was called when a net.Server was not running. This applies to all instances of net.Server, including HTTP, HTTPS, and HTTP/2 Server instances.

A key was passed to single executable application APIs to identify an asset, but no match could be found.

An attempt was made to bind a socket that has already been bound.