Hi, Right now, while using lazy loading, I load all my providers in app.module.ts which I guess isn’t maybe the best strategy because this won’t speed up my app boot time, specially because I’ve got something like 50 custom providers (don’t judge me :wink: ). Therefore I’m asking my self if I shou…

No, just a little further down there’s this. https://angular.io/guide/ngmodule-faq#should-i-add-other-providers-to-a-module-or-a-component I see two issues: (1) code design: The programmer needs to clearly decide which providers are universal, and which providers are only used by a particular con…

I don’t have an answer for you, but I thought you might like to know that I’m struggling with exactly the same decisions. I have some providers that only inject into exactly one place – often another provider, which I broke into sub-providers to modularize code. And I’m not sure what the best way to…

Thx feel a bit less alone :wink: I’m guessing not loading all these providers would really improve my boot time but I’ve really no idea if it’s possible to share a provider between only a selected list of modules, which would be a must in my case, but I’ve got really no idea if it’s possible and if…

Forwarded my question to stackoverflow too: [David Dal Busco] Lazy loading and providers strategy angular, ionic-framework, angular-module, angular-providers asked by David Dal Busco on 11:33AM - 12 Oct 17

@AaronSterling don’t know if you would be agree with me but I just read the angular documentation and I have the feeling that this is a design restriction respectively angular is designed to load all providers at boot time without any other pattern. Do you understand this the same way as I do? http…

Thx for pointing that out, don’t know why but I’m really confuse about this subject…I should do more test locally to see what works and what doesn’t work with my app Anyway, reading the documentation you pointed out, I found the following super duper important to understand, thx a lot Then each n…

Hi, If you are using lazy loading module for your pages (A, B, C), then just add your provider name under providers:[] property in @NgModule of each pages. B.module.ts import { Provider2 } from '../provider2'; @NgModule({ ... providers: [ Provider2 ] }) export class B {} C.module.ts i…

I did forget about this thread So I gonna close it and mark the answer of @AaronSterling as the correct one If I understand correctly a. You use stateless providers, then yes you might be able to declare them in separate modules because if you do so, each modules gonna use is own provider (“no me…

@Tommertom If your app is quite small then yes it is easy to code without following any design patterns, there’s a low chance of getting confused and you don’t need lazy loading. Services provided in components can still share their state with any child components, that’s why angular best practices…

[image] rlouie: angular best practices state you should provide services from the top-most component from where they will be shared this sentence sounds like a good summary to keep in mind to me, thx

Lazy loading and providers

Ionic Framework ionic-v3

Tommertom March 13, 2018, 10:43am 9

See Learn Multiple File Upload by building an Instragram-style app

and @rlouie view on local declaration of providers.

Some say Ionic Apps are so small, you only want to declare in module.

Regards

Tom

Topic		Replies	Views
Lazy loading - Providers and modules ionic-v3	9	2337	August 31, 2018
Best way to check if a user is logged while the app is loading? ionic-v3	7	7716	September 15, 2017
Injectables are a singleton only per IonicPage and not for the whole app ionic-v3	11	3414	July 13, 2017
Ionic 3's lazy loading is bad for large apps it's being worked on! ionic-v3	23	13955	November 7, 2017
Modals annd tabs create new instances for services ionic-v3	6	890	May 12, 2018

Lazy loading and providers

Related topics