CODEWITHSUNDEEP
javascriptangularjs
user677526
user677526

Reputation:

Are there any reasons NOT to use angular-loader?

I've worked with Angular for a little bit, but I keep managing to learn something new - today, I installed the angular-seed project in order to give my development a little kick in the pants. I ran into the index-async file and learned about the angular-loader - which I hadn't used before.

I found this question, as well: What is angular-loader.js for?

It looks as though the index-async file is using a script loader in addition to the angular module loader, which makes sense. However, I've never used this method before. (In my company, we've used RequireJS to load angular modules before, and so I can understand why something like this would be easier and less cumbersome.) Yet, it also seems that I could use the loader without a third-party script loader - I could just include all of my app files, in any order, before the loader is called, without having to worry about the dependencies.

In short - when should I use angular-loader? More importantly, is there any reason NOT to use it all the time?

Upvotes: 3

Views: 719

Answers (1)

Andy
Andy

Reputation: 5414

Well, you don't have to use it if you don't need it.

From the Angular Docs, you use it:

If you are loading multiple script files containing Angular modules, you can load them asynchronously and in any order as long as you load this file first. Often the contents of this file are copy&pasted into the index.html to avoid even the initial request to angular-loader.min.js. See angular-seed for an example of usage.

The reason behind is to optimize the loading time on the client-side - only load the currently needed module for the user, particularly if you have a reasonably huge app.

Upvotes: 1

Related Questions