I'm just starting to evaluate integration with RequireJS and I'm concerned the benefits may not outweigh the cost. I want to speak in as general terms as possible here, because that's what I haven't (to my satisfaction at least) been able to scrounge from the interwebs.
Integrating Require seems like it would have *major* negative consequences on complexity and testability. Can i still create angular modules by composition of submodules? (All the examples I've seen just have a single *main* module.) And how do I unit-test all this stuff when its wrapped in define()? Like i said i'm just getting started researching, but I'm leaning very heavily against using require in my case. I especially don't want to redo build configs, tests, and all that jazz. Am i overestimating the negative impacts here? Thanks. On Saturday, June 29, 2013 6:40:49 PM UTC-5, David Driscoll wrote: > > I was watching the meetup video on Angular 1.2 and beyond, and at around > 55:00, the question is asked about angularjs and requirejs. Misko and Brad > drop a bomb that RequireJS is going to replace angular.module, are there > any more details about how this integration will work? > > > http://www.youtube.com/watch?v=W13qDdJDHp8&feature=player_detailpage#t=3301s > > -- 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/groups/opt_out.
