Angular-cli: Ng 8.0 + ivy + library Error : does not have 'ngModuleDef' property

Created on 30 May 2019 · 8Comments · Source: angular/angular-cli

🐞 bug report

Is this a regression?

Description

this is a simple test ng 8.0 + ivy + library. is it ivy supported custom library ?
this is the error message i get :
Error: Type MyLibModule does not have 'ngModuleDef' property.
if i turn off ivy, all work fine

🔬 Minimal Reproduction

https://github.com/keatkeat87/angular-ivy-library-issue

step :
ng new library-and-project-issue --enable-ivy
cd library-and-project-issue
ng g library my-lib
ng build my-lib

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
import { MyLibModule } from 'my-lib'; // add

@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    AppRoutingModule,
    MyLibModule  // add
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

ng serve --open

Angular Version:
Angular CLI: 8.0.0
Node: 12.3.1
OS: win32 x64
Angular:
...

Package Version

@angular-devkit/architect 0.800.0
@angular-devkit/core 8.0.0
@angular-devkit/schematics 8.0.0
@schematics/angular 8.0.0
@schematics/update 0.800.0
rxjs 6.4.0

ngtoolwebpack feature

Source

keatkeat87

👍3

Most helpful comment

Hi @keatkeat87, yes this is something in the roadmap to add ngcc processing on workspace libraries. We are targeting this for 8.1

Thanks

alan-agius4 on 31 May 2019

👍6

All 8 comments

Libraries outside of node_modules that are made available using paths-mapping are not currently processed by ngcc, so they are not compiled for Ivy usage. For the time being you can run ./node_modules/.bin/ivy-ngcc -s ./dist each time after building the library and before serving.