How codesplinta/busser works
Main Components Overview
a) Core Event System
• Event Bus (Central messaging system)
• Event Emitters
• Event Subscribers
b) State Management Layer
• Storage Handlers (Browser Storage, URL State)
• State Primitives (List, Count, Property, Composite)
• Signals Integration
c) Hook Categories
• Core Hooks (useBus, useOn)
• State Hooks (useList, useCount, etc.)
• Utility Hooks (useOutsideClick, useControlKeysPress, etc.)
Key Relationships
• Event flow between components using the event bus
• State updates and their propagation
• Integration points with external storage (Browser Storage, URL)
• Signal-based reactivity paths
Architectural Patterns
• Cascade Broadcasts pattern
• Shadow Events system
• Publisher/Subscriber model
• State primitive transformations
Implementation Details
Technical aspects:
[Event Bus Core]
↓
[State Primitives] → [Signal Variants]
↓
[Storage Adapters] → [Browser Storage/URL]
↓
[Utility Hooks]
Component Relationships
Key interactions:
useBus() ←→ Event Bus Core
useList()/useCount() ←→ State Primitives
useBrowserStorage() ←→ Storage Adapters
useControlKeysPress() ←→ Utility Layer
Data Flow
Following flows:
Component A → Event Bus → Component B
State Update → Signal → UI Update
Browser Storage → State → Component