Node.js error codes
Search by code or error message to find official explanations and troubleshooting or diagnostic links.
Search runs in your browser. The same number can have different meanings in different products.
Node.js Code
449 results- invalid arg type
An argument of the wrong type was passed to a Node.js API.
Node.jsNode.js - invalid arg value
An invalid or unsupported value was passed for a given argument.
Node.jsNode.js - invalid async id
An invalid asyncId or triggerAsyncId was passed using AsyncHooks. An id less than -1 should never happen.
Node.jsNode.js - invalid buffer size
A swap was performed on a Buffer but its size was not compatible with the operation.
Node.jsNode.js - invalid char
Invalid characters were detected in headers.
Node.jsNode.js - invalid cursor pos
A cursor on a given stream cannot be moved to a specified row without a specified column.
Node.jsNode.js - invalid fd
A file descriptor ('fd') was not valid (e.g. it was a negative value).
Node.jsNode.js - invalid fd type
A file descriptor ('fd') type was not valid.
Node.jsNode.js - invalid file url host
A Node.js API that consumes file: URLs (such as certain functions in the fs module) encountered a file URL with an incompatible host. This situation can only occur on Unix-like systems where only localhost or an empty host is supported.
Node.jsNode.js - invalid file url path
A Node.js API that consumes file: URLs (such as certain functions in the fs module) encountered a file URL with an incompatible path. The exact semantics for determining whether a path can be used is platform-dependent. The thrown error object includes an input property that contains the URL object of the invalid file: URL.
Node.jsNode.js - invalid handle type
An attempt was made to send an unsupported "handle" over an IPC communication channel to a child process. See subprocess.send() and process.send() for more information.
Node.jsNode.js - invalid http token
An invalid HTTP token was supplied.
Node.jsNode.js - invalid ip address
An IP address is not valid.
Node.jsNode.js - invalid mime syntax
The syntax of a MIME is not valid.
Node.jsNode.js - invalid module
An attempt was made to load a module that does not exist or was otherwise not valid.
Node.jsNode.js - invalid module specifier
The imported module string is an invalid URL, package name, or package subpath specifier.
Node.jsNode.js - invalid object define property
An error occurred while setting an invalid attribute on the property of an object.
Node.jsNode.js - invalid opt value
An invalid or unexpected value was passed in an options object.
Node.jsNode.js - invalid opt value encoding
An invalid or unknown file encoding was passed.
Node.jsNode.js - invalid package config
An invalid package.json file failed parsing.
Node.jsNode.js - invalid package target
The package.json "exports" field contains an invalid target mapping value for the attempted module resolution.
Node.jsNode.js - invalid performance mark
While using the Performance Timing API (perf_hooks), a performance mark is invalid.
Node.jsNode.js - invalid protocol
An invalid options.protocol was passed to http.request().
Node.jsNode.js - invalid repl eval config
Both breakEvalOnSigint and eval options were set in the REPL config, which is not supported.
Node.jsNode.js - invalid repl input
The input may not be used in the REPL. The conditions under which this error is used are described in the REPL documentation.
Node.jsNode.js - invalid return property
Thrown in case a function option does not provide a valid value for one of its returned object properties on execution.
Node.jsNode.js - invalid return property value
Thrown in case a function option does not provide an expected value type for one of its returned object properties on execution.
Node.jsNode.js - invalid return value
Thrown in case a function option does not return an expected value type on execution, such as when a function is expected to return a promise.
Node.jsNode.js - invalid state
Indicates that an operation cannot be completed due to an invalid state. For instance, an object may have already been destroyed, or may be performing another operation.
Node.jsNode.js - invalid sync fork input
A Buffer, TypedArray, DataView, or string was provided as stdio input to an asynchronous fork. See the documentation for the child_process module for more information.
Node.jsNode.js - invalid this
A Node.js API function was called with an incompatible this value.
Node.jsNode.js - invalid transfer object
An invalid transfer object was passed to postMessage().
Node.jsNode.js - invalid tuple
An element in the iterable provided to the WHATWG URLSearchParams constructor did not represent a [name, value] tuple – that is, if an element is not iterable, or does not consist of exactly two elements.
Node.jsNode.js - invalid typescript syntax
The provided TypeScript syntax is not valid.
Node.jsNode.js - invalid uri
An invalid URI was passed.
Node.jsNode.js - invalid url
An invalid URL was passed to the WHATWG URL constructor or the legacy url.parse() to be parsed. The thrown error object typically has an additional property 'input' that contains the URL that failed to parse.
Node.jsNode.js - invalid url pattern
An invalid URLPattern was passed to the WHATWG URLPattern constructor to be parsed.
Node.jsNode.js - invalid url scheme
An attempt was made to use a URL of an incompatible scheme (protocol) for a specific purpose. It is only used in the WHATWG URL API support in the fs module (which only accepts URLs with 'file' scheme), but may be used in other Node.js APIs as well in the future.
Node.jsNode.js - ipc channel closed
An attempt was made to use an IPC communication channel that was already closed.
Node.jsNode.js - ipc disconnected
An attempt was made to disconnect an IPC communication channel that was already disconnected. See the documentation for the child_process module for more information.
Node.jsNode.js