Add build targets #11
Assignees
Milestone
Comments
This was referenced Mar 23, 2018
BenAtEventbrite
pushed a commit
that referenced
this issue
Mar 29, 2018
Added Gulp in order to create build targets for ECMAScript modules (ESM), CommonJS (cjs), Universal Modules (UMD), and dist bundles. This should hopefully be the final step before actually doing an inaugural release. * ESM - used by modern dependency systems like Webpack or Rollup that can do tree-shaking optimizations * CJS - used primarily by Node for resolving dependencies * Dist bundle - used by legacy dependency systems like requireJS * UMD - Can't think of a good use case where you'd use UMD over the previous 3, but adding it for now for completeness. May get removed in later releases Was having issues with `lodash` including everything just for `isPlainObject` so I rewrote the code to no longer need it. In the future if we do need `lodash` we should use [`lodash-es`](https://www.npmjs.com/package/lodash-es) (lodash exported as ES modules). Also changing the package name to be just `eventbrite` instead of `brite-rest`. Fixes #11
|
🎉 This issue has been resolved in version 1.0.0 🎉 The release is available on: Your semantic-release bot 📦🚀 |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Now that we've got #8 & #10 we should be good to start creating initial build targets for the package. And afterwards we can release an alpha version.
Targets we want are:
/lib/esmfor use in modern bundlers with tree-shaking/lib/cjsfor use in Node/lib/umdfor legacy bundlers that read one of AMD, CJS or browser global/distfor folks that just want to include a<script>tagAfter this (or maybe with it) we can do #2.
Check out
react-composite-eventsfor an example of generating the build targets. I spent a lot of time researching and figuring it all out 😄The text was updated successfully, but these errors were encountered: