The current public interfaces using node's EventEmitter are being switched over to a new implementation that supports many new features including async handlers, counters (not just once), and argument cloning. Over the years we had multiple requests for such features but were limited by node's EventEmitter implementation.
As part of this transition, the following emitter APIs will no longer be supported:
newListener and removeListener eventslistenerCount()defaultMaxListenerseventNames()getMaxListeners()listenerCount()listeners()prependListener()prependOnceListener()setMaxListeners()
In addition, all existing server, request, and response events that are part of the hapi API (e.g. request.raw emitters remain unchanged) will switch to use a single format handler with a fixed number of arguments (vs. the current per-event-type function signature).
The current public interfaces using node's EventEmitter are being switched over to a new implementation that supports many new features including async handlers, counters (not just once), and argument cloning. Over the years we had multiple requests for such features but were limited by node's EventEmitter implementation.
As part of this transition, the following emitter APIs will no longer be supported:
newListenerandremoveListenereventslistenerCount()defaultMaxListenerseventNames()getMaxListeners()listenerCount()listeners()prependListener()prependOnceListener()setMaxListeners()In addition, all existing server, request, and response events that are part of the hapi API (e.g.
request.rawemitters remain unchanged) will switch to use a single format handler with a fixed number of arguments (vs. the current per-event-type function signature).