-
Notifications
You must be signed in to change notification settings - Fork 34
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
Polymer 3.0 support? #37
Comments
Polymer 3 support should only require moving to ES Modules as far as I understand it. What can we do to get the move to ES Modules moving? |
I think we should try auto converter https://github.com/Polymer/polymer-modulizer It looks like paper elements maintain 2.0 source code and auto-generate 3.0. See https://github.com/PolymerElements/paper-button/ branch named 3.0 __auto_generated_3.0_preview . Though, I think it's good to wait official 3.0 launch (supposed to be very soon, my guess is upcoming Google IO in May) and follow their official guideline for maintaining elements for all 1.0, 2.0, and 3.0. |
This project doesn't use Polymer, except as a Bower dev dependency. The element itself is a vanilla HTMLElement. |
Oh I see, I didn't know that. Anyways, I tried polymer-modulizer and here is the result (the tool doesn't assume Polymer) https://gist.github.com/kkimdev/20ee9a5a9655bb4909454534beaf59f6 Seems very straightfoward other than we also need to handle ace-builds. |
This issue and this issue are accomplishing the same thing |
Closing in favor of #39 |
https://www.polymer-project.org/blog/2017-08-23-hands-on-30-preview
The text was updated successfully, but these errors were encountered: