catull

@fabioformosa Ideally, you should not have to export components from `ngx-admin-lte` out of your `coreProject` in the first place. Rather, have services from `coreProject` offer your own components and services...

`ProjectA` indeed won't have to know about `ngx-admin-lte` and all its dependencies. My setup is a bit simpler, I have `myApp` -> `ngx-admin-lte`. For that to work, I have some...

What does `coreProject`'s main module provider: section look like ?

```typescript import { User, MenuService, LogoService, FooterService } from 'ngx-admin-lte'; @NgModule({ imports: [ CommonModule, RouterModule, NgxAdminLteModule ], declarations: [coreProjectComponent], exports: [ coreProjectComponent, User ], providers: [ MenuService, LogoService, FooterService ]...

Services and guards are **provided**, components are **exported**.

You can only go full Angular 6 if you do not have dependencies to `rxjs` prior to version 6. This is valid for direct or transitive dependencies. Check it with...

@TwanoO67 The effort is not so high. The question is though, how far back do you want to offer support. You cannot support both code bases in source code, Angular...

Interestingly, I never had to fiddle with the asset path configuration. Can be closed now.

Ah, I see. Never seen any runtime errors, because my web app does not have a need for translation or avatars. Kind of low-key, non-social bare bootstrap with menus and...

I build `sbcl` twice or three times a year locally. Currently using `clang` both as compiler and linker. May want to try out LLVM's `lld` in future. It'd be great...