Ivy preview report: error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class #30972

kolkov · 2019-06-11T10:24:21Z

Hi! I try to build another compex project with Ivy and get an error:

ERROR in node_modules/ng6-breadcrumbs/lib/breadcrumbs.module.d.ts(1,22): error TS-996002: Appears in the NgModule.imports of AppModule,
 but could not be resolved to an NgModule class

All libs from NPM:
https://www.npmjs.com/package/ng6-breadcrumbs

Angular CLI: 8.0.0
Node: 11.14.0
OS: win32 x64
Angular: 8.1.0-next.1
... animations, common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router, service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.800.0
@angular-devkit/build-angular     0.800.0
@angular-devkit/build-optimizer   0.800.0
@angular-devkit/build-webpack     0.800.0
@angular-devkit/core              7.3.9
@angular-devkit/schematics        7.3.9
@angular/cli                      8.0.0
@angular/http                     7.2.13
@angular/pwa                      0.13.9
@ngtools/webpack                  8.0.0
@schematics/angular               7.3.9
@schematics/update                0.800.0
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.30.0

@NgModule({
  declarations: [
    AppComponent,
    LoginComponent,
    NotFoundComponent,
    PublicComponent,
    PrivateComponent,
    HomeComponent,
    SidebarComponent,
    MobileSidebarToggleDirective,
    MobileSidebarCloseDirective,
    SidebarToggleDirective,
    SidebarCloseDirective,
    CloseDirective
  ],
  imports: [
    BrowserModule,
    ReactiveFormsModule,
    NgxPaginationModule,
    BreadcrumbsModule,
    HttpClientModule,
    /*Ng4LoadingSpinnerModule.forRoot(),*/
    NgxUiLoaderModule.forRoot({delay: 1500, maxTime: 10000}),
    // NgxUiLoaderHttpModule.forRoot({ delay: 1500, maxTime: 10000 }), // for Http module only
    AppRoutingModule,
    ServiceWorkerModule.register('ngsw-worker.js', {enabled: environment.production})
  ],
  providers: [
    {provide: HTTP_INTERCEPTORS, useClass: RequestInterceptorService, multi: true}
  ],
  bootstrap: [AppComponent]
})
export class AppModule {
}

Whats wrong?

The text was updated successfully, but these errors were encountered:

JoostK · 2019-06-11T19:06:30Z

By the looks of it, ng6-breadcrumbs does not have its Angular metadata JSON file next to the root typings. Instead, the metadata files are hidden inside the package, next to each source file.

The relevant code in ngcc can be found here:

angular/packages/compiler-cli/ngcc/src/packages/entry_point.ts

Lines 91 to 101 in 83141fe

    
           const metadataPath = 
        
               AbsoluteFsPath.resolve(entryPointPath, typings.replace(/\.d\.ts$/, '') + '.metadata.json'); 
        
           const entryPointInfo: EntryPoint = { 
        
             name: entryPointPackageJson.name, 
        
             packageJson: entryPointPackageJson, 
        
             package: packagePath, 
        
             path: entryPointPath, 
        
             typings: AbsoluteFsPath.resolve(entryPointPath, typings), 
        
             compiledByAngular: fs.exists(metadataPath), 
        
           };

. Once we have config file support per #30591 it should become possible to re-wire the metadata file to one of the metadata files nested in the package.

kolkov · 2019-06-11T20:06:11Z

@JoostK Thanks! Waiting for fixes...

kunl · 2019-06-25T02:25:41Z

Angular CLI: 8.1.0-beta.3
Node: 12.4.0
OS: darwin x64
Angular: 8.1.0-next.3
... common, compiler, compiler-cli, core, forms
... language-service, platform-browser, platform-browser-dynamic
... router

Package Version

@angular-devkit/architect 0.801.0-beta.3
@angular-devkit/build-angular 0.801.0-beta.3
@angular-devkit/build-optimizer 0.801.0-beta.3
@angular-devkit/build-webpack 0.801.0-beta.3
@angular-devkit/core 8.1.0-beta.3
@angular-devkit/schematics 8.1.0-beta.3
@angular/cli 8.1.0-beta.3
@ngtools/webpack 8.1.0-beta.3
@schematics/angular 8.1.0-beta.3
@schematics/update 0.801.0-beta.3
rxjs 6.5.2
typescript 3.4.5
webpack 4.35.0


ERROR in ../node_modules/@angular/common/http/http.d.ts:2799:22 - error TS-996002: Appears in the NgModule.imports of ChatModule, but could not be resolved to an NgModule class

