I have an larger editor.module which is required by two lazy loaded modules a.module and b.module. It like to move the editor away from app.module. Is it anyhow possible to define a third lazy loaded module editor.module as a lazy loaded dependency of a.module and b.module. Which ever is loaded first loads the editor module?
Asked
Active
Viewed 134 times
4
R. Richards
- 24,603
- 10
- 64
- 64
Manuel
- 9,112
- 13
- 70
- 110
-
Nice question, did you find a way around it? – Isidrok Oct 06 '17 at 07:57
-
I have nearly the same question. In my case, Angular automatically made `editor.module` a non-lazy-loaded module. My problem currently is, that (at least in dev mode) the providers of `editor.module` are instantiated twice. – bgerth Apr 13 '18 at 08:36