Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Different ways of consuming application and their requirements #47

Open
juanca opened this issue Sep 19, 2017 · 0 comments
Open

Different ways of consuming application and their requirements #47

juanca opened this issue Sep 19, 2017 · 0 comments

Comments

@juanca
Copy link
Contributor

juanca commented Sep 19, 2017

It has become obvious that different ways of distributing source code is impacting the techniques in bundling the library.

We need a dedicate PR which fixes our current pattern(s):

  • Browser bundle

This bundle is our own compiled source code which can be dropped into a page though a <script> tag. This should support natively support a list of browsers (so it can bundle the necessary polyfills)

  • Module system

Expose raw source code which can be consumed by an application with a module system (e.g. Webpack). Host application can optimize the browser bundle. This should state the minimum requirements for code transformation (e.g. ES6 -> ES5, polyfills).

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Development

No branches or pull requests

1 participant