doc: avoid mentioning 'uncaughtException' #16905
Closed
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
I think we should not mention the
'uncaughtException'
event in the documentation of the error events. Experience has taught me that it is usually used in the wrong way leading to bizarre situations like parsers blocked in a wrong state, events emitted multiple times when they should not, etc. If an'error'
event does not have a listener the process should just exit.Checklist
Affected core subsystem(s)
doc