2799 export declare class HttpClientModule {
                          ~~~~~~~~~~~~~~~~
../node_modules/@angular/common/http/http.d.ts:2799:22 - error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class

2799 export declare class HttpClientModule {
                          ~~~~~~~~~~~~~~~~

StephenFluin · 2019-06-27T16:57:28Z

I'm hitting this as well.

Repro steps:

git clone git@github.com:StephenFluin/fluin.io.git
cd fluin.io
yarn
# enable Ivy in /src/tsconfig.json
ng serve

Failure log

WARNING in Unknown member type: "[key: string]: (data: any) => void;

ERROR in ../node_modules/@angular/common/http/http.d.ts:2799:22 - error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class

2799 export declare class HttpClientModule {
                          ~~~~~~~~~~~~~~~~
../node_modules/@angular/platform-browser/animations/animations.d.ts:37:22 - error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class

37 export declare class BrowserAnimationsModule {
                        ~~~~~~~~~~~~~~~~~~~~~~~
../node_modules/@angular/material/card/typings/card-module.d.ts:8:22 - error TS-996002: Appears in the NgModule.imports of AdminModule, but could not be resolved to an NgModule class

8 export declare class MatCardModule {
                       ~~~~~~~~~~~~~
../node_modules/@angular/material/input/typings/input-module.d.ts:8:22 - error TS-996002: Appears in the NgModule.imports of AdminModule, but could not be resolved to an NgModule class

8 export declare class MatInputModule {
                       ~~~~~~~~~~~~~~

** Angular Live Development Server is listening on localhost:4200, open your browser on http://localhost:4200/ **
ℹ ｢wdm｣: Failed to compile.

version info

Angular CLI: 8.1.0-beta.3
Node: 12.3.1
OS: linux x64
Angular: 8.1.0-rc.0
... animations, common, compiler, compiler-cli, core, forms
... platform-browser, platform-browser-dynamic, platform-server
... router, service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.801.0-beta.3
@angular-devkit/build-angular     0.801.0-beta.3
@angular-devkit/build-optimizer   0.801.0-beta.3
@angular-devkit/build-webpack     0.801.0-beta.3
@angular-devkit/core              8.1.0-beta.3
@angular-devkit/schematics        8.1.0-beta.3
@angular/cdk                      8.0.0-beta.2
@angular/cli                      8.1.0-beta.3
@angular/fire                     5.2.0-beta.3
@angular/material                 8.0.0-beta.2
@ngtools/webpack                  8.1.0-beta.3
@schematics/angular               8.1.0-beta.3
@schematics/update                0.801.0-beta.3
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.35.0

petebacondarwin · 2019-06-27T21:23:29Z

I think this might be a timing issue where webpack's cache is providing the un-processed .d.ts files to ngtsc rather than the ones that ngcc has modified.

Previously secondary entry-points, e.g `@angular/common/http`, were being resolved to the primary entry-point, e.g `@angular/common`. This meant that these entry-points were not being processed as part of a compilation leading to error messages. This change inverts the `tryResolvePackage` logic to attempt to use `require.resolve()` first and only looking in the parent directory of the typings file as a fallback if the main resolve fails. Fixes angular/angular#30972 (comment)

petebacondarwin · 2019-06-28T09:38:11Z

This PR should fix @StephenFluin's error - maybe also the original issue?
angular/angular-cli#14934

Previously secondary entry-points, e.g `@angular/common/http`, were being resolved to the primary entry-point, e.g `@angular/common`. This meant that these entry-points were not being processed as part of a compilation leading to error messages. This change inverts the `tryResolvePackage` logic to attempt to use `require.resolve()` first and only looking in the parent directory of the typings file as a fallback if the main resolve fails. Fixes angular/angular#30972 (comment)

j-Cis · 2019-07-10T14:02:57Z

Hello, I have the same problem

i ｢wdm｣: Compiling...
 93% after chunk asset optimization SourceMapDevToolPlugin main.js generate Source 93% after 
chunk asset optimization SourceMapDevToolPlugin polyfills.js generate S 93% after chunk asset 
optimization SourceMapDevToolPlugin runtime.js generate Sou 93% after chunk asset optimization 
SourceMapDevToolPlugin styles.js generate Sour 93% after chunk asset optimization 
SourceMapDevToolPlugin vendor.js generate Sour 93% after chunk asset optimization 
SourceMapDevToolPlugin polyfills.js generate S 93% after chunk asset optimization 
SourceMapDevToolPlugin runtime.js generate Sou 93% after chunk asset optimization 
SourceMapDevToolPlugin styles.js generate Sour 93% after chunk asset optimization 
SourceMapDevToolPlugin vendor.js generate Sour 93% after chunk asset optimization 
SourceMapDevToolPlugin main.js attach SourceMa
Date: 2019-07-10T13:43:03.940Z - Hash: 51aba17ea805a301a859
4 unchanged chunks
chunk {main} main.js, main.js.map (main) 302 kB [initial] [rendered]
Time: 2288ms
i ｢wdm｣: Compiled successfully.

    ERROR in node_modules/@syncfusion/ej2-angular-grids/src/grid/grid.module.d.ts(4,22): error 
    TS-996002: Appears in the NgModule.imports of **AppModule**, but could not be resolved to 
    an NgModule   class

my versions is

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

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.801.0
@angular-devkit/build-angular     0.801.0
@angular-devkit/build-optimizer   0.801.0
@angular-devkit/build-webpack     0.801.0
@angular-devkit/core              8.1.0
@angular-devkit/schematics        8.1.0
@ngtools/webpack                  8.1.0
@schematics/angular               8.1.0
@schematics/update                0.801.0
rxjs                              6.5.2
typescript                        3.4.5
webpack                           4.35.2

End my appModule ... where is error i'dont know:

import { BrowserModule } from '@angular/platform-browser';
import { NgModule } from '@angular/core';
import { Routes, RouterModule } from '@angular/router';

import { GridModule, PageService, 
SortService, FilterService, GroupService } from '@syncfusion/ej2-angular-grids';

//import { AppRoutingModule } from './app-routing.module';
import { AppComponent } from './app.component';
import { NavExitComponent, NavHideComponent, NavEditComponent, NavJoinComponent, 
NavHelpComponent, NavL18nComponent, NavOpenComponent, NavSaveComponent, 
NavToolComponent, NavViewComponent, } from './public/components/nav';
import { DomSanitizerPipe } from './public/pipes/dom-sanitizer.pipe';


const routes: Routes = [
   { path: '', component: NavHelpComponent, outlet: 'nav'},
   { path: 'exit', component: NavExitComponent, outlet: 'nav'},
   { path: 'hide', component: NavHideComponent, outlet: 'nav'},
   { path: 'save', component: NavSaveComponent, outlet: 'nav'},
   { path: 'open', component: NavOpenComponent, outlet: 'nav'},
   { path: 'join', component: NavJoinComponent, outlet: 'nav'},
   { path: 'edit', component: NavEditComponent, outlet: 'nav'},
   { path: 'tool', component: NavToolComponent, outlet: 'nav'},
   { path: 'help', component: NavHelpComponent, outlet: 'nav'},
   { path: 'l18n', component: NavL18nComponent, outlet: 'nav'},
   { path: 'view', component: NavViewComponent, outlet: 'nav'},
];

@NgModule({
  declarations: [
    AppComponent,
    NavExitComponent,
    NavHideComponent,
    NavEditComponent,
    NavJoinComponent,
    NavHelpComponent,
    NavL18nComponent,
    NavOpenComponent,
    NavSaveComponent,
    NavToolComponent,
    NavViewComponent,
    DomSanitizerPipe
  ],
  imports: [BrowserModule, RouterModule.forRoot(routes), GridModule ],
  providers: [PageService, SortService, FilterService, GroupService ],
  bootstrap: [AppComponent]
})
export class AppModule { }

lwensveen · 2019-07-10T14:39:58Z

This is still a problem indeed.

For instance:
node_modules/@angular/common/common.d.ts(115,22): error TS-996002: Appears in the NgModule.imports of CoreModule, but could not be resolved to an NgModule class

EDIT: with version 8.2.0-next.0

petebacondarwin · 2019-07-10T18:59:26Z

Can you confirm that you get the errors with the next versions of Angular (i.e. currently 8.2.0-next.1)? I see that @CisSasGot appears to be using 8.1.0, which does not contain a number of IVY fixes.

andrasz · 2019-07-23T11:44:12Z

Hello everyone!

I see this issue is closed, but I'm experiencing the same problem only with a different library. I'm using the latest angular cli at this time (8.2.0-next.2) and created a brand new app with ivy enabled. After installing the library from npm and building the app, the error is the same as reported above:

ERROR in node_modules/@mobiscroll/angular-lite/src/js/modules/mobiscroll.angular.free.d.ts:6:15 - error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class

6 declare class MbscModule {
                ~~~~~~~~~~

The steps to reproduce the issue is to add the @mobiscroll/angular-lite package to the project (and also install the rxjs-compat)

npm i @mobiscroll/angular-lite --save`
npm i rxjs-compat --save

and then import the MbscModule and add it to the AppModule imports:

import { MbscModule } from '@mobiscroll/angular-lite';`
@NgModule({
  declarations: [
    AppComponent
  ],
  imports: [
    BrowserModule,
    MbscModule,
  ],
  providers: [],
  bootstrap: [AppComponent]
})
export class AppModule { }

Is this still an issue with Ivy? The same library works when not using Ivy, and based on the error message I could not find anything else out there that resembled the problem.

petebacondarwin · 2019-07-24T08:24:33Z

I'll take a look.

Phil147 · 2019-07-24T10:56:57Z

We also run into this problem building our library with ivy enabled and ng-packagr on 8.2.0-next.2.
It throws the error once we import another module from the library itself.

E.g. we have an icon component and other components reuse that one.

So once we have

@NgModule({
  imports: [
    NxIconModule, <-------
    FormsModule,
    ReactiveFormsModule
  ],
})
export class NxRadioToggleModule {
}

the build fails at this point. The icon module gets built before.
[...]/icon/icon.module.d.ts(1,22): error TS-996002: Appears in the NgModule.imports of NxRadioToggleModule, but could not be resolved to an NgModule class

petebacondarwin · 2019-07-24T11:17:10Z

@Phil147 - just to be clear, building libraries with IVY mode is not yet supported. You should still build your library with ViewEngine mode and publish it with ngpackagr. Then only run ngcc on the published package when it is being consumed in an app.

Phil147 · 2019-07-24T11:20:37Z

@petebacondarwin thx for the heads up! but thx to the ivy checks we found that we didn't export everything in some public-api.ts files 👍 😄

do you know when library builds are planned to be supported?

ovchinnikov · 2019-07-26T08:58:57Z

Hello, I have the same problem with a different library (DevExtreme).
Here is an example https://github.com/ovchinnikov/dx-ivy
Any help is greatly appreciated.

naveedahmed1 · 2019-08-08T16:12:42Z

This is still a problem even with 9.0.0-next.0. I am receiving this error even with my apps internal shared modules.

@vikerman can you please reopen this issue?

JoostK · 2019-08-08T16:37:24Z

@naveedahmed1 This problem can have many different causes, could you please open a new issue with a reproduction so we can investigate?

naveedahmed1 · 2019-08-09T13:56:54Z

@JoostK yes you are right, in my case the problem was with one of the plugin.

StephenFluin · 2019-08-09T14:45:39Z

@naveedahmed1 just for tracking purposes, what plugin was it?

naveedahmed1 · 2019-08-09T14:58:05Z

@StephenFluin one of them is @agm/core, there's a pull request pending, which should fix this issue.

sebholstein/angular-google-maps#1647

So, for testing I have disabled this plugin.

The other was ng2-img-cropper, which is now maintained as a new plugin ngx-img-cropper, upgrading to ngx-img-cropper fixed the issue.

Another issue which I am having is related to flex-layout, I initially reported the issue on flex-layout repo but Angular team moved it to Angular repo since it's related to IVY. #32064

andrasz · 2019-08-12T06:49:45Z

@petebacondarwin Hi there! Did you have a chance to look into the problem I posted? Is this still an IVY issue or is the problem with @mobiscroll/angular-lite package? Thanks for your time!

petebacondarwin · 2019-08-12T15:13:22Z

It seems that we are not realising that the MbscModule is not being noticed by ngcc and so not being processed. I wonder if this is because we are processing the minified code, where multiple classes are declared in a single var statement separated by commas, and ngcc might be only looking at the first item in each declaration list?
Tracking internally as FW-1505

Ketec · 2019-08-22T10:21:57Z

Tried with 9.0.0-next.3, the problem still exists with MbscModule.

With 9 supposedly having Ivy by default - this is going to be a bigger and more widespread problem.

dioslaska · 2019-08-27T08:30:07Z

@petebacondarwin I don't think the var statement could be the issue here (or not only that).
I created an example which reproduces the error, with a dummy module and component. The compiled files are in src/mobiscroll, along with the generated .d.ts and metadata.json files.
Everything works as expected once Ivy is de-activated.
Any idea?

angular-automatic-lock-bot · 2019-09-27T16:03:07Z

This issue has been automatically locked due to inactivity.
Please file a new issue if you are encountering a similar or related problem.

Read more about our automatic conversation locking policy.

_{This action has been performed automatically by a bot.}

Previously secondary entry-points, e.g `@angular/common/http`, were being resolved to the primary entry-point, e.g `@angular/common`. This meant that these entry-points were not being processed as part of a compilation leading to error messages. This change inverts the `tryResolvePackage` logic to attempt to use `require.resolve()` first and only looking in the parent directory of the typings file as a fallback if the main resolve fails. Fixes angular/angular#30972 (comment)

AndrewKushnir added the comp: ivy label Jun 11, 2019

ngbot bot added this to the needsTriage milestone Jun 11, 2019

petebacondarwin added the comp: ngcc label Jun 24, 2019

petebacondarwin mentioned this issue Jun 28, 2019

fix(@ngtools/webpack): NGCC should process secondary entry-points angular/angular-cli#14934

Merged

vikerman closed this as completed in angular/angular-cli#14934 Jun 28, 2019

This was referenced Jun 29, 2019

[compiler-cli 8.1.0-next.3 w/ Ivy] NgModule error regarding HttpClientModule #31253

Closed

ERROR in node_modules/@angular/platform-browser/animations/animations.d.ts:37:22 #31348

Closed

ronnyek mentioned this issue Jul 16, 2019

Error when running ng serve akveo/nebular#1613

Closed

2 tasks

dioslaska mentioned this issue Aug 22, 2019

Could not be resolved to an NgModule class with Angular ivy acidb/mobiscroll#470

Closed

dioslaska mentioned this issue Sep 2, 2019

Ivy error TS-996002, when using compiled esm5 files #32442

Closed

whyboris mentioned this issue Sep 12, 2019

App does not compile with Ivy - Angular 9 #32466

Closed

1 task

angular-automatic-lock-bot bot locked and limited conversation to collaborators Sep 27, 2019

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

Ivy preview report: error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class #30972

Ivy preview report: error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class #30972

kolkov commented Jun 11, 2019 •

edited

JoostK commented Jun 11, 2019

kolkov commented Jun 11, 2019

kunl commented Jun 25, 2019

StephenFluin commented Jun 27, 2019

petebacondarwin commented Jun 27, 2019

petebacondarwin commented Jun 28, 2019

j-Cis commented Jul 10, 2019 •

edited

lwensveen commented Jul 10, 2019 •

edited

petebacondarwin commented Jul 10, 2019

andrasz commented Jul 23, 2019 •

edited

petebacondarwin commented Jul 24, 2019

Phil147 commented Jul 24, 2019 •

edited

petebacondarwin commented Jul 24, 2019

Phil147 commented Jul 24, 2019

ovchinnikov commented Jul 26, 2019

naveedahmed1 commented Aug 8, 2019

JoostK commented Aug 8, 2019

naveedahmed1 commented Aug 9, 2019

StephenFluin commented Aug 9, 2019

naveedahmed1 commented Aug 9, 2019

andrasz commented Aug 12, 2019

petebacondarwin commented Aug 12, 2019 •

edited

Ketec commented Aug 22, 2019

dioslaska commented Aug 27, 2019

angular-automatic-lock-bot bot commented Sep 27, 2019

Ivy preview report: error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class #30972

Ivy preview report: error TS-996002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class #30972

Comments

kolkov commented Jun 11, 2019 • edited

JoostK commented Jun 11, 2019

kolkov commented Jun 11, 2019

kunl commented Jun 25, 2019

Package Version

StephenFluin commented Jun 27, 2019

Failure log

version info

petebacondarwin commented Jun 27, 2019

petebacondarwin commented Jun 28, 2019

j-Cis commented Jul 10, 2019 • edited

lwensveen commented Jul 10, 2019 • edited

petebacondarwin commented Jul 10, 2019

andrasz commented Jul 23, 2019 • edited

petebacondarwin commented Jul 24, 2019

Phil147 commented Jul 24, 2019 • edited

petebacondarwin commented Jul 24, 2019

Phil147 commented Jul 24, 2019

ovchinnikov commented Jul 26, 2019

naveedahmed1 commented Aug 8, 2019

JoostK commented Aug 8, 2019

naveedahmed1 commented Aug 9, 2019

StephenFluin commented Aug 9, 2019

naveedahmed1 commented Aug 9, 2019

andrasz commented Aug 12, 2019

petebacondarwin commented Aug 12, 2019 • edited

Ketec commented Aug 22, 2019

dioslaska commented Aug 27, 2019

angular-automatic-lock-bot bot commented Sep 27, 2019

kolkov commented Jun 11, 2019 •

edited

j-Cis commented Jul 10, 2019 •

edited

lwensveen commented Jul 10, 2019 •

edited

andrasz commented Jul 23, 2019 •

edited

Phil147 commented Jul 24, 2019 •

edited

petebacondarwin commented Aug 12, 2019 •

edited