I suggested commenting here, because I think we can do a bit more to improve interop with CommonJS. That said, yes, completely replacing the module system with something else is not likely to be doable for 1.x.
On Tue, Jan 20, 2015 at 4:23 PM, Ben Clinkinbeard < [email protected]> wrote: > What do you guys think? >> > > I think completely overhauling Angular's module system is a massive > undertaking far beyond the intended scope of this proposal. I don't > understand why the referenced GitHub issue is seen as intersecting with > this proposal. > > The modules are already being published to npm, which carries with it an > overwhelming expectation of CommonJS compatibility. Can't we meet that > baseline expectation before embarking on an epic effort to modify something > as fundamental as the Angular module system? > > -- > 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.
