-
Notifications
You must be signed in to change notification settings - Fork 2k
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
bower.json missing "main" and "moduleType" #525
Comments
@azakus ? |
Sorry for the delay on this. It turns out there's more to it than just simple concat/minification. Many/most components rely on an HTML Import of You can vulcanize everything with |
Thanks for the response, @robdodson. It's not clear to me how ES6 Loaders and HTML imports can work together. Somebody will figure it out, eventually. :) Still, it's now clear that a minified polymer.js would violate the bower spec. They recently updated it: https://github.com/bower/bower.json-spec#main (see second bullet, "Do not include minified files."). Feel free to close this issue if you want to defer resolution of this problem until there's a better understanding about how to consume polymer via bower. Thanks for your help! |
Any automated tools and/or build tools can't consume polymer without additional configuration work since polymer's bower.json is missing a "main" property. It is also missing a "moduleType" property, but that is arguably less important (but why not add it?).
I know there is a bit of contention about what "main" should point to, but most JavaScript packages that export a global script point it to a single un-minified file.
Since there is no un-minified file in this repo, the "main" property would point to the minified polymer.js, I guess? Unfortunately, this is nearly useless to us since folks would have to add additional manual configuration in order to bypass polymer when performing minification.
Is there any chance we could have the un-minified polymer.js included in this repo and point the "main" property at it?
Thanks guys!
The text was updated successfully, but these errors were encountered: