AOT Compilation Error when importing Secondary Entry Points

Type of Issue

[x ] Bug Report
[ ] Feature Request

Description

The following error is thrown when importing a secondary entry point in AOT mode.

ERROR in : Unexpected value ‘TestLabelModule in C:/Users/kkang/Sources/tester/tester/node_modules/@amat/theme/spinner/spinner.module.d.ts’ imported by the module ‘AppModule in C:/Users/kkang/Sources/tester/tester/src/app/app.module.ts’. Please add a @NgModule annotation.

How To Reproduce

1. Create a library with secondary entry point.
2. Import the component in another Angular project using the secondary entry point.
3. Build using Angular CLI with --prod or --aot flag.
4. Import the same component using the primary entry point, build will work without any errors.

I have created a testing repo which can be used to reproduce this issue: https://github.com/Karankang007/ng-packagr-testlib

import { TestLabelModule } from '@test/lib/label'; // Fails
import { TestLabelModule } from '@test/lib';          // Passes

Expected Behaviour

No compile or runtime errors in AOT mode.

Version Information

$ node_modules/.bin/ng-packagr --version
ng-packagr:            2.4.1
@angular/compiler:     5.2.9
@angular/compiler-cli: 5.2.9
rollup:                0.55.5
tsickle:               0.27.2
typescript:            2.5.3

[thomaspink]

We got a similar build like material (every component is its own module and a secondary entry point;) and moved now to a build using ng-packagr. This issue basically breaks the whole library when being used and build in a CLI project in AOT mode. Any updates on this issue?

[pieniazek]

@dherges Any updates on this? It’s currently a critical issue for us