Skip to content

events: make memory leak warning name more verbose

Checklist
  • make -j4 test (UNIX), or vcbuild test nosign (Windows) passes
  • tests and/or benchmarks are included
  • documentation is changed or added
  • commit message follows commit guidelines
Affected core subsystem(s)

events

Description of change

Switch from a generic Warning to the more specific MaxListenersExceededWarning, as suggested in #8298 (separate PR for this because this is a semver-major change).

CI: https://ci.nodejs.org/job/node-test-commit/4842/

Merge request reports

Loading