Initial version - Githubissues

shawnlonas commented 8 years ago

The solution is to provide a command line tool that can:

create a "pseudo"-locked bower file that specifies every dependency to an exact commit as well as provides a "resolutions" entry to try to help enforce the desired version (if a conflict occurs)
- NOTE: "locked" bower file also contains version info for each dependency so it is easy to see all versions that are currently in use, as well as when the bower file was last "locked"
provide a way to easily return to the "unlocked" version
validate the components within bower_components with the versions as defined in the "locked" bower file
- This allows our build / deploy system to fail a build if the bower install results in bower_components that do not match the desired versions

shawnlonas commented 8 years ago

Thoughts @shaunnetherby / @joshuajohnson814 / @kevin-wise-infusionsoft / @wejrowski ?

kevin-wise commented 8 years ago

Overall, looks pretty solid, especially as a first take. Can't wait to use it! Thanks for taking the initiative @shawnlonas

MaKleSoft commented 8 years ago

There seem to be a couple of minor issues that would have been caught by our eslint rules. Why not start using it now?

shawnlonas commented 8 years ago

@MaKleSoft , sorry for the style / linting errors that you had to wade through. I will try to set it up and run it on this.

infusionsoft / bower-locker