Open flash1293 opened 9 years ago
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.
I made such a script for my own project, you can get it here: https://github.com/flash1293/polymer-highlander
If someone knows a better way, I would be very interested.
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.
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.