3 ms·
Then the problem has nothing to do with AngularJS per se, but how you package and deliver a web app in general. You need to learn about asset management. Take
by lobo_tuerto 12y ago
Then the problem has nothing to do with AngularJS per se, but how you package and deliver a web app in general.
You need to learn about asset management. Take a look at webpack for example: http://webpack.github.io/ http://webpack.github.io/
In the video they explain the strat behind how they managed to make a big app load only the necessary parts. With that, and some researching on your part should be enough to get you on the right track.
In any case, your argument doesn't hold. It isn't only for small apps. ;)
- hippich 12y agoBelieve me, this is problem with AngularJS (mostly because they invented modules/dependencies and decided to stick with it despite obvious deficiencies instead of teaming up with other open source projects and using something like require.js Strategy is easy part, as this stuff done many times already. The devil is in details about how to actually get into guts of angular's dependency and routing systems.