They are roughly the same, with a few differences:
angular.bootstrap(document, ['TodoApp']);
This will work if you have your scripts loaded at the end of the page (instead of in the header).
Otherwise, the DOM will not be loaded at the time of bootrsaping the app (there won't be any template to be compiled, the directives won't have any effect).
This one works: plnkr
This one doesn't: plnkr
angular.bootstrap(angular.element("body")[0], ['TodoApp']);
The same as before, using body
as the root of the application. It uses a selector that is not available in jqLite, so you need to have full jQuery included in the app.
I'm not sure what is the advantage of using body
instead document
, but probably has something to do with e2e testing, as explained in this comment
plknr
angular.element(document).ready(function() {
angular.bootstrap(document);
});
This one actually waits for the DOM to be loaded, so it will work even if you include your scripts in the header.
This is basically the same as jQuery's $(document).ready(
, but using jqLite
's angular.element
.
In the last example, no modules are being passed to the bootstrap function, most likely you will need to declare your main module, unless your app consists only on controllers in the global namespace.
So the last option will be like the following, in order to be similar to the other two:
angular.element(document).ready(function() {
angular.bootstrap(document, ['TodoApp']);
});
plknr
I guess that most of the time the safest bet is using this last approach.
If you love us? You can donate to us via Paypal or buy me a coffee so we can maintain and grow! Thank you!
Donate Us With