Storing listeners in a Map<event, Set<handler>> gives O(1) add/remove and prevents duplicate registrations of the same function. Returning an unsubscribe function from on is a small ergonomic win that pairs well with React effects (return unsubscribe) and removes the need for callers to keep a reference to the original handler. Iterating over [...set] in emit snapshots the listener list so a handler that calls off mid-dispatch does not skip later listeners. Use this when you need decoupled cross-tree messaging without pulling in a dependency.

once is the right primitive for boot signals, modal-confirm replies, and any 'wait for the next event of type X' pattern. Implementing it as on plus an immediate off() inside the wrapped handler keeps the listener registry clean and fires exactly once even if emit is called many times. Returning the unsubscribe function lets callers cancel a pending one-shot if the surrounding component unmounts before the event fires. Pair this with Promises by writing new Promise((res) => bus.once('boot:done', res)) for await-friendly call sites.

Wrapping a single event in a channel object lets callers consume the bus without typing the event name at every site, which is where typos hide bugs. In a TypeScript codebase, the channel<E extends keyof Events> generic narrows the payload to the right shape per event, so the compiler catches userLogin.emit({ wrong: true }). The pattern also makes mocking trivial in tests: pass a fake userLogin channel instead of the whole bus. Keep emit/on on the bus root for legacy code paths and let new code pick channels.