Cannot compile using Ivy: Failed to read entry point info -> ERROR in Failed to list lazy routes : app.module#AppModule routes: Unknown module

Description

I’ve enabled the ivy compiler flag and when I compile I get the following stream of error messages

WARNING in Failed to read entry point info from …/node_modules/npm/test/fixtures/config/package.json with error SyntaxError: Unexpected end of JSON input.

WARNING in Failed to read entry point info from …/node_modules/npm/test/fixtures/config/package.json with error SyntaxError: Unexpected end of JSON input.

ERROR in Failed to list lazy routes: Unknown module ‘…/src/app/app.module#AppModule’.

🔥 Exception or Error

ERROR in Failed to list lazy routes: Unknown module '../src/app/app.module#AppModule'.

🌍 Your Environment

Angular Version:

<!-@angular-devkit/build-optimizer   0.800.3
@angular-devkit/build-webpack     0.800.3
@angular-devkit/core              7.3.9
@angular-devkit/schematics        8.0.3
@angular/cdk                      8.0.1
@angular/cli                      8.0.3
@angular/pwa                      0.800.3
@ngtools/webpack                  8.0.3
@schematics/angular               8.0.3
@schematics/update                0.800.3
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.30.0- ✍️-->

[Splaktar]

@avatsaev this issue was closed as it didn’t include a reproduction. https://github.com/angular/angular/issues/32547 has been opened, with a reproduction, to track this issue going forward.

[bobskigit]

Its angular 8.1.0-next.3 of @angular/core.

Its a relatively large multi-language application around 100+ components, 50 or so services. It’s been migrated from 6 to 7 to 8 over the last year. There are around 20 modules all loaded lazily, with a single shared common module. If I turn IVY off it compiles perfectly.

I have removed all the lazy loaded modules and the error is exactly the same, we also use DevExtreme from Devexpress for a large number of the UI widgets.

Is it possible to run something to provide a better pinpoint for the errors?