-
Notifications
You must be signed in to change notification settings - Fork 11.9k
Description
Bug Report or Feature Request (mark with an x)
- [x] bug report -> please search issues before submitting
- [x] feature request
Area
- [x] CLI V6
Versions
node v9.7.1
npm v6.1.0
macOS High Sierra
Angular CLI: 6.0.7
Node: 9.7.1
OS: darwin x64
Angular:
...
Package Version
------------------------------------------------------
@angular-devkit/architect 0.6.7
@angular-devkit/core 0.6.7
@angular-devkit/schematics 0.6.7
@schematics/angular 0.6.7
@schematics/update 0.6.7
rxjs 6.2.0
typescript 2.7.2
Repro steps
after I upgrade my cli project to CLI v6 in order to use multiple projects I created another project
and I try to share code from my first project: root/src/app/ and use it in the new project: root/projects/my-second-app
Projects structure
├── projects
│ ├── my-second-app
│ └── my-second-app-e2e
├── src
│ ├── app
I just import module and use one of the components in the second app.
serve my second project work for me but when I execute ng build my-second-app --prod --aot
I get this error:
ERROR in : Cannot determine the module for class XXXComponent in /Users/.../xxx.component.ts! Add xxxComponent to the NgModule to fix it.
this is strange since this module is of the first project and it not part of the module I'm using in the second project.
in case I'm execute ng build my-second-app without the flags: --prod --aot it work
I'm not sure if sharing module like I did is the best practice and if not what is the best practice to share code like module, services etc when I have multiple projects.
The log given by the failure
ERROR in : Cannot determine the module for class XXXComponent in /Users/.../xxx.component.ts! Add xxxComponent to the NgModule to fix it.
Desired functionality
Option 1: ng build my-second-app --prod --aot should pass like ng build my-second-app
Option 2: in case the way I try to share code is not the correct way please suggest another way?