Difference between revisions of "UnhandledPromiseRejectionWarning"
Jump to navigation
Jump to search
| Line 5: | Line 5: | ||
== See also == | == See also == | ||
* <code>[[missing 'error' handler on this Redis client]]</code> | * <code>[[missing 'error' handler on this Redis client]]</code> | ||
| − | + | * [ [[bugsnag]] ] [[Unhandled rejection]] | |
== See also == | == See also == | ||
Latest revision as of 09:27, 24 May 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)
See also[edit]
See also[edit]
Advertising:
