fix: MaxListenersExceededWarning when much loggers share same transport

[adoyle-h]

fix #1791

[adoyle-h]

@indexzero @jcrugzz @DABH @ChrisAlderson Can you review the PR?

[devonik]

I don't think this will be ok. As I understood you should not do target.setMaxListeners(Infinity);. Because then you just ignore the Warning

Instead of this the real problem should be fixed.

[wbt]

I think it is possible to use the proposed new code in your calling context to silence the warning until there's a real fix in.

[devonik]

In my case i didn't find the bug and maybe it has to do with the winston package. I always get the warning on uncaughtException listener.
As solution I do following (entry point of lambda in this case):
process.removeAllListeners('uncaughtException') process.on('uncaughtException', (error) => { logger.error("uncaughtException from lambda entrypoint", { stack: error }) })

[wbt]

It's possible the issue is in Winston code, but silencing the warning in Winston isn't a fix of the root cause. If the warning is annoying you should be able to silence it in your own code.