Angular.js: Routes should allow to load modules/controllers on demand
When you route to a specific location, the template for that route is loaded on demand. There should also be a feature to specify a module or controller script that will be loaded when the user routes to the given location.
There is a solution using require.js (https://github.com/matys84pl/angularjs-requirejs-lazy-controllers), but it adds another library and another nesting level (angular module definitions within require.js module definitions)
As for the use case:
- Increase the initial startup time by loading scripts only when they are needed.
- Only serve scripts to users that have the right to see the route they are used in.
- Enhanced modularity.
zilluss
All 23 comments
+1
bkuhl
on 17 Apr 2013
+1
moisesbaddini
on 21 Jul 2013
+1
santyclaz
on 16 Aug 2013
+1
zaver
on 20 Aug 2013
+1
missinglink
on 28 Aug 2013
+1, but even the ability to lazy load modules at all would be nice.
spalger
on 4 Sep 2013
+1
felixdulfer
on 7 Sep 2013
I have made a very small change to angular that allows modules to load after bootstrap, which is more general than the lazy load controller approach at https://github.com/matys84pl/angularjs-requirejs-lazy-controllers.
Put these lines in createInjector(), just before the return statement (tested this on 1.2.0-rc.2):
instanceInjector.loadNewModules = function (mods) {
forEach(loadModules(mods), function(fn) { instanceInjector.invoke(fn || noop); });
};
Then, after the module source is loaded dynamically (i use requireJS for now) just call $injector.loadNewModules(['nameOfModuleJustLoaded']), and all the components get registered nicely with angular (well the few things i've tested so far seem to work perfectly).
I'll try to make a PR out of this one day, when i get a spare moment...
:+1:
cleyshan
on 9 Oct 2013
This (or just lazy loading at all indeed) is absolutely vital for single-page apps.
dgieselaar
on 30 Oct 2013
+1
I applied this workaround and solved my problem http://ify.io/lazy-loading-in-angularjs/ . Hope this help.
Cosmitar
on 25 Feb 2014
+1, with the ability to do another config for the loaded module and register new routes.
mokkabonna
on 25 Feb 2014
+1
renato
on 28 Feb 2014
+1
juji
on 25 Mar 2014
+1
BaggersIO
on 18 Jun 2014
:heart: google,this function is basic and obvious
hyper315
on 18 Aug 2014
+1
stefanomozart
on 31 Jul 2015
+1
senthanal
on 27 Sep 2015
+1
paul-ntech
on 15 Oct 2015
+1
napstercake
on 1 Dec 2015
+1
vldmri
on 3 Oct 2016
it's 2016. something should have been done..
:)
May the awesomeness will always be with you,
Tri Rahmat Gunadi - JUJI
http://jujiyangasli.com
Ph 0813.1012.8924
On Mon, Oct 3, 2016 at 7:02 PM, pyotruk [email protected] wrote:
+1
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
https://github.com/angular/angular.js/issues/2135#issuecomment-251088850,
or mute the thread
https://github.com/notifications/unsubscribe-auth/AAeH8RayUZA4MUmqWPnUIyb5S6Rsg5PRks5qwO64gaJpZM4AfSRI
.
juji
on 7 Oct 2016
The de-facto solution appears to be to use a 3rd party https://oclazyload.readme.io which appears to solve the problem in a generic way.
jamie-pate
on 12 Apr 2017
In 1.6.7, it will be possible to load new modules into the injector after the app has been initialized, e.g. in a route's resolve function. You'll still have to provide a way to load and execute the script though. See https://github.com/angular/angular.js/commit/34237f929927295392bbb1a600e78cbde581839a for more info
Narretz
on 27 Sep 2017
Related issues
nosideeffects
·
3Comments
gkalpak
·
3Comments
jetta20162
·
3Comments
kishanmundha
·
3Comments
brijesh1ec
·
3Comments
Most helpful comment
In 1.6.7, it will be possible to load new modules into the injector after the app has been initialized, e.g. in a route's resolve function. You'll still have to provide a way to load and execute the script though. See https://github.com/angular/angular.js/commit/34237f929927295392bbb1a600e78cbde581839a for more info