| FazBrowse GitHub Viewer | Trending | | Home |
| Tools: [Download Repo ZIP] [Original HTTPS Page] |
There was a problem hiding this comment.
"the process.on('uncaughtException') event" is confusing since it's a piece of code and not just the event name.
Sorry, something went wrong.
There was a problem hiding this comment.
Perhaps:
To guard against crashing the Node.js process, a listener can be registered on
the `process` object's `'uncaughtException'` event
(e.g. `process.on('uncaughtException', (err) => /* ... */)`) or the [`domain`][] module
can be used...
Sorry, something went wrong.
There was a problem hiding this comment.
That seems mostly alright to me, except I think if we're going to have a code example like that, it shouldn't be inline, it takes up too much space IMHO.
Sorry, something went wrong.
|
Great to see this. Left some comments! |
Sorry, something went wrong.
Sorry, something went wrong.
|
LGTM |
Sorry, something went wrong.
|
Bump! |
Sorry, something went wrong.
|
Landing this tomorrow if there are no more comments. |
Sorry, something went wrong.
Sorry, something went wrong.
PR-URL: #7480 Reviewed-By: James M Snell <jasnell@gmail.com>
PR-URL: #7480 Reviewed-By: James M Snell <jasnell@gmail.com>
| Back | FazBrowse Home | New Git URL |
Checklist
Affected core subsystem(s)
doc, events
Description of change
general doc improvements
cc @nodejs/documentation