Errors
Node.js errors
ERR_* codes, module resolution and runtime errors.
462 entries1 written pages
Showing 151 to 200 of 462Source: Node.js documentation
| Code | Error | Category | Page |
|---|---|---|---|
| ERR_HTTP2_PING_CANCEL | An HTTP/2 ping was canceled. | Node.js error codes | Reference |
| ERR_HTTP2_PING_LENGTH | HTTP/2 ping payloads must be exactly 8 bytes in length. | Node.js error codes | Reference |
| ERR_HTTP2_PSEUDOHEADER_NOT_ALLOWED | An HTTP/2 pseudo-header has been used inappropriately. Pseudo-headers are header key names that begin with the : prefix. | Node.js error codes | Reference |
| ERR_HTTP2_PUSH_DISABLED | An attempt was made to create a push stream, which had been disabled by the client. | Node.js error codes | Reference |
| ERR_HTTP2_SEND_FILE | An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send a directory. | Node.js error codes | Reference |
| ERR_HTTP2_SEND_FILE_NOSEEK | An attempt was made to use the Http2Stream.prototype.responseWithFile() API to send something other than a regular file, but offset or length options were provided. | Node.js error codes | Reference |
| ERR_HTTP2_SESSION_ERROR | The Http2Session closed with a non-zero error code. | Node.js error codes | Reference |
| ERR_HTTP2_SETTINGS_CANCEL | The Http2Session settings canceled. | Node.js error codes | Reference |
| ERR_HTTP2_SOCKET_BOUND | An attempt was made to connect a Http2Session object to a net.Socket or tls.TLSSocket that had already been bound to another Http2Session object. | Node.js error codes | Reference |
| ERR_HTTP2_SOCKET_UNBOUND | An attempt was made to use the socket property of an Http2Session that has already been closed. | Node.js error codes | Reference |
| ERR_HTTP2_STATUS_101 | Use of the 101 Informational status code is forbidden in HTTP/2. | Node.js error codes | Reference |
| ERR_HTTP2_STATUS_INVALID | An invalid HTTP status code has been specified. Status codes must be an integer between 100 and 599 (inclusive). | Node.js error codes | Reference |
| ERR_HTTP2_STREAM_CANCEL | An Http2Stream was destroyed before any data was transmitted to the connected peer. | Node.js error codes | Reference |
| ERR_HTTP2_STREAM_CLOSED | Used when an action has been performed on an HTTP/2 Stream that has already been closed. | Legacy Node.js error codes | Reference |
| ERR_HTTP2_STREAM_ERROR | A non-zero error code was been specified in an RST_STREAM frame. | Node.js error codes | Reference |
| ERR_HTTP2_STREAM_SELF_DEPENDENCY | When setting the priority for an HTTP/2 stream, the stream may be marked as a dependency for a parent stream. This error code is used when an attempt is made to mark a stream and dependent of itself. | Node.js error codes | Reference |
| ERR_HTTP2_TOO_MANY_CUSTOM_SETTINGS | The number of supported custom settings (10) has been exceeded. | Node.js error codes | Reference |
| ERR_HTTP2_TOO_MANY_INVALID_FRAMES | The limit of acceptable invalid HTTP/2 protocol frames sent by the peer, as specified through the maxSessionInvalidFrames option, has been exceeded. | Node.js error codes | Reference |
| ERR_HTTP2_TOO_MANY_ORIGINS | The number of uniq origin sent by the server has exceeded the value defined in options.maxOriginSetSize. | Node.js error codes | Reference |
| ERR_HTTP2_TRAILERS_ALREADY_SENT | Trailing headers have already been sent on the Http2Stream. | Node.js error codes | Reference |
| ERR_HTTP2_TRAILERS_NOT_READY | The http2stream.sendTrailers() method cannot be called until after the 'wantTrailers' event is emitted on an Http2Stream object. The 'wantTrailers' event will only be emitted if the waitForTrailers option is set for the Http2Stream. | Node.js error codes | Reference |
| ERR_HTTP2_UNSUPPORTED_PROTOCOL | http2.connect() was passed a URL that uses any protocol other than http: or https:. | Node.js error codes | Reference |
| ERR_HTTP_BODY_NOT_ALLOWED | An error is thrown when writing to an HTTP response which does not allow contents. | Node.js error codes | Reference |
| ERR_HTTP_CONTENT_LENGTH_MISMATCH | Response body size doesn't match with the specified content-length header value. | Node.js error codes | Reference |
| ERR_HTTP_HEADERS_SENT | An attempt was made to add more headers after the headers had already been sent. | Node.js error codes | Reference |
| ERR_HTTP_INVALID_CHAR | Used when an invalid character is found in an HTTP response status message (reason phrase). | Legacy Node.js error codes | Reference |
| ERR_HTTP_INVALID_HEADER_VALUE | An invalid HTTP header value was specified. | Node.js error codes | Reference |
| ERR_HTTP_INVALID_STATUS_CODE | Status code was outside the regular status code range (100-999). | Node.js error codes | Reference |
| ERR_HTTP_REQUEST_TIMEOUT | The client has not sent the entire request within the allowed time. | Node.js error codes | Reference |
| ERR_HTTP_SOCKET_ASSIGNED | The given ServerResponse was already assigned a socket. | Node.js error codes | Reference |
| ERR_HTTP_SOCKET_ENCODING | Changing the socket encoding is not allowed per RFC 7230 Section 3. | Node.js error codes | Reference |
| ERR_HTTP_TRAILER_INVALID | The Trailer header was set even though the transfer encoding does not support that. | Node.js error codes | Reference |
| ERR_ILLEGAL_CONSTRUCTOR | An attempt was made to construct an object using a non-public constructor. | Node.js error codes | Reference |
| ERR_IMPORT_ASSERTION_TYPE_FAILED | An import assertion has failed, preventing the specified module to be imported. | Legacy Node.js error codes | Reference |
| ERR_IMPORT_ASSERTION_TYPE_MISSING | An import assertion is missing, preventing the specified module to be imported. | Legacy Node.js error codes | Reference |
| ERR_IMPORT_ASSERTION_TYPE_UNSUPPORTED | An import attribute is not supported by this version of Node.js. | Legacy Node.js error codes | Reference |
| ERR_IMPORT_ATTRIBUTE_MISSING | An import attribute is missing, preventing the specified module to be imported. | Node.js error codes | Reference |
| ERR_IMPORT_ATTRIBUTE_TYPE_INCOMPATIBLE | An import type attribute was provided, but the specified module is of a different type. | Node.js error codes | Reference |
| ERR_IMPORT_ATTRIBUTE_UNSUPPORTED | An import attribute is not supported by this version of Node.js. | Node.js error codes | Reference |
| ERR_INCOMPATIBLE_OPTION_PAIR | An option pair is incompatible with each other and cannot be used at the same time. | Node.js error codes | Reference |
| ERR_INDEX_OUT_OF_RANGE | A given index was out of the accepted range (e.g. negative offsets). | Legacy Node.js error codes | Reference |
| ERR_INPUT_TYPE_NOT_ALLOWED | The --input-type flag was used to attempt to execute a file. This flag can only be used with input via --eval, --print, or STDIN. | Node.js error codes | Reference |
| ERR_INSPECTOR_ALREADY_ACTIVATED | While using the node:inspector module, an attempt was made to activate the inspector when it already started to listen on a port. Use inspector.close() before activating it on a different address. | Node.js error codes | Reference |
| ERR_INSPECTOR_ALREADY_CONNECTED | While using the node:inspector module, an attempt was made to connect when the inspector was already connected. | Node.js error codes | Reference |
| ERR_INSPECTOR_CLOSED | While using the node:inspector module, an attempt was made to use the inspector after the session had already closed. | Node.js error codes | Reference |
| ERR_INSPECTOR_COMMAND | An error occurred while issuing a command via the node:inspector module. | Node.js error codes | Reference |
| ERR_INSPECTOR_NOT_ACTIVE | The inspector is not active when inspector.waitForDebugger() is called. | Node.js error codes | Reference |
| ERR_INSPECTOR_NOT_AVAILABLE | The node:inspector module is not available for use. | Node.js error codes | Reference |
| ERR_INSPECTOR_NOT_CONNECTED | While using the node:inspector module, an attempt was made to use the inspector before it was connected. | Node.js error codes | Reference |
| ERR_INSPECTOR_NOT_WORKER | An API was called on the main thread that can only be used from the worker thread. | Node.js error codes | Reference |
Other families: JavaScript, npm, React, Next.js, TypeScript, Vite, webpack, Jest