A Yeoman generated Angular app works fine til I add ['ngResource'] and then it hangs

angularjs, yeoman

Solution

Got the answer (or at least the understanding) from Green & Seshadri's AngularJS book.

The angular.module statement works in two modes: configuration and run. The 'ngResource' statement works fine with configuration:

angular.module('a3App', ['ngResource']).config(function ($routeProvider) {
  $routeProvider
    .when('/', {
     templateUrl: 'views/main.html',
     controller: 'MainCtrl'
   })
   .otherwise({
     redirectTo: '/'
   });
});

Works

but put that same statement in an angular.module(...).factory statement and it fails/quietly hangs (because .factory is a run rather than configuration statement):

angular.module('a3App', ['ngResource']).factory('myService', function($resource) {
...

This is explained at location 6456 of the Kindle version of the AngularJS book ("Loading and Dependencies" in Chapter 7). It makes sense after the fact (I guess all things do)..but an error message and/or updated documentation would be great.

Problem

I created an AngularJS app with "yo angular", ran "grunt server --force" and got to the 'Allo, Allo' success screen. When I added ['ngResource'] as shown below it appears to hang...or at least nothing is displayed in the browser any more. We're tried adding $resource as a param to function..i.e. tried actually using a resource but no luck. I don't see any errors in the web console. We verified that angular-resource.js is listed in components/angular-resources. This feels like a dumb newbie error but its got us stuck. ``` 'use strict'; angular.module('a3App', ['ngResource']) .factory('myService', function () { var foo = 42; return { someMethod: function() { return foo; } }; }); ```

Original source