Do we think that adding it in the CLI adds to the debugging ergonomics? getEventListeners it not standard or very-well known, we might want to drop it eventually.

Adding it to the tree seems very confusing ux the way it is right now. So I was doing this so I could debug easier. If you want to scrap this cl then that is fine. But we need something to promote passive event listeners. 

I don't think we need a tree. And we already have the list there. Could we simply render all the listeners in the list?

Yes, the list was what I was referring to. It is a list based on the Dom tree. But it is kind of weird with ancestors and show descendants. That is basically all event listeners in the document. How should the ux look ? 

As a plain list of the listeners? I guess Ancestors and Descendants options should be mutually exclusive.

Right, that was my original approach to have a select list showing descendants, ancestors, target only. But that idea was rejected due to the extra time it would require to iterate the Dom. And that we didn't want users to set it to descendants and cause full tree walks. 

may be implemented by  issue 688537 

I believe i fixed it a while ago.