I have a created a web component, let's call it a-1.html, this is the main 
web component that I would like to publish, but this component also depends 
on another component that I created, b-2.html, and b-2.html also depends on 
a third component that I created c-3.html.

I have followed Polymer's Create reusable elements 
<https://www.polymer-project.org/1.0/docs/start/reusableelements.html> guide 
in order to publish my element on GitHub, everything worked fine in terms 
of development (they were already developed), and I made the documentation, 
and I published on GitHub, but I'm facing 1 problem.

The guide deals as if you have a single component to be published, and it 
mentions that if there's any dependencies, I should place them, but what if 
my dependencies are still local dependencies? I can't put b-2.html and 
c-3.html in *bower.json*, because they are not yet online.

So later on, when I'm installing my element using *bower install 
<username>/element*, the element is not working because it's missing 
b-2.html and c-3.html, also the online demo (Github page using gp.sh) is 
not working.

For this situation, where should I place these files in order to have a 
complete working repo on GitHub, and also a working demo.

*Directory:*
bower_components
--- lots of compoenents
--- including b-2 and c-3 added manually by me
---- in order for the demo to working locally, but since they 
----- aren't in *bower.json*, this won't work eventually
bower.json
demo
---index.html
index.html
README.md
test
---basic-test.html
---index.html
a-1.html

THANKS!

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/e3a3051b-5ef9-499b-bd77-d56ac346fc22%40googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to