Publish as UMD bundle

[jrop]

Publishing as a UMD bundle allows for easy use in HTML pages via unpkg:

<script src="https://unpkg.com/hyperapp@1.0.1/dist/hyperapp.js"></script>
<script src="https://unpkg.com/hyperx@latest/dist/hyperx.min.js"></script>
<script>
  const {app, h} = hyperapp
  const hx = hyperx(h)
  const main = app(
    {}, // state
    {}, // actions
    () => hx`<div>Hello from HyperX!</div>`,
    document.getElementById('root')
  )
</script>

This change is completely backward-compatible and supports:

• CommonJS (require('hyperx') still works)
• AMD
• library exported as window.hyperx when included via a <script> tag

This mirrors how React is publishing their module as well. See: https://unpkg.com/react@16.2.0/cjs/

[jrop]

Here is a demo of it in action on CodePen.

[tsjnsn]

This would be really nice

[jrop]

@tsjnsn For the moment, I published a single version of a UMD build of this package here:

https://www.npmjs.com/package/@jrop/hyperx

I still would like to have this merged though :/

[goto-bus-stop]

using browserify with tinyify seems simpler than placing a webpack config file in the root just for umd:

"scripts": {
  "prepublish": "browserify -s hyperx -p tinyify index.js -o dist/hyperx.js"
}

and a bit more in line with other choo-adjacent projects :)

[goto-bus-stop]

personally i'm cool with publishing UMD builds. I know not everyone in the choojs org likes em tho. you can also use https://wzrd.in/standalone/hyperx which browserifies a UMD build on the fly.

[mreinstein]

the ecma world has chosen es modules for the module standard. closing this in favor of #85