No, you can design Grunt tasks that are very similar to Gulp tasks. It's not going to throw a wrench in the works too much. You wont get it for free - you will have to write some of the tasks yourself - but generally speaking as long as you try to avoid maintenance ( adding new features/tasks etc ), on it, its a one-off.
On Wed, Sep 9, 2015 at 6:24 PM, Pedro Fernando Marquez Soto < [email protected]> wrote: > Reading about the features on Angular 2.0, I got to the part about Angular > ditching Grunt and using GulpJS instead > <http://ng-learn.org/2014/03/AngularJS-2-Status-Preview/#where_is_grunt>.What > exactly does this mean for Grunt based projects? > > I recently started a new project which uses Grunt, and Angular 1.3 is my > main technology there. I want to prepare for a future migration to Angular > 2.0 and I want to know if it will force me to migrate from Grunt to GulpJS. > > Does this change break my existing Grunt project? > > -- > You received this message because you are subscribed to the Google Groups > "AngularJS" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at http://groups.google.com/group/angular. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "AngularJS" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at http://groups.google.com/group/angular. For more options, visit https://groups.google.com/d/optout.
