Why is pho-devstack using the angular bower package over the NPM package?

[renestalder]

Shouldn't we use the angular NPM module to be able to require angular, angular-route and all other angular components via Browserify? Or what's exactly the deal that the default AngularJS setup in pho devstack uses bower to get angular?

I've read about the most people use the bower package instead of NPM for front-end components, but keeps open how I should implement Angular Addons in my code. Just plain script lines in my footer?

Seems I didn't get the principles of Browserify. Or pho devstack has chosen another way.

[PavelGavlik]

I would prefer to use npm instead of Bower. It plays well Browserify and it looks like community is starting to use npm also for front-end packages.

The reason why I've not already migrated away from Bower is #3. First builds become significantly slower when AngularJS is required and I don't want to have slow builds...

When #3 is done, I will migrate to npm entirelly.

[renestalder]

@PavelGavlik Thanks Pavel. I thought there may be more general reasons to use bower over NPM. But it answers my question for pho-devstack.