TODO: stub event bus/broadcasting package

[brandonjpierce]

Event system

Must haves:

• Cross context comms (main thread, web worker, shared worker)
• Context isolation (main thread only, or this tab only)
• Decoupled from any form of persistence
• Strong type safety
• Strong debug tooling / observability

---

Nice to haves

• Interop with redux dev tools for introspection

---

Applicable areas to start with:

• Offscreen indicators
• Map interaction (zoom to, tether, center on)
• Baseball card management (get me out of React render cycle driving baseball cards)
• Layer interaction (click / hover layer)
• Layer management (hide/show layer, change layer order)

[brandonjpierce]

• https://github.com/pubkey/broadcast-channel/tree/master
• https://github.com/SupremeTechnopriest/react-idle-timer/tree/master
• https://github.com/Rovniy/tabs-broadcast/tree/master
• https://github.com/Romainlg29/use-broadcast/tree/main
• https://github.com/pavelstencl/broadcasterJS/tree/main

[belsrc]

It looks like you have done some initial DD on this. Is this something we, possibly, want to dive deeper into (larger discussion)? i.e.

• Are we just using an "off the shelf lib"?
• If we are, then what is really going in here and why?
• You listed some uses, but is there more which would help define things further?
• Is it even something that needs to be a package or something just used in an app if desired?

[brandonjpierce]

Yeah I think we need to chat with the folks that did some micro RfC's like Andrew and bring that into the larger conversation as you noted before we make a decision.