emitter-domain
Allows for improved domain error handling for emitters
Domain EventEmitter Error Handling in Node
By default in node.js, EventEmitter errors are implicitely handled by the Domain in which the EventEmitter is created.
To handle EventEmitter errors in an alternate Domain it must be added explicitely using domain.add
, but sometimes this isn't possible. This can make EventEmitter errors hard to trace:
EventEmitter Handler Error Example
var Domain = var emittervar domain1 = Domaindomain1domain1 var domain2 = Domaindomain2domain2 { console} { console}
Above, the error in fooHandler
gets handled by domain1
and handleCreateErr
.
EventEmitter Emit Error Example
var Domain = var emittervar domain1 = Domaindomain1domain1 var domain2 = Domaindomain2domain2 { console} { console}
Above, the error emitted gets handled by domain1
and handleCreateErr
.
Examples using EmitterDomains
Any EventEmitters created w/in EmitterDomains emit errors more predictably.
EventEmitter Handler Error Example w/ EmitterDomain
var EmitterDomain = var Domain = var emittervar domain1 = EmitterDomaindomain1domain1 var domain2 = Domaindomain2domain2 { console} { console}
Above, the error in fooHandler
gets handled by domain2
and handleEmitterErr
!
EventEmitter Emit Error Example w/ EmitterDomain
var EmitterDomain = var Domain = var emittervar domain1 = Domaindomain1domain1 var domain2 = Domaindomain2domain2 { console} { console}
Above, the error emitted gets handled by domain2
and handleEmitterErr
!
TLDR;
As event emitters are used throughout an application, it can be hard to handle their errors with domains. EmitterDomains make event emitter errors bubble to domains wrapping the currently executing code.
License
MIT