Reference

API

• h() creates a virtual DOM node (VNode) that gets rendered.
• text() turns a string into a VNode.
• app() initializes a Hyperapp app and mounts it.
• memo() creates a special VNode that is lazily rendered.

Architecture

• State represents your application's data.
• Views represent your state visually.
• Actions cause state transitions and trigger effects.
• Effects are triggered by actions to interact with external processes.
• Subscriptions dispatch actions in response to external events.
• Dispatch controls action dispatching.

    Flowchart showing the general flow of a hyperapp app.

<h2 title="“I’d like to think of browsing the glossary as flipping pages in a book. I can go anywhere instantly and learn whatever suits my fancy.” ―@icylace">Glossary</h2>

• Action: An app behavior that transitions state and invokes effects.
• Action Descriptor: A tuple representing an action with its payload.
• Component: A view with a specific purpose.
• Dispatch Function: The process that executes actions, applies state, and calls effects.
• Dispatch Initializer: A function that controls dispatch.
• Effect: A generalized encapsulation of an external process.
• Effecter: A function that carries out an effect.
• Event Payload: A payload specific to an event.
• Memoization: In Hyperapp, the delayed rendering of VNodes.
• Mount Node: The DOM element that holds the app.
• Payload: Data given to an action.
• State: The unified set of data your Hyperapp application uses and maintains.
• State Transition: An evolutionary step for the state.
• Subscriber: A function that carries out a subscription.
• Subscription: A binding between the app and external events.
• Top-Level View: The main view which is given the state.
• VDOM: The virtual DOM, an in-memory representation for the DOM of the current page.
• View: A function describing the desired DOM, represented by a VNode, as a function of the current state.
• Wrapped Action: An action that is returned by another action.