Not compatible with Ivy (experimental)

[paullessing]

Issue description
When compiling with Ivy, the compilation fails with the following error:

ERROR in src/app/app.module.ts(8,12): error TS-991010: Value at position 1 in the NgModule.importss of AppModule is not a reference: [object Object]

Steps to reproduce and a minimal demo of the problem
I could not create a stackblitz or plunker for this as it is intending to show a compiler failure and I do not know how to demonstrate this.
You can check out https://github.com/paullessing/agm-ivy-demo and attempt to build after running yarn install.

1. Install new project of Angular 8 using ng new
2. Add @agm/core and set up the default import

   imports: [
     BrowserModule,
     AgmCoreModule.forRoot({
       apiKey: environment.mapsApiKey,
     })
   ]
   

3. Enable Ivy in tsconfig.app.json:

   {
     ...
     "angularCompilerOptions": {
        "enableIvy": true
     }
   }
   

4. Enable AOT in angular.json to work around "lazy routes not found":

   {
     "projects": {
       "my-project": {
         "architect": {
           "build": {
             "options": {
               ...
               "aot": true,
             }
           }
         }
       }
     }
   }
   

5. Run ng serve

Current behavior
Compile fails with error:

ERROR in src/app/app.module.ts(8,12): error TS-991010: Value at position 1 in the NgModule.importss of AppModule is not a reference: [object Object]

(Position 1 in the imports array is the AgmCoreModule.forRoot())

Expected/desired behavior
No compiler failures

angular2 & angular-google-maps version

"@agm/core": "1.0.0-beta.5",

Angular CLI: 8.0.1
Node: 10.16.0
OS: win32 x64
Angular: 8.0.0
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.1
@angular-devkit/build-angular     0.800.1
@angular-devkit/build-optimizer   0.800.1
@angular-devkit/build-webpack     0.800.1
@angular-devkit/core              8.0.1
@angular-devkit/schematics        8.0.1
@angular/cli                      8.0.1
@ngtools/webpack                  8.0.1
@schematics/angular               8.0.1
@schematics/update                0.800.1
rxjs                              6.4.0
typescript                        3.4.5
webpack                           4.30.0

Other information
Compile works when Ivy is disabled.

May be related to angular/angular#28603 which states that if the package.json does not contain a types or typings property, the module will be excluded from compilation.

Unable to reproduce. Could it be that importss has two 's'?

[paullessing]

Unable to reproduce. Could it be that importss has two 's'?

I think that's because it's an array with name imports so the error message is attempting to pluralise it.

I just tried again with a brand new project, and it still fails (with beta version 6). I updated the details above.

ok, try

ng new my-proj --enable-ivy
cd my-proj
npm install @agm/core

add AgmCoreModule.forRoot... to the imports

npm start

[paullessing]

That is literally exactly what I did in the demo project I linked in the description above.

[ramses10]

Same problem here.

@paullessing @ramses10 would you like to join Discord so we can discuss this more interactively?

[ramses10]

@doom777 fine for me

[drabadan]

reproduced with build:prod
@doom777 have you tried with prod flag?

[lakinducker]

I am having the exact same problem. My app is similar to the example that Paul has shared. I get the Value at position 1 in the NgModule.importss of AppModule is not a reference: [object Object] on both ng b --prod and ng b.

[aviaur]

Angular: 8.0.0
@agm/core: 1.0.0-beta.6

Hi, I have the same problem when Ivy is enabled :
ERROR in src/app/app.module.ts(37,12): error TS-991010: Value at position 16 in the NgModule.importss of AppModule is not a reference: [object Object]

Works when Ivy is disabled

[BobBDE]

By looking at the problem I found 2 related issue in angular and angular-cli package.

It seems that the error comes from a librairy that is outside of node_module and made available using path-mapping.

Check the following comment and issue : angular/angular-cli#14594 (comment)

And also this issue : angular/angular#30945

Unfortunately I couldn't make the librairy works with the technique describe in the comment (first link) using : ./node_modules/.bin/ivy-ngcc -s ./dist.

I don't really understand what's going on, but maybe that can help you.

hmm, perhaps after implementing #1648 it would work. I am not aware of any path-linked libraries in our lib, but we do use unusual packing