Node.js error codes

The provided TypeScript syntax is unsupported. This could happen when using TypeScript syntax that requires transformation with type-stripping.

An attempt was made to use something that was already closed.

The V8 BreakIterator API was used but the full ICU data set is not installed.

While using the Performance Timing API (perf_hooks), no valid performance entry types are found.

Used when a given value is out of the accepted range.

A --vfs-load source does not exist, is neither a regular file nor a directory, or is a source no provider claims.

A dynamic import callback was not specified.

A dynamic import callback was invoked without --experimental-vm-modules.

The module attempted to be linked is not eligible for linking, because of one of the following reasons:

The cachedData option passed to a module constructor is invalid.

Cached data cannot be created for modules which have already been evaluated.

The module being returned from the linker function is from a different context than the parent module. Linked modules must share the same context.

The linker function returned a module for which linking has failed.

The module was unable to be linked due to a failure.

The module must be successfully linked before instantiation.

The fulfilled value of a linking promise is not a vm.Module object.

The current module's status does not allow for this operation. The specific meaning of the error depends on the specific function.

The WASI instance has already started.

The WASI instance has not been started.

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). TypeScript parsing and WebAssembly module imports, including source phase imports, report this error when WebAssembly is unavailable. Node.js does not provide an alternative implementation for these operations. This error can be caught without terminating the process.

The Response that has been passed to WebAssembly.compileStreaming or to WebAssembly.instantiateStreaming is not a valid WebAssembly response.

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.

The Worker initialization failed.

The execArgv option passed to the Worker constructor contains invalid flags.

The destination thread threw an error while processing a message sent via postMessageToThread().

The thread requested in postMessageToThread() is invalid or has no workerMessage listener.

The thread id requested in postMessageToThread() is the current thread id.

Sending a message via postMessageToThread() timed out.

An operation failed because the Worker instance is not currently running.

The Worker instance terminated because it reached its memory limit.

The path for the main script of a worker is neither an absolute path nor a relative path starting with ./ or ../.

All attempts at serializing an uncaught exception from a worker thread failed.

The pathname used for the main script of a worker has an unknown file extension.

The requested functionality is not supported in worker threads.

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.

A ZIP archive entry failed CRC-32 verification, or produced more or fewer bytes than its declared uncompressed size, while being read.

A named entry was requested from a ZipFile or ZipBuffer that does not contain an entry with that name.

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.

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.

A mutating method (such as zipFile.addEntry() or zipFile.delete()) was called on a ZipFile that was not opened with { writable: true }.