Dmitriy Mozgovoy

Yes, JSDoc has the same behavior (I thought the package has its own parser because of jsoc-parser in the dependencies), but since it renders docs as html it's possible to...

But this package could just replace `@` to `@` and then output it to a markdown block of code. This would not be an ideal solution, but acceptable to have...

Yeap. This lib has a bit more issues that just emitAsync and currently i have not an idea how to fix that and keep 100% compability. Some internal props isn't...

[It doesn’t look so good :) We have to fix this 😄 ](https://www.npmtrends.com/eventemitter2-vs-eventemitter3-vs-eventemitter4-vs-events-vs-EventEmitter)

@RangerMauve I just found out that wildcard emitter benchmark is totally fake 😄 https://github.com/EventEmitter2/EventEmitter2/blob/f3f642f17e081ec605e4504b8c5ca002d3f663ba/test/perf/benchmark.js#L11 https://github.com/EventEmitter2/EventEmitter2/blob/799d2f83305ce6752d54038e865416942763ed64/test/perf/benchmark.js#L38-L44 Previously i wonder how that heavy code has a performance only three times less than...

@RangerMauve not for long, It looks like just about 9 years :) It seems searchListenerTree is too slow and over complicated for emit purpose. And it's hard to refactor it,...

@RangerMauve Hm. I never needed to use wildcards emitters, at least something harder than basic one level wildcard e.g. `event.*` . This lib supports multilevel * and ** and in...

Thanks for the report! I just fixed it :)

@gengshenghong The EventNS type is not an array of separate events. It is an event namespace/event path for the wildcard emitter. It could be a string like 'body.menu.click' or an...

Unfortunately EventEmitter2 does not currently support this static method. Its api corresponds to v11.