window.angular.module("foo") not understood. about ng-dependencies HOT 4 CLOSED

It probably is possible, but why do you actually do this?

Why not just drop the window.?

from ng-dependencies.

I was working with someone troubleshooting a problem they were having with dependencies. Turned out to be this window..

I asked the same question and they said visual studio doesn't like it when they do just angular.module... so they write window.angular.module.... I'll happily drop the window. for myself. Just looking to be a good contributor and add in the problem use case I found.

from ng-dependencies.

Adding support for window.angular.module would increase the processing time for everybody else who just use angular.module. That's because now we need to look for two patterns instead of one. My suggestion for your case is to wrap your angular code in IIFE, like so:

(function (angular) {
    angular.module(...)
    ...
})(window.angular);

from ng-dependencies.

I'm with @blai on this. Closing.

from ng-dependencies.