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
include additional options in pub build? #15930
Comments
cc @johnmccutchan. |
FWIW - a temporary workaround for this is to define your own transformer that does this and add it to the transformer section of your pubspec.yaml file so it gets invoked after pub-build. |
Added Library-Polymer label. |
Removed Area-Polymer label. |
Removed Library-Polymer label. |
Added this to the Later milestone. |
Added Polymer-P-2 label. |
Removed this from the Later milestone. |
Removed Polymer-P-2 label. |
Removed Polymer-Milestone-Later label. |
This issue has been moved to dart-archive/polymer-dart#105. |
some options we've heard requested from users:
(a) allow to choose whether or not to include certain polyfills (e.g. if you intend to run only on a browser that has native support for shadow dom, for example)
(b) merge files together (e.g. single deploy target)
I'm not sure yet that the right solution is to make polymer transformers configurable this way. An alternative I like is to provide a separate package that optimizes your .html for deployment. For instance:
- removes dart.js
- it's configurable to remove stuff you don't need
- combines .js files together if possible (addresses (b))
- it can also inline images and .css
This might be related to issue #14537 as well
The text was updated successfully, but these errors were encountered: