Angular Dependency Injection and Lazy Loaded Modules

Let's explore the different ways of registering an Angular service with the dependency injection mechanism, in particular the peculiarities when it comes to lazy loaded Angular Modules.
Repo: github.com/jur...
Blog post: juristr.com/bl...

[@Kotfluegel]

This doesn't answer the question, of which lazy chunk ships the code for this service? I guess the service's code still ends up in the main chunk? Or does the DataServiceModule produce it's own lazy loaded module, which get's fetched as either Feature1 or Feature2 is being activated?

[@juristr]

Check the linked blog post in the description or play around with the provided code example. That should make it pretty evident 🙂

[@hsemog]

Great explanation! Although I would also like to hear your opinion on the pros and cons of example providedIn: DataAccessModule

[@juristr]

Might be a good occasion for another video. I'll note it down!

[@artempalamarchuk2605]

the main problem of this approach it is circular dependencies

[@hsemog]

@@artempalamarchuk2605 yes i know that, and that’s easily fixable with an empty dedicated module. Still I’m just curious if that offers any benefit regarding DI.

[@artempalamarchuk2605]

@@hsemog as for me better to use just simple 'providers' instead syntax (tree-shaking not so necessary in many cases) rather than create additional module just for import/export