Load a module immediately when the app starts

[Robert Gomez]

Hi,

I have an AuthModule with my components, imports, exports, routing, etc....

I would like to load it immediately when the app starts to have all its routing available since the beggining, in other words, I don't want to load this module lazily.

I have found that if I keep this module imported in the imports of the app.module.ts, all routes of my AuthModule are working as expected.

The question is:

1. This is the correct approach?
2. Should I use a custom PreloadingStrategy that is mentioned in a lot of blogs out there? (and why)

Both ways works, but, what's the difference? what is the correct way to do this?

[bastien lemaire]

Hey Robert, this is the right approach but that means the routes defined in authModule will not be nested within routes defined in AppModule

[Sander Elias]

Hi Robbert,

Then don't load is lazy, just use it as a normal module.

Regards

Sander

[Robert Gomez]

On Tuesday, April 7, 2020 at 5:15:44 AM UTC-4, bastien lemaire wrote:

Hey Robert, this is the right approach but that means the routes defined in authModule will not be nested within routes defined in AppModule

Hi, thanks for answering me back. Do you think that will have an impact on performance or something? Should my AuthModule routes be nested within routes defined in app.routing? 

[Sander Elias]

Hi Robert,

Your initial payload will be bigger, but all things auth will load from the get-go without slowdown. So it is up to you what you prefer.

Regards

Sander