How jorgebucaran/hyperapp works
Main Components
a) Core Framework Layer:
• Virtual DOM Engine
• State Management System
• Action Handler
• Effect System
• Subscription System
b) Official Package Ecosystem:
• DOM Package
• SVG Package
• HTML Package
• Time Package
• Events Package
Key Architectural Elements
• State → View → Actions → State (cycle)
• Effects and Subscriptions as side-effect handlers
Top Level:
┌─────────────────────────────────────────────┐
• Client Browser │
• ┘
Core Framework (Center):
┌─────────────────────────────────────────────┐
• Hyperapp Core │
• ┌─────────┐ ┌─────────┐ ┌─────────┐ │
• State │ -> │ View │ -> │ Actions │ │
• ┘ └─────────┘ └─────────┘ │
• ↑ │ │
• ┘ │
• ┘
Side Systems (Connected to Core):
┌─────────────┐ ┌─────────────┐
• Effects │ │Subscriptions│
• ┘ └─────────────┘
Important Details
a) Core Framework Features:
• 1KB size indicator
• Virtual DOM optimization
• State management flow
b) Package Integration:
• How official packages connect to the core
• Extension points for custom effects/subscriptions
Notes for Implementation Details
• How h() and text() functions relate to the Virtual DOM
• Where state updates trigger re-renders
• Where side effects can occur