Make container required without exceptions!

The title is deceiving because the container is required according to the documentation and types, so this is not “technically” a breaking change. So, what am I talking about?

app(state, actions, view)

Some of you may be aware that Hyperapp can be used partially “headless”, that is, without a DOM. While this may sound like a useful “feature”, it’s really just a side effect of how we compute the view function. Using Hyperapp as a state manager can be fun, but that’s not what this project is about.

<angy-old-man-rant> Hyperapp is for building web applications. If you are building an application that is not based web technologies, then look elsewhere. </angy-old-man-rant>

😄

[zaceno]

One reason (maybe) to leave the behavior as is wrt the container, is for testing apps (or sub-apps/modules) without the need to include a server-side-dom-library.

If all you need is to verify that actions update the state accordingly, you can just use the view as a trigger to test this. Or if you prefer just assert your views by just deep-equal-checking virtual nodes.

Obviously that’s still possible with the rendering engine running. But it’s just nice not to engage it and have to set up a fake DOM to avoid errors, if you don’t need it.

[jorgebucaran]

The people spoke! I’ll put it back then. 😃