You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Dec 19, 2017. It is now read-only.
When I try to use components which are developed with the javascript-version of polymer along with my own components developed in dart-polymer, both (dart-polymer and js-polymer) try to register elements and collide.
For the polymer_elements dart-package this issue is circumvented by changing the html-import from js-polymer to dart-polymer. This can be done for example by a post-install-script in bower, but it would be much nicer if both polymers play along somehow.
The text was updated successfully, but these errors were encountered:
Unfortunately there is a fundamental design difference here between where bower and pub store package dependencies. We can leave the bug open since I agree its a pain point, but there is no acceptable solution that I know of yet...
A post-install bower script could overwrite all the bower files (for polymer and polymer_elements) to point into the packages folder I guess, but that seems really hacky.
oh also fwiw not sure why I never mentioned it but there is also the custom_element_apigen package which is what polymer_elements uses. It requires a fair bit of configuration though, and also requires node/npm.
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
When I try to use components which are developed with the javascript-version of polymer along with my own components developed in dart-polymer, both (dart-polymer and js-polymer) try to register elements and collide.
For the polymer_elements dart-package this issue is circumvented by changing the html-import from js-polymer to dart-polymer. This can be done for example by a post-install-script in bower, but it would be much nicer if both polymers play along somehow.
The text was updated successfully, but these errors were encountered: