thanks for the suggestion. I'll try that.
Am Donnerstag, 8. Februar 2018 16:58:48 UTC+1 schrieb Joern Turner:
> Maybe the following is obvious to anybody but me and maybe it's not even a
> pure Polymer issue but i'm lost with this problem and would appreciate help
> a lot.
> First of all:
> - working with Polymer 2 and bower
> - i've created a couple of components. Some of these are complete apps in
> themselves so they have a set of dependencies loaded in via bower. Each of
> these compoents live in their own git repo. For far so good. That's working
> - each of the apps will have a structure like this:
> -- bower_components
> - now i'd like to use these components and aggregate them in another app.
> So my take was to bower install them from their respective repo.
> And here's the actual problem. Lets say my new app 'my-app' loads
> 'my-comp1' from external git. 'my-comp1' will have e.g. a html import
> pointing to 'bower_compoents/paper-input/paper-input.html. This resolves
> just fine when i use my-comp1 directly.
> But when i bower install it it will land in the bower_components folder of
> 'my-app' and the pathes inside of 'my-comp1' will break as they don't
> resolve to 'my-app/bower_components/paper-input/paper-input.html' but to
> which is not there.
> I've searched the net for advice for hours both in the bower and the
> Polymer world but couldn't find an answer on how to organize a
> componentized project. Maybe i'm just overlooking the obvious but i'm
> really stuck on this.
> Any help is highly appreciated.
> Thanks Joern
Follow Polymer on Google+: plus.google.com/107187849809354688692
You received this message because you are subscribed to the Google Groups
To unsubscribe from this group and stop receiving emails from it, send an email
To view this discussion on the web visit
For more options, visit https://groups.google.com/d/optout.