In my projects I have experienced some problems (version conflicts) when using "polymer", since then I am using "Polymer/polymer". I am sure not everyone understands bower so deep to understand the implications, so I think it would be good to do it consistently.
On Tuesday, February 25, 2014 10:42:28 PM UTC+1, Rob Dodson wrote: > > I noticed there are some polymer packages registered in the bower registry. > > polymer (links to components/polymer) > polymer-platform > polymer-elements > polymer-ui-elements > polymer-polymer (links to Polymer/polymer) > > In the polymer docs, we sometimes tell people to install from a package > > $ bower install polymer > > and we sometimes tell them to install from the repo > > $ bower install Polymer/polymer-elements > > I'm wondering if there might be an incompatibility situation. > For example, if a component author adds polymer-polymer to their > bower.json file, then bower is going to create a folder called > "polymer-polymer" in the bower_components dir. If another author depends on > "polymer" then the bower_components dir will now contain directories for > both polymer and polymer-polymer. So you might end up with elements > importing the same libraries from different locations. > > I'm wondering if we should have one consistent way of doing (and > documenting) everything? > Follow Polymer on Google+: plus.google.com/107187849809354688692 --- You received this message because you are subscribed to the Google Groups "Polymer" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To view this discussion on the web visit https://groups.google.com/d/msgid/polymer-dev/1154107e-afb1-4a7f-85ca-f405fb1725d4%40googlegroups.com. For more options, visit https://groups.google.com/groups/opt_out.
