Error code search

An attempt was made to use a URL of an incompatible scheme (protocol) for a specific purpose. It is only used in the WHATWG URL API support in the fs module (which only accepts URLs with 'file' scheme), but may be used in other Node.js APIs as well in the future.

An attempt was made to use an IPC communication channel that was already closed.

An attempt was made to disconnect an IPC communication channel that was already disconnected. See the documentation for the child_process module for more information.

An attempt was made to create a child Node.js process using more than one IPC communication channel. See the documentation for the child_process module for more information.

An attempt was made to open an IPC communication channel with a synchronously forked Node.js process. See the documentation for the child_process module for more information.

IP is blocked by net.BlockList.

An ESM loader hook returned without calling next() and without explicitly signaling a short circuit.

An error occurred while loading a SQLite extension.

An attempt was made to load a resource, but the resource did not match the integrity defined by the policy manifest. See the documentation for policy manifests for more information.

An attempt was made to load a resource, but the resource was not listed as a dependency from the location that attempted to load it. See the documentation for policy manifests for more information.

An attempt was made to load a policy manifest, but the manifest had multiple entries for a resource which did not match each other. Update the manifest entries to match in order to resolve this error. See the documentation for policy manifests for more information.

A policy manifest resource had an invalid value for one of its fields. Update the manifest entry to match in order to resolve this error. See the documentation for policy manifests for more information.

A policy manifest resource had an invalid value for one of its dependency mappings. Update the manifest entry to match to resolve this error. See the documentation for policy manifests for more information.

An attempt was made to load a policy manifest, but the manifest was unable to be parsed. See the documentation for policy manifests for more information.

An attempt was made to read from a policy manifest, but the manifest initialization has not yet taken place. This is likely a bug in Node.js.

A policy manifest was loaded, but had an unknown value for its "onerror" behavior. See the documentation for policy manifests for more information.

An attempt was made to allocate memory (usually in the C++ layer) but it failed.

A message posted to a MessagePort could not be deserialized in the target vm Context. Not all Node.js objects can be successfully instantiated in any context at this time, and attempting to transfer them using postMessage() can fail on the receiving side in that case.

A method is required but not implemented.

A required argument of a Node.js API was not passed. This is only used for strict compliance with the API specification (which in some cases may accept func(undefined) but not func()). In most native Node.js APIs, func(undefined) and func() are treated identically, and the ERR_INVALID_ARG_TYPE error code may be used instead.

This error code was replaced by ERR_MISSING_TRANSFERABLE_IN_TRANSFER_LIST in Node.js 15.0.0, because it is no longer accurate as other types of transferable objects also exist now.

For APIs that accept options objects, some options might be mandatory. This code is thrown if a required option is missing.

An attempt was made to read an encrypted key without specifying a passphrase.

The V8 platform used by this instance of Node.js does not support creating Workers. This is caused by lack of embedder support for Workers. In particular, this error will not occur with standard builds of Node.js.

An object that needs to be explicitly listed in the transferList argument is in the object passed to a postMessage() call, but is not provided in the transferList for that call. Usually, this is a MessagePort. In Node.js versions prior to v15.0.0, the error code being used here was ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LIST. However, the set of transferable object types has been expanded to cover more types than MessagePort.

A module can not be linked because the same module requests in it are not resolved to the same module.

A module file could not be resolved by the ECMAScript modules loader while attempting an import operation or when loading the program entry point.

A callback was called more than once. A callback is almost always meant to only be called once as the query can either be fulfilled or rejected but not both at the same time. The latter would be possible by calling a callback more than once.

While using Node-API, a constructor passed was not a function.

Used by the Node-API when Constructor.prototype is not an object.

While calling napi_create_dataview(), a given offset was outside the bounds of the dataview or offset + length was larger than a length of given buffer.

While calling napi_create_typedarray(), the provided offset was not a multiple of the element size.

While calling napi_create_typedarray(), (length * size_of_element) + byte_offset was larger than the length of given buffer.

An error occurred while invoking the JavaScript portion of the thread-safe function.

An error occurred while attempting to retrieve the JavaScript undefined value.

On the main thread, values are removed from the queue associated with the thread-safe function in an idle loop. This error indicates that an error has occurred when attempting to start the loop.

Once no more items are left in the queue, the idle loop must be suspended. This error indicates that the idle loop has failed to stop.

A non-context-aware native addon was loaded in a process that disallows them.

An attempt was made to use operations that can only be used when building V8 startup snapshot even though Node.js isn't building one.

The operation cannot be performed when it's not in a single-executable application.