Errors
Node.js errors
ERR_* codes, module resolution and runtime errors.
462 entries1 written pages
Showing 101 to 150 of 462Source: Node.js documentation
| Code | Error | Category | Page |
|---|---|---|---|
| ERR_EVENT_RECURSION | Thrown when an attempt is made to recursively dispatch an event on EventTarget. | Node.js error codes | Reference |
| ERR_EXECUTION_ENVIRONMENT_NOT_AVAILABLE | The JS execution context is not associated with a Node.js environment. This may occur when Node.js is used as an embedded library and some hooks for the JS engine are not set up properly. | Node.js error codes | Reference |
| ERR_FALSY_VALUE_REJECTION | A Promise that was callbackified via util.callbackify() was rejected with a falsy value. | Node.js error codes | Reference |
| ERR_FEATURE_UNAVAILABLE_ON_PLATFORM | Used when a feature that is not available to the current platform which is running Node.js is used. | Node.js error codes | Reference |
| ERR_FFI_CALL_FAILED | A low-level FFI call failed. | Node.js error codes | Reference |
| ERR_FFI_INVALID_POINTER | An invalid pointer was passed to an FFI operation. | Node.js error codes | Reference |
| ERR_FFI_LIBRARY_CLOSED | An operation was attempted on an FFI dynamic library after it was closed. | Node.js error codes | Reference |
| ERR_FS_CP_DIR_TO_NON_DIR | An attempt was made to copy a directory to a non-directory (file, symlink, etc.) using fs.cp(). | Node.js error codes | Reference |
| ERR_FS_CP_EEXIST | An attempt was made to copy over a file that already existed with fs.cp(), with the force and errorOnExist set to true. | Node.js error codes | Reference |
| ERR_FS_CP_EINVAL | When using fs.cp(), src or dest pointed to an invalid path. | Node.js error codes | Reference |
| ERR_FS_CP_FIFO_PIPE | An attempt was made to copy a named pipe with fs.cp(). | Node.js error codes | Reference |
| ERR_FS_CP_NON_DIR_TO_DIR | An attempt was made to copy a non-directory (file, symlink, etc.) to a directory using fs.cp(). | Node.js error codes | Reference |
| ERR_FS_CP_SOCKET | An attempt was made to copy to a socket with fs.cp(). | Node.js error codes | Reference |
| ERR_FS_CP_SYMLINK_TO_SUBDIRECTORY | When using fs.cp(), a symlink in dest pointed to a subdirectory of src. | Node.js error codes | Reference |
| ERR_FS_CP_UNKNOWN | An attempt was made to copy to an unknown file type with fs.cp(). | Node.js error codes | Reference |
| ERR_FS_EISDIR | Path is a directory. | Node.js error codes | Reference |
| ERR_FS_FILE_TOO_LARGE | An attempt was made to read a file larger than the supported 2 GiB limit for fs.readFile(). This is not a limitation of Buffer, but an internal I/O constraint. | Node.js error codes | Reference |
| ERR_FS_INVALID_SYMLINK_TYPE | An invalid symlink type was passed to the fs.symlink() or fs.symlinkSync() methods. | Legacy Node.js error codes | Reference |
| ERR_FS_WATCH_QUEUE_OVERFLOW | The number of file system events queued without being handled exceeded the size specified in maxQueue in fs.watch(). | Node.js error codes | Reference |
| ERR_HTTP2_ALTSVC_INVALID_ORIGIN | HTTP/2 ALTSVC frames require a valid origin. | Node.js error codes | Reference |
| ERR_HTTP2_ALTSVC_LENGTH | HTTP/2 ALTSVC frames are limited to a maximum of 16,382 payload bytes. | Node.js error codes | Reference |
| ERR_HTTP2_CONNECT_AUTHORITY | For HTTP/2 requests using the CONNECT method, the :authority pseudo-header is required. | Node.js error codes | Reference |
| ERR_HTTP2_CONNECT_PATH | For HTTP/2 requests using the CONNECT method, the :path pseudo-header is forbidden. | Node.js error codes | Reference |
| ERR_HTTP2_CONNECT_SCHEME | For HTTP/2 requests using the CONNECT method, the :scheme pseudo-header is forbidden. | Node.js error codes | Reference |
| ERR_HTTP2_ERROR | A non-specific HTTP/2 error has occurred. | Node.js error codes | Reference |
| ERR_HTTP2_FRAME_ERROR | Used when a failure occurs sending an individual frame on the HTTP/2 session. | Legacy Node.js error codes | Reference |
| ERR_HTTP2_GOAWAY_SESSION | New HTTP/2 Streams may not be opened after the Http2Session has received a GOAWAY frame from the connected peer. | Node.js error codes | Reference |
| ERR_HTTP2_HEADERS_AFTER_RESPOND | Additional headers were specified after an HTTP/2 response was initiated. | Node.js error codes | Reference |
| ERR_HTTP2_HEADERS_OBJECT | Used when an HTTP/2 Headers Object is expected. | Legacy Node.js error codes | Reference |
| ERR_HTTP2_HEADERS_SENT | An attempt was made to send multiple response headers. | Node.js error codes | Reference |
| ERR_HTTP2_HEADER_REQUIRED | Used when a required header is missing in an HTTP/2 message. | Legacy Node.js error codes | Reference |
| ERR_HTTP2_HEADER_SINGLE_VALUE | Multiple values were provided for an HTTP/2 header field that was required to have only a single value. | Node.js error codes | Reference |
| ERR_HTTP2_INFO_HEADERS_AFTER_RESPOND | HTTP/2 informational headers must only be sent prior to calling the Http2Stream.prototype.respond() method. | Legacy Node.js error codes | Reference |
| ERR_HTTP2_INFO_STATUS_NOT_ALLOWED | Informational HTTP status codes (1xx) may not be set as the response status code on HTTP/2 responses. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_CONNECTION_HEADERS | HTTP/1 connection specific headers are forbidden to be used in HTTP/2 requests and responses. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_HEADER_VALUE | An invalid HTTP/2 header value was specified. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_INFO_STATUS | An invalid HTTP informational status code has been specified. Informational status codes must be an integer between 100 and 199 (inclusive). | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_ORIGIN | HTTP/2 ORIGIN frames require a valid origin. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_PACKED_SETTINGS_LENGTH | Input Buffer and Uint8Array instances passed to the http2.getUnpackedSettings() API must have a length that is a multiple of six. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_PSEUDOHEADER | Only valid HTTP/2 pseudoheaders (:status, :path, :authority, :scheme, and :method) may be used. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_SESSION | An action was performed on an Http2Session object that had already been destroyed. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_SETTING_VALUE | An invalid value has been specified for an HTTP/2 setting. | Node.js error codes | Reference |
| ERR_HTTP2_INVALID_STREAM | An operation was performed on a stream that had already been destroyed. | Node.js error codes | Reference |
| ERR_HTTP2_MAX_PENDING_SETTINGS_ACK | Whenever an HTTP/2 SETTINGS frame is sent to a connected peer, the peer is required to send an acknowledgment that it has received and applied the new SETTINGS. By default, a maximum number of unacknowledged SETTINGS frames may be sent at any given time. | Node.js error codes | Reference |
| ERR_HTTP2_NESTED_PUSH | An attempt was made to initiate a new push stream from within a push stream. Nested push streams are not permitted. | Node.js error codes | Reference |
| ERR_HTTP2_NO_MEM | Out of memory when using the http2session.setLocalWindowSize(windowSize) API. | Node.js error codes | Reference |
| ERR_HTTP2_NO_SOCKET_MANIPULATION | An attempt was made to directly manipulate (read, write, pause, resume, etc.) a socket attached to an Http2Session. | Node.js error codes | Reference |
| ERR_HTTP2_ORIGIN_LENGTH | HTTP/2 ORIGIN frames are limited to a length of 16382 bytes. | Node.js error codes | Reference |
| ERR_HTTP2_OUT_OF_STREAMS | The number of streams created on a single HTTP/2 session reached the maximum limit. | Node.js error codes | Reference |
| ERR_HTTP2_PAYLOAD_FORBIDDEN | A message payload was specified for an HTTP response code for which a payload is forbidden. | Node.js error codes | Reference |
Other families: JavaScript, npm, React, Next.js, TypeScript, Vite, webpack, Jest