-
-
Notifications
You must be signed in to change notification settings - Fork 55
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
Switch all component build to rollup #162
Comments
I like the idea of this. Is this one file overall per component or one file per format? (i.e. one for AMD, one for CommonJS, one for system) |
it will be one file overall per module type (amd, commonjs ...) , like what we did with core. |
Alright, I think this will be fine then. We should have the packages and core synced up anyways as far as the build method. |
@bigopon This can be closed right? |
Yes, Rollup, while gives a lot of benefits related to distribution, limits the consumption of a component library that distributes custom element (ex: CSS autoprefixing). |
With #147 in place, and incoming new way to register global resources via aurelia/framework#858 , it's now possible to distribute every ux package in a single file., and it's more desirable to to do, for build pref, runtime startup perf, size reasons.
Rollup is a good bundler for this, and it will also make the build setup very simple.
Thoughts ? @ZHollingshead @EisenbergEffect
The text was updated successfully, but these errors were encountered: