>
> it doesn't protect any core modules from being polluted (although to be
> fair, they could be polluted anyways).
>
I don't understand why this concern is connected to CommonJS usage. If it's
never been a problem before, why would it be a problem now?
convention for the ngMock / multiple modules exported
Just to provide a concrete proposal people can weigh in on, I (again?)
propose the following.
```
require('angular-mocks/ngMock')
require('angular-mocks/ngMockE2E')
require('angular-mocks/ngAnimateMock')
```
This would allow consistent use of `.name` when registering the modules.
--
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.
