wode-emittery-pattern

To decouple side effects from Zustand store actions, enforce an event-driven architecture where store actions only emit type-safe Emittery events, allowing sidecar components to handle side-effect execution independently.

The sidecar pattern isolates side-effect logic like toasts, confirms, and network requests into dedicated sidecar components that subscribe to typed Emittery events emitted by Zustand store actions.

Set up typed event contracts by defining `as const` event type objects in `Module:Action` form and creating strongly typed emitter and data payload mappings to ensure type safety end-to-end.

Yes, you can use Emittery for module-scoped inter-component communication by applying a listener hook pattern that allows sidecar components to react to typed event payloads emitted across module boundaries.

Store actions should only emit events to improve testability and separation of concerns, ensuring tightly coupled UI and store logic is replaced by a consistent event-driven architecture without embedded side effects.