Skip to content
JS
Errors

Node.js errors

ERR_* codes, module resolution and runtime errors.

462 entries1 written pages
Showing 251 to 300 of 462Source: Node.js documentation
CodeError
ERR_MANIFEST_INTEGRITY_MISMATCHAn attempt was made to load a policy manifest, but the manifest had multiple entries for a resource which did not match each other. Update the manifest entries to match in order to resolve this error.
ERR_MANIFEST_INVALID_RESOURCE_FIELDA policy manifest resource had an invalid value for one of its fields. Update the manifest entry to match in order to resolve this error.
ERR_MANIFEST_INVALID_SPECIFIERA policy manifest resource had an invalid value for one of its dependency mappings. Update the manifest entry to match to resolve this error.
ERR_MANIFEST_PARSE_POLICYAn attempt was made to load a policy manifest, but the manifest was unable to be parsed. See the documentation for policy manifests for more information.
ERR_MANIFEST_TDZAn attempt was made to read from a policy manifest, but the manifest initialization has not yet taken place. This is likely a bug in Node.js.
ERR_MANIFEST_UNKNOWN_ONERRORA policy manifest was loaded, but had an unknown value for its "onerror" behavior. See the documentation for policy manifests for more information.
ERR_MEMORY_ALLOCATION_FAILEDAn attempt was made to allocate memory (usually in the C++ layer) but it failed.
ERR_MESSAGE_TARGET_CONTEXT_UNAVAILABLEA message posted to a MessagePort could not be deserialized in the target vm Context. Not all Node.js objects can be successfully instantiated in any context at this time, and attempting to transfer them using postMessage() can fail on the receiving side in that case.
ERR_METHOD_NOT_IMPLEMENTEDA method is required but not implemented.
ERR_MISSING_ARGSA required argument of a Node.js API was not passed. This is only used for strict compliance with the API specification (which in some cases may accept func(undefined) but not func()).
ERR_MISSING_MESSAGE_PORT_IN_TRANSFER_LISTThis error code was replaced by ERR_MISSING_TRANSFERABLE_IN_TRANSFER_LIST in Node.js 15.0.0, because it is no longer accurate as other types of transferable objects also exist now.
ERR_MISSING_OPTIONFor APIs that accept options objects, some options might be mandatory. This code is thrown if a required option is missing.
ERR_MISSING_PASSPHRASEAn attempt was made to read an encrypted key without specifying a passphrase.
ERR_MISSING_PLATFORM_FOR_WORKERThe V8 platform used by this instance of Node.js does not support creating Workers. This is caused by lack of embedder support for Workers.
ERR_MISSING_TRANSFERABLE_IN_TRANSFER_LISTAn object that needs to be explicitly listed in the transferList argument is in the object passed to a postMessage() call, but is not provided in the transferList for that call. Usually, this is a MessagePort.
ERR_MODULE_LINK_MISMATCHA module can not be linked because the same module requests in it are not resolved to the same module.
ERR_MODULE_NOT_FOUNDA module file could not be resolved by the ECMAScript modules loader while attempting an import operation or when loading the program entry point.
ERR_MULTIPLE_CALLBACKA callback was called more than once. A callback is almost always meant to only be called once as the query can either be fulfilled or rejected but not both at the same time.
ERR_NAPI_CONS_FUNCTIONWhile using Node-API, a constructor passed was not a function.
ERR_NAPI_CONS_PROTOTYPE_OBJECTUsed by the Node-API when Constructor.prototype is not an object.
ERR_NAPI_INVALID_DATAVIEW_ARGSWhile calling napi_create_dataview(), a given offset was outside the bounds of the dataview or offset + length was larger than a length of given buffer.
ERR_NAPI_INVALID_TYPEDARRAY_ALIGNMENTWhile calling napi_create_typedarray(), the provided offset was not a multiple of the element size.
ERR_NAPI_INVALID_TYPEDARRAY_LENGTHWhile calling napi_create_typedarray(), (length * size_of_element) + byte_offset was larger than the length of given buffer.
ERR_NAPI_TSFN_CALL_JSAn error occurred while invoking the JavaScript portion of the thread-safe function.
ERR_NAPI_TSFN_GET_UNDEFINEDAn error occurred while attempting to retrieve the JavaScript undefined value.
ERR_NAPI_TSFN_START_IDLE_LOOPOn the main thread, values are removed from the queue associated with the thread-safe function in an idle loop. This error indicates that an error has occurred when attempting to start the loop.
ERR_NAPI_TSFN_STOP_IDLE_LOOPOnce no more items are left in the queue, the idle loop must be suspended. This error indicates that the idle loop has failed to stop.
ERR_NON_CONTEXT_AWARE_DISABLEDA non-context-aware native addon was loaded in a process that disallows them.
ERR_NOT_BUILDING_SNAPSHOTAn attempt was made to use operations that can only be used when building V8 startup snapshot even though Node.js isn't building one.
ERR_NOT_IN_SINGLE_EXECUTABLE_APPLICATIONThe operation cannot be performed when it's not in a single-executable application.
ERR_NOT_SUPPORTED_IN_SNAPSHOTAn attempt was made to perform operations that are not supported when building a startup snapshot.
ERR_NO_CRYPTOAn attempt was made to use crypto features while Node.js was not compiled with OpenSSL crypto support.
ERR_NO_ICUAn attempt was made to use features that require ICU, but Node.js was not compiled with ICU support.
ERR_NO_LONGER_SUPPORTEDA Node.js API was called in an unsupported manner, such as Buffer.write(string, encoding, offset[, length]).
ERR_NO_TEMPORALAn attempt was made to use features that require Temporal, but Node.js was not compiled with Temporal support or it has been disabled in the current environment (for example, when running with --no-harmony-temporal).
ERR_NO_TYPESCRIPTAn attempt was made to use features that require Native TypeScript support, but Node.js was not compiled with TypeScript support.
ERR_OPERATION_FAILEDAn operation failed. This is typically used to signal the general failure of an asynchronous operation.
ERR_OPTIONS_BEFORE_BOOTSTRAPPINGAn attempt was made to get options before the bootstrapping was completed.
ERR_OUTOFMEMORYUsed generically to identify that an operation caused an out of memory condition.
ERR_OUT_OF_RANGEA given value is out of the accepted range.
ERR_PACKAGE_IMPORT_NOT_DEFINEDThe package.json "imports" field does not define the given internal package specifier mapping.
ERR_PACKAGE_MAP_EXTERNAL_FILEA module attempted to resolve a bare specifier using the package map, but the importing file is not located within any package defined in the map. $ node --experimental-package-map=./package-map.json /tmp/script.js Error [ERR_PACKAGE_MAP_EXTERNAL_FILE]: Cannot resolve "dep-a" from "/tmp/script.js": file is not within...
ERR_PACKAGE_MAP_INVALIDThe package map configuration file is invalid. This can occur when: The file does not exist at the specified path.
ERR_PACKAGE_MAP_KEY_NOT_FOUNDA package's dependencies object in the package map references a package key that is not defined in the packages object. { "packages": { "app": { "url": "./app", "dependencies": { "foo": "nonexistent" } } } } In this example, "nonexistent" is referenced as a dependency target but not defined in packages, which will...
ERR_PACKAGE_PATH_NOT_EXPORTEDThe package.json "exports" field does not export the requested subpath. Because exports are encapsulated, private internal modules that are not exported cannot be imported through the package resolution, unless using an absolute URL.
ERR_PARSE_ARGS_INVALID_OPTION_VALUEWhen strict set to true, thrown by util.parseArgs() if a <boolean> value is provided for an option of type <string>, or if a <string> value is provided for an option of type <boolean>.
ERR_PARSE_ARGS_UNEXPECTED_POSITIONALThrown by util.parseArgs(), when a positional argument is provided and allowPositionals is set to false.
ERR_PARSE_ARGS_UNKNOWN_OPTIONWhen strict set to true, thrown by util.parseArgs() if an argument is not configured in options.
ERR_PARSE_HISTORY_DATAThe node:repl module was unable to parse data from the REPL history file.
ERR_PERFORMANCE_INVALID_TIMESTAMPAn invalid timestamp value was provided for a performance mark or measure.

Other families: JavaScript, npm, React, Next.js, TypeScript, Vite, webpack, Jest