wode-emittery-pattern

What problem does it solve?

It solves tightly coupled UI/store logic by forcing inter-component communication and side-effect handling to use a consistent event-driven architecture instead of embedding side effects inside state actions.

Core Features & Use Cases

• Typed event contracts: Use as const event type objects and strongly typed emitter/data mappings to keep event payloads correct end-to-end.
• Store emits only: Zustand (or store) actions only emit events and never run side effects, improving testability and separation of concerns.
• Sidecar handlers: Side-effects like toasts, confirms, and network requests live in sidecar components that subscribe to emitted events using a listener hook pattern.
• Clear naming & structure: Enforce Module:Action event naming to keep large apps organized and discoverable.

Quick Start

Use wode-emittery-pattern when implementing a Zustand store and React sidecar so that store actions emit typed Emittery events and the sidecar components perform the confirm/toast/network work.