Skip to content

Navigation Menu

Sign in
Appearance settings

Search code, repositories, users, issues, pull requests...

Provide feedback

We read every piece of feedback, and take your input very seriously.

Saved searches

Use saved searches to filter your results more quickly

Appearance settings

Commit c139d2a

Browse filesBrowse files
BridgeARMylesBorins
authored andcommitted
doc: fix unhandled to uncaught
PR-URL: #20293 Reviewed-By: Vse Mozhet Byt <vsemozhetbyt@gmail.com> Reviewed-By: Richard Lau <riclau@uk.ibm.com> Reviewed-By: Trivikram Kamat <trivikr.dev@gmail.com> Reviewed-By: Luigi Pinca <luigipinca@gmail.com>
1 parent 81de533 commit c139d2a
Copy full SHA for c139d2a

File tree

Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed
Open diff view settings
Filter options
Expand file treeCollapse file tree

1 file changed

+1
-1
lines changed
Open diff view settings
Collapse file

‎doc/api/errors.md‎

Copy file name to clipboardExpand all lines: doc/api/errors.md
+1-1Lines changed: 1 addition & 1 deletion
  • Display the source diff
  • Display the rich diff
Original file line numberDiff line numberDiff line change
@@ -107,7 +107,7 @@ pass or fail).
107107

108108
For *all* [`EventEmitter`][] objects, if an `'error'` event handler is not
109109
provided, the error will be thrown, causing the Node.js process to report an
110-
unhandled exception and crash unless either: The [`domain`][domains] module is
110+
uncaught exception and crash unless either: The [`domain`][domains] module is
111111
used appropriately or a handler has been registered for the
112112
[`'uncaughtException'`][] event.
113113

0 commit comments

Comments
0 (0)
Morty Proxy This is a proxified and sanitized view of the page, visit original site.