Errors
Node.js errors
ERR_* codes, module resolution and runtime errors.
462 entries1 written pages
Showing 351 to 400 of 462Source: Node.js documentation
| Code | Error | Category | Page |
|---|---|---|---|
| ERR_STREAM_WRAP | Prevents an abort if a string decoder was set on the Socket or if the decoder is in objectMode. const Socket = require('node:net').Socket; const instance = new Socket(); instance.setEncoding('utf8'); | Node.js error codes | Reference |
| ERR_STREAM_WRITE_AFTER_END | An attempt was made to call stream.write() after stream.end() has been called. | Node.js error codes | Reference |
| ERR_STRING_TOO_LONG | An attempt has been made to create a string longer than the maximum allowed length. | Node.js error codes | Reference |
| ERR_SYNTHETIC | An artificial error object used to capture the call stack for diagnostic reports. | Node.js error codes | Reference |
| ERR_SYSTEM_ERROR | An unspecified or non-specific system error has occurred within the Node.js process. The error object will have an err.info object property with additional details. | Node.js error codes | Reference |
| ERR_TAP_LEXER_ERROR | An error representing a failing lexer state. | Legacy Node.js error codes | Reference |
| ERR_TAP_PARSER_ERROR | An error representing a failing parser state. Additional information about the token causing the error is available via the cause property. | Legacy Node.js error codes | Reference |
| ERR_TAP_VALIDATION_ERROR | This error represents a failed TAP validation. | Legacy Node.js error codes | Reference |
| ERR_TEST_FAILURE | This error represents a failed test. Additional information about the failure is available via the cause property. | Node.js error codes | Reference |
| ERR_THROTTLED | A call was dropped because a throttled function could not invoke it immediately or its pending queue was full. | Node.js error codes | Reference |
| ERR_TLS_ALPN_CALLBACK_INVALID_RESULT | This error is thrown when an ALPNCallback returns a value that is not in the list of ALPN protocols offered by the client. | Node.js error codes | Reference |
| ERR_TLS_ALPN_CALLBACK_WITH_PROTOCOLS | This error is thrown when creating a TLSServer if the TLS options include both ALPNProtocols and ALPNCallback. These options are mutually exclusive. | Node.js error codes | Reference |
| ERR_TLS_CERT_ALTNAME_FORMAT | This error is thrown by checkServerIdentity if a user-supplied subjectaltname property violates encoding rules. Certificate objects produced by Node.js itself always comply with encoding rules and will never cause this error. | Node.js error codes | Reference |
| ERR_TLS_CERT_ALTNAME_INVALID | While using TLS, the host name/IP of the peer did not match any of the subjectAltNames in its certificate. | Node.js error codes | Reference |
| ERR_TLS_DH_PARAM_SIZE | While using TLS, the parameter offered for the Diffie-Hellman (DH) key-agreement protocol is too small. By default, the key length must be greater than or equal to 1024 bits to avoid vulnerabilities, even though it is strongly recommended to use 2048 bits or larger for stronger security. | Node.js error codes | Reference |
| ERR_TLS_HANDSHAKE_TIMEOUT | A TLS/SSL handshake timed out. In this case, the server must also abort the connection. | Node.js error codes | Reference |
| ERR_TLS_INVALID_CONTEXT | The context must be a SecureContext. | Node.js error codes | Reference |
| ERR_TLS_INVALID_PROTOCOL_METHOD | The specified secureProtocol method is invalid. It is either unknown, or disabled because it is insecure. | Node.js error codes | Reference |
| ERR_TLS_INVALID_PROTOCOL_VERSION | Valid TLS protocol versions are 'TLSv1', 'TLSv1.1', or 'TLSv1.2'. | Node.js error codes | Reference |
| ERR_TLS_INVALID_STATE | The TLS socket must be connected and securely established. Ensure the 'secure' event is emitted before continuing. | Node.js error codes | Reference |
| ERR_TLS_PROTOCOL_VERSION_CONFLICT | Attempting to set a TLS protocol minVersion or maxVersion conflicts with an attempt to set the secureProtocol explicitly. Use one mechanism or the other. | Node.js error codes | Reference |
| ERR_TLS_PSK_SET_IDENTITY_HINT_FAILED | Failed to set PSK identity hint. Hint may be too long. | Node.js error codes | Reference |
| ERR_TLS_RENEGOTIATION_DISABLED | An attempt was made to renegotiate TLS on a socket instance with renegotiation disabled. | Node.js error codes | Reference |
| ERR_TLS_RENEGOTIATION_FAILED | Used when a TLS renegotiation request has failed in a non-specific way. | Legacy Node.js error codes | Reference |
| ERR_TLS_RENEGOTIATION_UNSUPPORTED | An attempt was made to renegotiate TLS, but the TLS implementation does not support caller-initiated renegotiation. | Node.js error codes | Reference |
| ERR_TLS_REQUIRED_SERVER_NAME | While using TLS, the server.addContext() method was called without providing a host name in the first parameter. | Node.js error codes | Reference |
| ERR_TLS_SESSION_ATTACK | An excessive amount of TLS renegotiations is detected, which is a potential vector for denial-of-service attacks. | Node.js error codes | Reference |
| ERR_TLS_SNI_FROM_SERVER | An attempt was made to issue Server Name Indication from a TLS server-side socket, which is only valid from a client. | Node.js error codes | Reference |
| ERR_TRACE_EVENTS_CATEGORY_REQUIRED | The trace_events.createTracing() method requires at least one trace event category. | Node.js error codes | Reference |
| ERR_TRACE_EVENTS_UNAVAILABLE | The node:trace_events module could not be loaded because Node.js was compiled with the --without-v8-platform flag, or because the process was initialized by an embedder that provides its own V8 platform. | Node.js error codes | Reference |
| ERR_TRAILING_JUNK_AFTER_STREAM_END | Trailing junk found after the end of the compressed stream. This error is thrown when extra, unexpected data is detected after the end of a compressed stream (for example, in zlib or gzip decompression). | Node.js error codes | Reference |
| ERR_TRANSFERRING_EXTERNALIZED_SHAREDARRAYBUFFER | A SharedArrayBuffer whose memory is not managed by the JavaScript engine or by Node.js was encountered during serialization. Such a SharedArrayBuffer cannot be serialized. | Legacy Node.js error codes | Reference |
| ERR_TRANSFORM_ALREADY_TRANSFORMING | A Transform stream finished while it was still transforming. | Node.js error codes | Reference |
| ERR_TRANSFORM_WITH_LENGTH_0 | A Transform stream finished with data still in the write buffer. | Node.js error codes | Reference |
| ERR_TTY_INIT_FAILED | The initialization of a TTY failed due to a system error. | Node.js error codes | Reference |
| ERR_UNAVAILABLE_DURING_EXIT | Function was called within a process.on('exit') handler that shouldn't be called within process.on('exit') handler. | Node.js error codes | Reference |
| ERR_UNCAUGHT_EXCEPTION_CAPTURE_ALREADY_SET | process.setUncaughtExceptionCaptureCallback() was called twice, without first resetting the callback to null. This error is designed to prevent accidentally overwriting a callback registered from another module. | Node.js error codes | Reference |
| ERR_UNESCAPED_CHARACTERS | A string that contained unescaped characters was received. | Node.js error codes | Reference |
| ERR_UNHANDLED_ERROR | An unhandled error occurred (for instance, when an 'error' event is emitted by an EventEmitter but an 'error' handler is not registered). | Node.js error codes | Reference |
| ERR_UNKNOWN_BUILTIN_MODULE | Used to identify a specific kind of internal Node.js error that should not typically be triggered by user code. Instances of this error point to an internal bug within the Node.js binary itself. | Node.js error codes | Reference |
| ERR_UNKNOWN_CREDENTIAL | A Unix group or user identifier that does not exist was passed. | Node.js error codes | Reference |
| ERR_UNKNOWN_ENCODING | An invalid or unknown encoding option was passed to an API. | Node.js error codes | Reference |
| ERR_UNKNOWN_FILE_EXTENSION | An attempt was made to load a module with an unknown or unsupported file extension. | Node.js error codes | Reference |
| ERR_UNKNOWN_MODULE_FORMAT | An attempt was made to load a module with an unknown or unsupported format. | Node.js error codes | Reference |
| ERR_UNKNOWN_SIGNAL | An invalid or unknown process signal was passed to an API expecting a valid signal (such as subprocess.kill()). | Node.js error codes | Reference |
| ERR_UNKNOWN_STDIN_TYPE | An attempt was made to launch a Node.js process with an unknown stdin file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it. | Legacy Node.js error codes | Reference |
| ERR_UNKNOWN_STREAM_TYPE | An attempt was made to launch a Node.js process with an unknown stdout or stderr file type. This error is usually an indication of a bug within Node.js itself, although it is possible for user code to trigger it. | Legacy Node.js error codes | Reference |
| ERR_UNSUPPORTED_DIR_IMPORT | import a directory URL is unsupported. Instead, self-reference a package using its name and define a custom subpath in the "exports" field of the package.json file. import './'; // unsupported import './index.js'; // supported import 'package-name'; // supported | Node.js error codes | Reference |
| ERR_UNSUPPORTED_ESM_URL_SCHEME | import with URL schemes other than file and data is unsupported. | Node.js error codes | Reference |
| ERR_UNSUPPORTED_NODE_MODULES_TYPE_STRIPPING | Type stripping is not supported for files descendant of a node_modules directory. | Node.js error codes | Reference |
Other families: JavaScript, npm, React, Next.js, TypeScript, Vite, webpack, Jest