You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
+1 here too, would love to be able to do this. working on a huge project with potentially dozens (hundreds?) of modules that may or may not ever be loaded, the decision is made at runtime. having them packaged as npm dependencies helps with the development process.
I'm not sure if its supposed to do it this way, but in my testing i'm setup with a nested lazy loading setup that has app -> admin -> content as the module tree, including a 3rd party module into the content module, this bundles the 3rd party module with my content module, so this could be a work around for this approach.
@Destreyf Yep, I did this in the same way, but what's about singleton services for a module ? As I understand when we provide a feature module from package the angular creates new instances of module. Am I right ?
@micronyks, I researched the topic quite a lot (dozen of similar issues out there - unresolved) and it seems like this issue just receives no love :(
I really depend on this right now, and it's making me rethink the whole ecosystem.
Currently, the only way around this is really wrapping a module, but this is of course extremely bad.
First of all thanks for the update @klemenoslaj . Even I feel like that I am stuck after developing so many libraries and I don't want to go with a wrapper module approach. @filipesilva : Guys do you have any update on this issue?
This issue is probably making people insane. Please provide a way or at least update in which release we should expect the resolution?
Reacted by Siddharth Ganesh, Thruba, Jim Barrett, Jan Silbersiepe, wiikka, Jose Berrocal, Nikhil Shah, Jalal EL-SHAER, İlker ERHALIM and Nadav Sinai
Any Update?
When should we expect this feature?
Some information will really be helpful.
Reacted by Klemen Oslaj, Collin Dutter, Fabio Nolasco, ajorda3, Aitor, Lars Saalbach, İlker ERHALIM, Vinicius Dantas e Melo, Anirudh-Konduri, Andreas Burø and 5 more
Activity
filipesilva commentedon Oct 10, 2016
This is a very relevant question. I don't think we support it in the CLI atm.
AshMcConnell commentedon Oct 17, 2016
+1 for lazy loading from a package
lorenjerickson commentedon Oct 26, 2016
+1 here too, would love to be able to do this. working on a huge project with potentially dozens (hundreds?) of modules that may or may not ever be loaded, the decision is made at runtime. having them packaged as npm dependencies helps with the development process.
tsluijter commentedon Nov 9, 2016
+1 for lazy loading from a package too
odannyboy000 commentedon Nov 10, 2016
+1 for lazy loading from a package
sclausen commentedon Nov 12, 2016
+1
Destreyf commentedon Nov 14, 2016
I'm not sure if its supposed to do it this way, but in my testing i'm setup with a nested lazy loading setup that has app -> admin -> content as the module tree, including a 3rd party module into the content module, this bundles the 3rd party module with my content module, so this could be a work around for this approach.
sclausen commentedon Nov 14, 2016
@Destreyf that sounds great. Could you be more specific on how you actually did it? For example provide a plunkr? That would be awesome.
waltherp commentedon Feb 17, 2017
+1
captainkovalsky commentedon Apr 5, 2017
@Destreyf Yep, I did this in the same way, but what's about singleton services for a module ? As I understand when we provide a feature module from package the angular creates new instances of module. Am I right ?
29 remaining items
klemenoslaj commentedon Aug 1, 2018
Issue is probably related to #6373 as well.
micronyks commentedon Aug 3, 2018
is there any update for this issue?
I have also plenty of angular libraries which I use as packages and I want to lazy load them?
I don't want to have a wrapper module which imports requires module from
node_modulesfolder and then wrapper module can be lazy loaded.is it resolved in other referenced links?
Will any one provide any update on this issue?
klemenoslaj commentedon Aug 3, 2018
@micronyks, I researched the topic quite a lot (dozen of similar issues out there - unresolved) and it seems like this issue just receives no love :(
I really depend on this right now, and it's making me rethink the whole ecosystem.
Currently, the only way around this is really wrapping a module, but this is of course extremely bad.
micronyks commentedon Aug 3, 2018
First of all thanks for the update @klemenoslaj . Even I feel like that I am stuck after developing so many libraries and I don't want to go with a wrapper module approach.
@filipesilva : Guys do you have any update on this issue?
This issue is probably making people insane. Please provide a way or at least update in which release we should expect the resolution?
wiikka commentedon Aug 13, 2018
+1
micronyks commentedon Aug 21, 2018
Any Update?
When should we expect this feature?
Some information will really be helpful.
Bhargavi-Kotagaram commentedon Oct 15, 2018
Hi,
Me too got stuck with same issue, any update on this?
Thanks,
alan-agius4 commentedon Nov 4, 2018
Duplicate of #6373
bionara commentedon Nov 16, 2018
Any updates on this issue?
deepthan commentedon Nov 19, 2018
this work for me, you can try it #6373
angular-automatic-lock-bot commentedon Sep 8, 2019
This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.
Read more about our automatic conversation locking policy.
This action has been performed automatically by a bot.