Closed ankon closed 8 years ago
@ankon It's because we don't want to be in the bower registry. See https://github.com/Polymer/polymer/issues/1245#issuecomment-79179300
Thank you, that makes a lot of sense.
https://blog.polymer-project.org/announcements/2016/02/16/2016-roadmap/ ... Goals:
Accelerate Polymer + Community engagement Tighten the core Polymer team and community feedback loop - better evolve Polymer as the community evolves Publish all elements to npm and bower ...
@marcus7777 We cannot simply flip private: false
on all our repos - some names have already been taken (e.g. http://bower.io/search/?q=paper-ripple). We are looking into how to publish to bower, but we need to find another way. (If it was this easy, we would have done it already.)
why not simply flip private: false on all your repos it a step?
@marcus7777 Because then people (not us) could publish some, but not all of the repos to bower, and it would be a fair assumption that paper-ripple
was also published and maintained by this team, but that assumption is incorrect. Since we don't have an answer that fixes all the elements, we can't just flip this boolean.
dropping it
thanks
I noticed this just now: why does
bower.json
actually specifyprivate
?