Angular Application Architecture

Question

I have two modules one Core module,another Shared module.

Core module contains application wide singleton services and component which are loaded intially such as login,navbar.

Shared module contains reusable components,pipe and services.Also it import material module.

Now in core module we have login and navbar components which requires material module.And material module is imported in shared module.So I need to import shared module in core module. But according to Angular guideline we should not import shared module in core.

So how can I resolve this issue to avoid importing shared module in core module.

Brian Smith · Accepted Answer · 2021-06-27 16:05:30Z

1

Using a modular approach and lazy loading the modules. It is best to import into each feature module the necessary components/module needed for that feature.

For your case, in core module, you can just import the necessary material items needed to get your nav bar and login to work without the entire overhead of everything in the material module (or shared module) being loaded in core.

answered Jun 27, 2021 at 16:05

Brian Smith

1,6661 gold badge18 silver badges36 bronze badges

Sign up to request clarification or add additional context in comments.

1 Comment

abhishek modgi Over a year ago

Thanks for your answer.That is best way to avoid shared module bieng imported in core

Collectives™ on Stack Overflow

Angular Application Architecture

1 Answer 1

1 Comment

Your Answer

Hot Network Questions

Collectives™ on Stack Overflow

1 Answer 1

1 Comment

Your Answer

Sign up or log in

Post as a guest

Related