Difference between revisions of "UnhandledPromiseRejectionWarning"
Jump to navigation
Jump to search
Tags: Mobile web edit, Mobile edit |
|||
Line 6: | Line 6: | ||
[[missing 'error' handler on this Redis client]] | [[missing 'error' handler on this Redis client]] | ||
+ | == See also == | ||
+ | * {{Node}} | ||
− | + | [[Category:Node]] |
Revision as of 07:36, 9 March 2023
(node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 1) (node:1) [DEP0018] DeprecationWarning: Unhandled promise rejections are deprecated. In the future, promise rejections that are not handled will terminate the Node.js process with a non-zero exit code. (node:1) UnhandledPromiseRejectionWarning: Unhandled promise rejection. This error originated either by throwing inside of an async function without a catch block, or by rejecting a promise which was not handled with .catch(). To terminate the node process on unhandled promise rejection, use the CLI flag `--unhandled-rejections=strict` (see https://nodejs.org/api/cli.html#cli_unhandled_rejections_mode). (rejection id: 2)
missing 'error' handler on this Redis client
See also
Advertising: