hyperapp

[marcus-herrmann]

https://hyperapp.js.org/

[SteveALee]

My thoughts on using hyperapp are that it offers the minimal possible framework of the type that is very popular for SPAs; namely VDOM views (jsx or hyperscript) + action functions + single state store. Thus it can provide a clear way to demonstrate design issues common to other frameworks.

It does have a few unique features compared to Vue, Reacts etc (but then they are all different and that is part of the vision here). V2 is imminent and makes a few big changes.

• Only pure functional views (access state and actions) and components (props only)
• Stateful 'components' are possible by nesting apps
• So called Lazy components get access to global state (a bit like React context) - bit of an anti pattern IMHO
• Pure action functions - can be automatically bound to subsets of state tree (so called slices)
• Absolute minimal lifecyle hooks
• Typescript support a little immature
• Easy to use as a global script (ie via Githubissues.
• Githubissues is a development platform for aggregating issues.