Commit 40a9289
doc: remove extraneous sentence in events.md
Since the previous sentence describes `10` as a default, and the
following sentence explains how to modify that default, it is
unnecessary to explain that "Obviously, not all events should be limited
to just 10 listeners."
PR-URL: #32457
Reviewed-By: James M Snell <jasnell@gmail.com>
Reviewed-By: Myles Borins <myles.borins@gmail.com>1 parent 6168bd5 commit 40a9289
1 file changed
Lines changed: 3 additions & 4 deletions
| Original file line number | Diff line number | Diff line change | |
|---|---|---|---|
@@ -740,10 +740,9 @@ added: v0.3.5 | |||
| 740 | 740 | ||
| 741 | 741 | By default `EventEmitter`s will print a warning if more than `10` listeners are | |
| 742 | 742 | added for a particular event. This is a useful default that helps finding | |
| 743 | - memory leaks. Obviously, not all events should be limited to just 10 listeners. | ||
| 744 | - The `emitter.setMaxListeners()` method allows the limit to be modified for this | ||
| 745 | - specific `EventEmitter` instance. The value can be set to `Infinity` (or `0`) | ||
| 746 | - to indicate an unlimited number of listeners. | ||
| 743 | + memory leaks. The `emitter.setMaxListeners()` method allows the limit to be | ||
| 744 | + modified for this specific `EventEmitter` instance. The value can be set to | ||
| 745 | + `Infinity` (or `0`) to indicate an unlimited number of listeners. | ||
| 747 | 746 | ||
| 748 | 747 | Returns a reference to the `EventEmitter`, so that calls can be chained. | |
| 749 | 748 | ||
0 commit comments