core-event-bus

A type-safe event bus manages inter-module communication by allowing modules to subscribe to specific events and broadcast payloads, ensuring the payload types match expectations to prevent runtime errors. It decouples senders from receivers.

You subscribe to events by registering a handler function for a specific event name, and broadcast events by emitting that name with a payload. The event bus then executes all subscribed handlers with the payload.

You need a centralized event bus when decoupling complex software systems where modules must notify each other of state changes, such as player movement or network status updates in game development, without direct dependencies.

Yes, the event bus supports once-only events, allowing a handler to be executed a single time for a particular event before being automatically unregistered from future broadcasts.

Yes, this event bus implementation operates with zero dependencies and ensures type-safe payload handling during event broadcasting, verifying that event payloads match the expected types defined in the handler.

You unregister a module by calling the unsubscription method for the specific event, removing its handler from the event bus so it no longer receives broadcasts for that event type.