Conversation
|
This would be really nice |
|
@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 :/ |
| "test": "tape test/*.js", | ||
| "coverage": "covert test/*.js" | ||
| "coverage": "covert test/*.js", | ||
| "prepack": "webpack" |
There was a problem hiding this comment.
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 :)
|
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. |
|
the ecma world has chosen es modules for the module standard. closing this in favor of #85 |
Publishing as a UMD bundle allows for easy use in HTML pages via unpkg:
This change is completely backward-compatible and supports:
require('hyperx')still works)window.hyperxwhen included via a<script>tagThis mirrors how React is publishing their module as well. See:
https://unpkg.com/[email protected]/cjs/