AngularJS fail to load module

Question

AngularJS fail to load module

EDIT: This only happens with IE (tested on IE10)

I have a app that loads fine initially, however, when refreshed it gives this error:

SCRIPT5022: No module: myAppModule

myAppModule is an angular module defined in app.js which is loaded after loading angular.js

angular.module('myAppModule', []);

and is auto-bootstrapped via:

<html ng-app="myAppModule">

The scripts are loaded as follows (no AMD loader):

<script>window.jQuery ||
    document.write('<script src="js/vendor/jquery-1.8.0.min.js"></script>')</script>
<script>window.angular ||
    document.write('<script src="js/vendor/angular-1.0.2.min.js"></script>')</script>

<script src="js/app.js"></script>
<script src="js/controller.js"></script>

I reckon that angularjs is getting loaded first and auto-bootstrapping the application, but app.js has not been loaded yet

javascript
html5
angularjs

Answer 1

Ok I don't know why auto-bootstrapping is failing, but if I manually bootstrap the application it works fine.

e.g.

<html>

...

<script src="js/app.js"></script>
<script src="js/controller.js"></script>
<script>angular.bootstrap(document, ['myAppModule']);</script>

Answer 2

I felt like and idiot when I found what I was doing wrong, but in case you're like me, then here are some other things to check first:

Make sure the child module is loading first. In my case, I had to make sure that the child module was physically before my parent module. You can confirm this by putting a breakpoint on each module init line.
Even with correct physical order, the execute order was still off. One of my modules was wrapped in a self-executing function, and the other was not. Doh.
There was an error in the child function which actually caused this error to show twice in the console. This is because I use a syntax like this:
```
var mod = angular.module("blah", []);
mod.filter("filterName", function(){ ... }); 
```
At one point I forgot the empty brackets when starting the module, so the line looked like this and threw this error:
```
var mod = angular.module("blah");  // <-- wrong
```

To recap, make sure the child module executes first and has no errors.

Answer 3

I had this very same problem, only in IE9. Lower versions of IE actually worked fine, as did newer browsers.

Manually bootstrapping solved the problem, but threw an error "Unknown Provider" for a filter that is part of my module. Note that the filter still seemed to be functioning as expected.

In the end, the solution that solved my problem and ceased the errors from being thrown at all was to simply rename the module file to be the same as the module.

So if the name of my module was myAppModule then the filename should be myAppModule.js and not my_app_module.js.

Answer 4

By the way, using Angular 1.0.6, loading jQuery before angular (hardcoded script tags) causes IE10 to throw 'no Module' error.

The only option I could find to correct it is to manually bootstrap and ensure my app.js that defines the module was loaded after all other child module references (like Barnabas mentioned).