2 goals I want to accomplish:
2 - Find the least resistant path to do #1 - it doesn’t have to be “perfect”, at this point just good enough will do. Once I have a path, I feel confident I can go off and do the necessary tweaking on the tooling. I just want 1 or 2 baseline recommendations on dependency management and tooling to try.
Here is what I see so far as a potential front-end only “tool” or “build” pack:
npm package manager - Common JS Modules, Explicit Dependency Injection; ensures dependencies play nicely together; source: http://stackoverflow.com/questions/18641899/what-is-the-difference-between-bower-and-npm
gulp - Task runner that lets you automate repetitive tasks (sass compilation, running of unit tests, browser refresh) source: http://brandonclapp.com/what-is-gulp-js-and-why-use-it/
webpack - module bundler that generates static assets; split application into multiple chunks and load those chunks on demand…sources: https://web-design-weekly.com/2014/09/24/diving-webpack/ + https://www.quora.com/What-is-webpack
There is apparently some overlap between gulp + webpack, but I think npm and gulp (and adding webpack as needed) is a good start unless I am missing something.