I didn't want to raise this on StackOverflow again, at least not without a more direct discussion.
I have been using this approach with some success, but, there seems to be some challenges when libraries have dependencies on other libraries. To try and narrow the problems down I started with a fresh workspace.
I've followed the steps, generating a new workspace, application, and two libraries (alpha and bravo). The bravo library imports the module declared in alpha, and the bravo component includes the alpha component (all based on the simple out-of-the-box generated samples from the latest Angular CLI).
In this scenario, whilst the live reload and development serve works just fine, I'm unable to ng build the second library (bravo), as it gets:
Unable to write a reference to MyLibAlphaComponent in /my-workspace/projects/my-lib-alpha/src/lib/my-lib-alpha.component.ts from /my-workspace/projects/my-lib-alpha/src/lib/my-lib-alpha.module.ts
Do you have any ideas for this scenario?
If I'm unable to get past this I'll follow the suggestions under angular/angular-cli#12000 (comment)
I didn't want to raise this on StackOverflow again, at least not without a more direct discussion.
I have been using this approach with some success, but, there seems to be some challenges when libraries have dependencies on other libraries. To try and narrow the problems down I started with a fresh workspace.
I've followed the steps, generating a new workspace, application, and two libraries (alpha and bravo). The bravo library imports the module declared in alpha, and the bravo component includes the alpha component (all based on the simple out-of-the-box generated samples from the latest Angular CLI).
In this scenario, whilst the live reload and development serve works just fine, I'm unable to ng build the second library (bravo), as it gets:
Do you have any ideas for this scenario?
If I'm unable to get past this I'll follow the suggestions under angular/angular-cli#12000 (comment)