nice to have: grunt-bower-task about generator-ionic HOT 3 CLOSED

bower-install is already in there.. see Gruntfile.js ---- @diegonetto is right..
https://github.com/diegonetto/generator-ionic/blob/master/templates/common/Gruntfile.js#L138

from generator-ionic.

The grunt bower-install task doesn't actually run bower install. It injects dependencies managed by bower into your index.html files so you don't have to. Here's the plugin - https://github.com/stephenplusplus/grunt-bower-install

There are two schools of thought when it comes to managing the bower_components and node_modules directories. There are arguments that support both excluding them from version control and having the final build system pull them in, or packaging them with your repository.

This issue got more coverage when the NPM registry went down for a bit last year, causing many build systems to hang. Here's a great post by @addyosmani on checking in front end dependencies.

For now, I think we should leave it up to the user's discretion. Tapping into githooks and having it run npm install && bower install on the post-merge hook would probably be the way I'd handle it.

from generator-ionic.

Thank you for the detailed response! That's exactly the dilemma I was confronted to. But I understand your decision.

Githooks are outside the build-process and everyone has to configure it on his own... I am currently aiming at simplifying the build process, so that the other programmers can easily build and run an app and its server. So it is not an alternative for my current issue.

from generator-ionic.