Errors
Node.js errors
ERR_* codes, module resolution and runtime errors.
462 entries1 written pages
Showing 401 to 450 of 462Source: Node.js documentation
| Code | Error | Category | Page |
|---|---|---|---|
| ERR_UNSUPPORTED_RESOLVE_REQUEST | An attempt was made to resolve an invalid module referrer. | Node.js error codes | Reference |
| ERR_UNSUPPORTED_TYPESCRIPT_SYNTAX | The provided TypeScript syntax is unsupported. This could happen when using TypeScript syntax that requires transformation with type-stripping. | Node.js error codes | Reference |
| ERR_USE_AFTER_CLOSE | An attempt was made to use something that was already closed. | Node.js error codes | Reference |
| ERR_V8BREAKITERATOR | The V8 BreakIterator API was used but the full ICU data set is not installed. | Legacy Node.js error codes | Reference |
| ERR_VALID_PERFORMANCE_ENTRY_TYPE | While using the Performance Timing API (perf_hooks), no valid performance entry types are found. | Node.js error codes | Reference |
| ERR_VALUE_OUT_OF_RANGE | Used when a given value is out of the accepted range. | Legacy Node.js error codes | Reference |
| ERR_VFS_INVALID_TARGET | A --vfs-mount source does not exist, is neither a regular file nor a directory, or is a source no provider claims. | Node.js error codes | Reference |
| ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING | A dynamic import callback was not specified. | Node.js error codes | Reference |
| ERR_VM_DYNAMIC_IMPORT_CALLBACK_MISSING_FLAG | A dynamic import callback was invoked without --experimental-vm-modules. | Node.js error codes | Reference |
| ERR_VM_MODULE_ALREADY_LINKED | The module attempted to be linked is not eligible for linking, because of one of the following reasons: It has already been linked (linkingStatus is 'linked') It is being linked (linkingStatus is 'linking') Linking has failed for this module (linkingStatus is 'errored') | Node.js error codes | Reference |
| ERR_VM_MODULE_CACHED_DATA_REJECTED | The cachedData option passed to a module constructor is invalid. | Node.js error codes | Reference |
| ERR_VM_MODULE_CANNOT_CREATE_CACHED_DATA | Cached data cannot be created for modules which have already been evaluated. | Node.js error codes | Reference |
| ERR_VM_MODULE_DIFFERENT_CONTEXT | The module being returned from the linker function is from a different context than the parent module. Linked modules must share the same context. | Node.js error codes | Reference |
| ERR_VM_MODULE_LINKING_ERRORED | The linker function returned a module for which linking has failed. | Legacy Node.js error codes | Reference |
| ERR_VM_MODULE_LINK_FAILURE | The module was unable to be linked due to a failure. | Node.js error codes | Reference |
| ERR_VM_MODULE_NOT_LINKED | The module must be successfully linked before instantiation. | Legacy Node.js error codes | Reference |
| ERR_VM_MODULE_NOT_MODULE | The fulfilled value of a linking promise is not a vm.Module object. | Node.js error codes | Reference |
| ERR_VM_MODULE_STATUS | The current module's status does not allow for this operation. The specific meaning of the error depends on the specific function. | Node.js error codes | Reference |
| ERR_WASI_ALREADY_STARTED | The WASI instance has already started. | Node.js error codes | Reference |
| ERR_WASI_NOT_STARTED | The WASI instance has not been started. | Node.js error codes | Reference |
| ERR_WEBASSEMBLY_NOT_SUPPORTED | A feature requiring WebAssembly was used, but WebAssembly is not supported or has been disabled in the current environment (for example, when running with --jitless). | Node.js error codes | Reference |
| ERR_WEBASSEMBLY_RESPONSE | The Response that has been passed to WebAssembly.compileStreaming or to WebAssembly.instantiateStreaming is not a valid WebAssembly response. | Node.js error codes | Reference |
| ERR_WORKER_HANDLE_NOT_TRANSFERABLE | An attempt was made to transfer a net.Socket, net.Server or net.BoundSocket to another thread via a worker_threads postMessage() call while it was not in a transferable state, for example because it had already started reading, had buffered data, or had already been adopted. | Node.js error codes | Reference |
| ERR_WORKER_INIT_FAILED | The Worker initialization failed. | Node.js error codes | Reference |
| ERR_WORKER_INVALID_EXEC_ARGV | The execArgv option passed to the Worker constructor contains invalid flags. | Node.js error codes | Reference |
| ERR_WORKER_MESSAGING_ERRORED | The destination thread threw an error while processing a message sent via postMessageToThread(). | Node.js error codes | Reference |
| ERR_WORKER_MESSAGING_FAILED | The thread requested in postMessageToThread() is invalid or has no workerMessage listener. | Node.js error codes | Reference |
| ERR_WORKER_MESSAGING_SAME_THREAD | The thread id requested in postMessageToThread() is the current thread id. | Node.js error codes | Reference |
| ERR_WORKER_MESSAGING_TIMEOUT | Sending a message via postMessageToThread() timed out. | Node.js error codes | Reference |
| ERR_WORKER_NOT_RUNNING | An operation failed because the Worker instance is not currently running. | Node.js error codes | Reference |
| ERR_WORKER_OUT_OF_MEMORY | The Worker instance terminated because it reached its memory limit. | Node.js error codes | Reference |
| ERR_WORKER_PATH | The path for the main script of a worker is neither an absolute path nor a relative path starting with ./ or ../. | Node.js error codes | Reference |
| ERR_WORKER_UNSERIALIZABLE_ERROR | All attempts at serializing an uncaught exception from a worker thread failed. | Node.js error codes | Reference |
| ERR_WORKER_UNSUPPORTED_EXTENSION | The pathname used for the main script of a worker has an unknown file extension. | Legacy Node.js error codes | Reference |
| ERR_WORKER_UNSUPPORTED_OPERATION | The requested functionality is not supported in worker threads. | Node.js error codes | Reference |
| ERR_ZIP_ARCHIVE_TOO_LARGE | An archive-level structure exceeds a limit: the archive comment exceeds the 65,535-byte encoded length that the ZIP format allows, or the archive's central directory is too large to buffer in memory. | Node.js error codes | Reference |
| ERR_ZIP_ENTRY_CORRUPT | A ZIP archive entry failed CRC-32 verification, or produced more or fewer bytes than its declared uncompressed size, while being read. | Node.js error codes | Reference |
| ERR_ZIP_ENTRY_NOT_FOUND | A named entry was requested from a ZipFile or ZipBuffer that does not contain an entry with that name. | Node.js error codes | Reference |
| ERR_ZIP_ENTRY_TOO_LARGE | A ZIP archive entry's declared size exceeds the configured limit, or a provided entry name or comment exceeds the 65,535-byte encoded length that the ZIP format allows. | Node.js error codes | Reference |
| ERR_ZIP_INVALID_ARCHIVE | Data that was expected to be a ZIP archive, or a structure within one, is missing, out of bounds, or otherwise inconsistent with the ZIP format. | Node.js error codes | Reference |
| ERR_ZIP_NOT_WRITABLE | A mutating method (such as zipFile.addEntry() or zipFile.delete()) was called on a ZipFile that was not opened with { writable: true }. | Node.js error codes | Reference |
| ERR_ZIP_UNSUPPORTED_FEATURE | A ZIP archive uses a feature outside of what this implementation supports, such as entry encryption, an unsupported compression method, or a multi-disk archive. | Node.js error codes | Reference |
| ERR_ZLIB_BINDING_CLOSED | Used when an attempt is made to use a zlib object after it has already been closed. | Legacy Node.js error codes | Reference |
| ERR_ZLIB_INITIALIZATION_FAILED | Creation of a zlib object failed due to incorrect configuration. | Node.js error codes | Reference |
| ERR_ZSTD_INVALID_PARAM | An invalid parameter key was passed during construction of a Zstd stream. | Node.js error codes | Reference |
| HOSTNAME_MISMATCH | Certificate does not match provided name. | OpenSSL error codes | Reference |
| HPE_CHUNK_EXTENSIONS_OVERFLOW | Too much data was received for a chunk extensions. In order to protect against malicious or malconfigured clients, if more than 16 KiB of data is received then an Error with this code will be emitted. | Node.js error codes | Reference |
| HPE_HEADER_OVERFLOW | Too much HTTP header data was received. In order to protect against malicious or malconfigured clients, if more than maxHeaderSize of HTTP header data is received then HTTP parsing will abort without a request or response object being created, and an Error with this code will be emitted. | Node.js error codes | Reference |
| HPE_UNEXPECTED_CONTENT_LENGTH | Server is sending both a Content-Length header and Transfer-Encoding: chunked. Transfer-Encoding: chunked allows the server to maintain an HTTP persistent connection for dynamically generated content. | Node.js error codes | Reference |
| INVALID_CA | A CA certificate is invalid. Either it is not a CA or its extensions are not consistent with the supplied purpose. | OpenSSL error codes | Reference |
Other families: JavaScript, npm, React, Next.js, TypeScript, Vite, webpack, Jest