Errors
Node.js errors
ERR_* codes, module resolution and runtime errors.
462 entries1 written pages
Showing 1 to 50 of 462Source: Node.js documentation
| Code | Error | Category | Page |
|---|---|---|---|
| ERR_REQUIRE_ESM | require() of ES Module not supported | Node.js error codes | Causes and fixes |
| ABORT_ERR | Used when an operation has been aborted (typically using an AbortController). APIs not using AbortSignals typically do not raise an error with this code. | Node.js error codes | Reference |
| CERT_CHAIN_TOO_LONG | The certificate chain length is greater than the maximum depth. | OpenSSL error codes | Reference |
| CERT_HAS_EXPIRED | The certificate has expired: the notAfter date is before the current time. | OpenSSL error codes | Reference |
| CERT_NOT_YET_VALID | The certificate is not yet valid: the notBefore date is after the current time. | OpenSSL error codes | Reference |
| CERT_REJECTED | The root CA is marked to reject the specified purpose. | OpenSSL error codes | Reference |
| CERT_REVOKED | The certificate has been revoked; it is on a certificate revocation list (CRL). | OpenSSL error codes | Reference |
| CERT_SIGNATURE_FAILURE | The signature of the certificate is invalid. | OpenSSL error codes | Reference |
| CERT_UNTRUSTED | The root certificate authority (CA) is not marked as trusted for the specified purpose. | OpenSSL error codes | Reference |
| CRL_HAS_EXPIRED | The certificate revocation list (CRL) has expired. | OpenSSL error codes | Reference |
| CRL_NOT_YET_VALID | The certificate revocation list (CRL) has a future issue date. | OpenSSL error codes | Reference |
| CRL_SIGNATURE_FAILURE | The signature of the certificate revocation list (CRL) is invalid. | OpenSSL error codes | Reference |
| DEPTH_ZERO_SELF_SIGNED_CERT | The passed certificate is self-signed and the same certificate cannot be found in the list of trusted certificates. | OpenSSL error codes | Reference |
| ERROR_IN_CERT_NOT_AFTER_FIELD | The certificate notAfter field contains an invalid time. | OpenSSL error codes | Reference |
| ERROR_IN_CERT_NOT_BEFORE_FIELD | The certificate notBefore field contains an invalid time. | OpenSSL error codes | Reference |
| ERROR_IN_CRL_LAST_UPDATE_FIELD | The CRL lastUpdate field contains an invalid time. | OpenSSL error codes | Reference |
| ERROR_IN_CRL_NEXT_UPDATE_FIELD | The CRL nextUpdate field contains an invalid time. | OpenSSL error codes | Reference |
| ERR_ACCESS_DENIED | A special type of error that is triggered whenever Node.js tries to get access to a resource restricted by the Permission Model. | Node.js error codes | Reference |
| ERR_AMBIGUOUS_ARGUMENT | A function argument is being used in a way that suggests that the function signature may be misunderstood. | Node.js error codes | Reference |
| ERR_ARG_NOT_ITERABLE | An iterable argument (i.e. a value that works with for...of loops) was required, but not provided to a Node.js API. | Node.js error codes | Reference |
| ERR_ASSERTION | 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. | Node.js error codes | Reference |
| ERR_ASYNC_CALLBACK | An attempt was made to register something that is not a function as an AsyncHooks callback. | Node.js error codes | Reference |
| ERR_ASYNC_LOADER_REQUEST_NEVER_SETTLED | An operation related to module loading is customized by an asynchronous loader hook that never settled the promise before the loader thread exits. | Node.js error codes | Reference |
| ERR_ASYNC_TYPE | The type of an asynchronous resource was invalid. Users are also able to define their own types if using the public embedder API. | Node.js error codes | Reference |
| ERR_BROTLI_COMPRESSION_FAILED | Data passed to a Brotli stream was not successfully compressed. | Node.js error codes | Reference |
| ERR_BROTLI_INVALID_PARAM | An invalid parameter key was passed during construction of a Brotli stream. | Node.js error codes | Reference |
| ERR_BUFFER_CONTEXT_NOT_AVAILABLE | 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. | Node.js error codes | Reference |
| ERR_BUFFER_OUT_OF_BOUNDS | An operation outside the bounds of a Buffer was attempted. | Node.js error codes | Reference |
| ERR_BUFFER_TOO_LARGE | An attempt has been made to create a Buffer larger than the maximum allowed size. | Node.js error codes | Reference |
| ERR_CANNOT_TRANSFER_OBJECT | The value passed to postMessage() contained an object that is not supported for transferring. | Legacy Node.js error codes | Reference |
| ERR_CANNOT_WATCH_SIGINT | Node.js was unable to watch for the SIGINT signal. | Node.js error codes | Reference |
| ERR_CHILD_CLOSED_BEFORE_REPLY | A child process was closed before the parent received a reply. | Node.js error codes | Reference |
| ERR_CHILD_PROCESS_IPC_REQUIRED | Used when a child process is being forked without specifying an IPC channel. | Node.js error codes | Reference |
| ERR_CHILD_PROCESS_STDIO_MAXBUFFER | 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. | Node.js error codes | Reference |
| ERR_CLOSED_MESSAGE_PORT | There was an attempt to use a MessagePort instance in a closed state, usually after .close() has been called. | Node.js error codes | Reference |
| ERR_CONSOLE_WRITABLE_STREAM | Console was instantiated without stdout stream, or Console has a non-writable stdout or stderr stream. | Node.js error codes | Reference |
| ERR_CONSTRUCT_CALL_INVALID | A class constructor was called that is not callable. | Node.js error codes | Reference |
| ERR_CONSTRUCT_CALL_REQUIRED | A constructor for a class was called without new. | Node.js error codes | Reference |
| ERR_CONTEXT_NOT_INITIALIZED | 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. | Node.js error codes | Reference |
| ERR_CPU_PROFILE_ALREADY_STARTED | The CPU profile with the given name is already started. | Node.js error codes | Reference |
| ERR_CPU_PROFILE_NOT_STARTED | The CPU profile with the given name is not started. | Node.js error codes | Reference |
| ERR_CPU_PROFILE_TOO_MANY | There are too many CPU profiles being collected. | Node.js error codes | Reference |
| ERR_CPU_USAGE | The native call from process.cpuUsage could not be processed. | Legacy Node.js error codes | Reference |
| ERR_CRYPTO_ARGON2_NOT_SUPPORTED | Argon2 is not supported by the current version of OpenSSL being used. | Node.js error codes | Reference |
| ERR_CRYPTO_CUSTOM_ENGINE_NOT_SUPPORTED | An OpenSSL engine was requested (for example, through the clientCertEngine or privateKeyEngine TLS options) that is not supported by the version of OpenSSL being used, likely due to the compile-time flag OPENSSL_NO_ENGINE. | Node.js error codes | Reference |
| ERR_CRYPTO_ECDH_INVALID_FORMAT | An invalid value for the format argument was passed to the crypto.ECDH() class getPublicKey() method. | Node.js error codes | Reference |
| ERR_CRYPTO_ECDH_INVALID_PUBLIC_KEY | An invalid value for the key argument has been passed to the crypto.ECDH() class computeSecret() method. It means that the public key lies outside of the elliptic curve. | Node.js error codes | Reference |
| ERR_CRYPTO_ENGINE_UNKNOWN | An invalid crypto engine identifier was passed to require('node:crypto').setEngine(). | Node.js error codes | Reference |
| ERR_CRYPTO_FIPS_FORCED | The --force-fips command-line argument was used but there was an attempt to enable or disable FIPS mode in the node:crypto module. | Node.js error codes | Reference |
| ERR_CRYPTO_FIPS_UNAVAILABLE | An attempt was made to enable or disable FIPS mode, but FIPS mode was not available. | Node.js error codes | Reference |
Other families: JavaScript, npm, React, Next.js, TypeScript, Vite, webpack, Jest