Except, you may notice that I did not mention Bower. It seems to me that the NPM/Browserify workflow is starting to gain momentum, and Bower is losing popularity. That, and the fact that NPM is very well known (and is a prereq to using Bower anyways), has convinced me that NPM/Browserify is the way to go.
I am not particularly opposed to integrating with Bower, but I'm going to hold off on it until someone says otherwise - doing it cleanly can get a little bit weird. Angular, for instance, has an entirely separate repo that they use for their bower version. That's gross.
Title says it all...
Except, you may notice that I did not mention Bower. It seems to me that the NPM/Browserify workflow is starting to gain momentum, and Bower is losing popularity. That, and the fact that NPM is very well known (and is a prereq to using Bower anyways), has convinced me that NPM/Browserify is the way to go.
I am not particularly opposed to integrating with Bower, but I'm going to hold off on it until someone says otherwise - doing it cleanly can get a little bit weird. Angular, for instance, has an entirely separate repo that they use for their bower version. That's gross.
(This will be part of The Refactor.