Extract Hyperx from core

Depending on https://github.com/substack/hyperxify/pull/8 to be merged to move forward is not reasonable. But the truth is that even if it’s not merged, hyperxify can still be used with HyperApp, it’s just a little more laborious.

const { h, app } = require("hyperapp")
const hyperx = require("hyperx")
const html = hyperx(h)

app({
    model: "Hi.",
    view: model => html`<h1>${model}</h1>`
})

browserify -t hyperxify index.js -g uglifyify | uglifyjs > bundle.js

HyperApp is officially neutral in the Hyperx/template functions VS JSX debate (although the README is biased in favor of JSX on the premise that it looks “cool”), so extracting Hyperx seems a natural move.

I’ll update online examples still using html via HyperApp and write the docs.

[jorgebucaran]

True, you will no longer import { html }, which was neat, but on the other hand using hyperx out of the box makes HyperApp opinionated about two things:

• using template functions (HyperApp is neutral, use what you want)
• using the hyperx module (what if someone writes a new html parser template function better than hyperx, should we switch? use both?)

I believe removing the hyperx dependency is a logical move.

Now let’s see the biggest positive from this move:

• You can start using Hyperapp in production right now, because we finally have a build setup that works and no longer need to wait for my PR to be merged (assuming it will be ha).

[jorgebucaran]

Closing as this landed in ~@0.2.1.