How to locate missing $injector error? - angularjs

Question

I'm porting some core angular stuff to a new project. Now I get injector errors but the stacktrace / angular error page does not show the classname of the offending injection errors. All I get is
Error: $injector:modulerr
Module Error
Usually there is a class name in there somewhere. Now I have to go through every single class (of dozens and dozens) and check the imports manually. Isn't there a better way? I've seen this happening while just adding classes. Sometimes it will show the name of the missing injection, sometimes it just comes up blank, when otherwise the stacktrace correctly identifies the missing/bad injection.
Is there some extra debug mode I can get at this information with?
The full (unuseful) stacktrace:
Failed to instantiate module FSApp due to:
Error: [$injector:modulerr] http://errors.angularjs.org/1.2.16/$injector/modulerr?p0=FSApp&p1=Error…cape%2Fmain%2Fresources%2Flib%2Fangular-1.2.16%2Fangular.min.js%3A32%3A445)
at Error (native)
at http://fs/main/resources/lib/angular-1.2.16/angular.min.js:6:450
at http://fs/main/resources/lib/angular-1.2.16/angular.min.js:33:332
at Array.forEach (native)
at q (http://fs/main/resources/lib/angular-1.2.16/angular.min.js:7:280)
at e (http://fs/main/resources/lib/angular-1.2.16/angular.min.js:32:445)
at http://fs/main/resources/lib/angular-1.2.16/angular.min.js:33:18
at Array.forEach (native)
at q (http://fs/main/resources/lib/angular-1.2.16/angular.min.js:7:280)
at e (http://fs/main/resources/lib/angular-1.2.16/angular.min.js:32:445
If you want to try to reproduce this, commit your changes. Delete a couple files here and there. Run your angular app. IF you delete enough you will soon get blank injector errors.

Answer 1

A few tips and tricks:
A similar injector error answer applies here: set a break point on the angular error code and look at the call stack.
Also, occasionally click the link at the top of the stack trace takes to a page (without the class name), but where the page's error has another stack trace link. Click on that link and the second page may have the name of the missing object.
Also, if you haven't moved to annotated code (which can make it easier to spot injector errors)In angular 1.3 and greater, you can use the directive 'ng=strict-di' on whatever element has the ng-app directive, and that will cause the app to throw an error on any un-annotated module--and it will include the function along with the parameters ('function($scope, service, something)') which is hopefully unique enough to find quickly.