Hello all, Consider the following stories:
As a developer contributing to patternfly, I don't want to work with multiple package installers and multiple install steps, so that I can contribute code with fewer steps and less complication. As an application developer consuming patternfly via npm, I don't want to have bower as a nested dependency when I install patternfly, so that I have a smaller install footprint. This is particularly important when I want to deploy to cloud environments like openshift, and/or in docker containers. Finally we can't forget the story: As an application developer consuming patternfly via bower, I want to keep using bower. As such I propose we consolidate our dependency management on npm/package.json for both patternfly-core and angular-patternfly. We would continue to maintain the bower.json file as we will continue to publish to bower, but bower will no longer be /required/ to either develop or consume patternfly. We could even consider generating the bower.json file from our package.json to eliminate the possibility of inconsistent dependency versions. Thoughts? Brian
_______________________________________________ Patternfly mailing list [email protected] https://www.redhat.com/mailman/listinfo/patternfly
