Finding the cause of "Unknown provider" errors

angularjs minify
Brett Postin picture Brett Postin · Mar 5, 2014 · Viewed 15.1k times · Source

I'm getting the following error:

Error: [$injector:unpr] Unknown provider: nProvider <- n

I know this is being caused by the minification process and I understand why. However is there an easy way to determine which file is actually causing the issue?

Answer

ansorensen picture ansorensen · Nov 19, 2014

Angular 1.3.x has an ng-strict-di directive that is placed on the same element as the ng-app directive. This element causes your app to throw an error whenever dependencies have not been annotated. While it still doesn't give you the line number of the offending code, it does give you the function with its parameters (i.e. function($scope, myServiceName)) which is hopefully unique enough that you can find it pretty quickly in a good code edit.

A good overview of the directive: ng-strict-di.

Related questions

Angular.module minification bug

Having the darnedest time trying to figure out why minification is not working. I have injected via an array object my providers prior the function per numerous suggestions across the web and yet still "Unknown provider: aProvider <- a" …

Read More
Rails 3 + angularjs + minification does not work in production: Unknown provider: eProvider

I've followed all the instructions I can find for fixing minification, e.g. var MyController = function(renamed$scope, renamedGreeter) { ... } MyController.$inject = ['$scope', 'greeter']; and someModule.factory('greeter', ['$window', function(renamed$window) { ...; }]); yet angular refuses to work still. It …

Read More
Unknown Provider e-provider error while using angularjs and ruby on rails

I have a Rails/AngularJS app which works fine in local development environment. However, when I deployed this app to Amazon Cloud the AngularJS returns this error in the browser console: Unknown provider: eProvider <- e However it works …

Read More