doc: clarify `unhandledRejection` events behaviors in process doc · nodejs/node@d940b15 · GitHub

nodejs / node Public

• Notifications You must be signed in to change notification settings
• Fork 36.6k
• Star 120k

• Code
• Issues 635
• Pull requests 756
• Actions
• Projects
• Security and quality
• Insights

Additional navigation options

Commit d940b15

Browse filesBrowse the repository at this point in the historyBrowse files

dario-piotrowicz

authored and

marco-ippolito

committed

doc: clarify unhandledRejection events behaviors in process doc

PR-URL: #57654 Reviewed-By: Luigi Pinca <luigipinca@gmail.com> Reviewed-By: Jake Yuesong Li <jake.yuesong@gmail.com> Reviewed-By: James M Snell <jasnell@gmail.com>

1 parent cdf3fa2 commit d940b15
Copy full SHA for d940b15

1 file changed

+4Lines changed: 4 additions & 0 deletions

File tree

Expand file treeCollapse file tree

Open diff view settings

Filter options

• doc/api
  • process.md

Expand file treeCollapse file tree

Open diff view settings

Collapse file

‎doc/api/process.md‎

Copy file name to clipboardExpand all lines: doc/api/process.md

+4Lines changed: 4 additions & 0 deletions

• Display the source diff
• Display the rich diff

Original file line number	Diff line number	Diff line change
@@ -578,6 +578,10 @@ address such failures, a non-operational
578	578	`resource.loaded`, which would prevent the `'unhandledRejection'` event from
579	579	being emitted.
580	580
	581	+ If an `'unhandledRejection'` event is emitted but not handled it will
	582	+ be raised as an uncaught exception. This alongside other behaviors of
	583	+ `'unhandledRejection'` events can changed via the [`--unhandled-rejections`][] flag.
	584	+
581	585	### Event: `'warning'`
582	586
583	587	<!-- YAML

0 commit comments

Comments

0 (0)