Error after updated to version 9

[clement911]

Trying to update to version 9.

Cryptic errors and massive headache as usual 😱.

I'm stuck on this one:

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

This likely means that the library (@angular/common/http) which declares HttpClientModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

What does it mean?

[clement911]

Setting "enableIvy": false in tsconfig.json does fix that particular error.
Isn't Ivy supposed to be usable already?

[petebacondarwin]

Are there no other errors?

[clement911]

The same error repeats multiple time.
Note that we did update material to 9.1.2 as part of the update instructions already.

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

This likely means that the library (@angular/common/http) which declares HttpClientModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

2801 export declare class HttpClientModule {
                          ~~~~~~~~~~~~~~~~
node_modules/mydatepicker/dist/my-date-picker.module.d.ts:1:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (mydatepicker) which declares MyDatePickerModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

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

This likely means that the library (@angular/platform-browser/animations) which declares BrowserAnimationsModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

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

This likely means that the library (@angular/material/dialog) which declares MatDialogModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

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

This likely means that the library (@angular/material/input) which declares MatInputModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatInputModule {
                       ~~~~~~~~~~~~~~
node_modules/@angular/material/select/select-module.d.ts:8:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/select) which declares MatSelectModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatSelectModule {
                       ~~~~~~~~~~~~~~~
node_modules/@angular/material/checkbox/checkbox-module.d.ts:11:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/checkbox) which declares MatCheckboxModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

11 export declare class MatCheckboxModule {
                        ~~~~~~~~~~~~~~~~~
node_modules/@angular/material/form-field/form-field-module.d.ts:8:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/form-field) which declares MatFormFieldModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatFormFieldModule {
                       ~~~~~~~~~~~~~~~~~~
node_modules/@angular/material/snack-bar/snack-bar-module.d.ts:8:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/snack-bar) which declares MatSnackBarModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatSnackBarModule {
                       ~~~~~~~~~~~~~~~~~
node_modules/@angular/material/icon/icon-module.d.ts:8:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/icon) which declares MatIconModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatIconModule {
                       ~~~~~~~~~~~~~
node_modules/@angular/material/tree/tree-module.d.ts:8:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/tree) which declares MatTreeModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatTreeModule {
                       ~~~~~~~~~~~~~
node_modules/@angular/material/tooltip/tooltip-module.d.ts:8:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/tooltip) which declares MatTooltipModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatTooltipModule {
                       ~~~~~~~~~~~~~~~~
node_modules/@angular/material/slider/slider-module.d.ts:8:22 - error NG6002: Appears in the NgModule.imports of AppModule, but could not be resolved to an NgModule class.

This likely means that the library (@angular/material/slider) which declares MatSliderModule has not been processed correctly by ngcc, or is not compatible with Angular Ivy. Check if a newer version of the library is available, and update if so. Also consider checking with the library's authors to see if the library is expected to be compatible with Ivy.

8 export declare class MatSliderModule {
                       ~~~~~~~~~~~~~~~

[petebacondarwin]

Can you post all of the versions of Angular packages that are installed, please.

[clement911]

"dependencies":
{
"@angular/animations": "^9.0.6",
"@angular/cdk": "^9.1.2",
"@angular/common": "^9.0.6",
"@angular/compiler": "^9.0.6",
"@angular/core": "^9.0.6",
"@angular/forms": "^9.0.6",
"@angular/material": "^9.1.2",
"@angular/platform-browser": "^9.0.6",
"@angular/platform-browser-dynamic": "^9.0.6",
"@angular/router": "^9.0.6",
"@ngx-loading-bar/core": "^4.2.0",
"bootstrap": "^4.4.1",
"c3": "^0.5.4",
"core-js": "^2.4.1",
"file-saver": "^1.3.8",
"interact.js": "^1.2.8",
"jquery": "^3.4.1",
"mydatepicker": "2.6.9",
"ngx-chips": "2.1.0",
"popper.js": "^1.16.0",
"rxjs": "^6.5.4",
"select2": "3.5.1",
"tslib": "^1.10.0",
"zone.js": "~0.10.2"
},
"devDependencies": {
"@angular-devkit/build-angular": "~0.900.6",
"@angular/cli": "^9.0.6",
"@angular/compiler-cli": "^9.0.6",
"@angular/language-service": "^9.0.6",
"@types/c3": "^0.7.3",
"@types/file-saver": "^1.3.0",
"@types/google.analytics": "^0.0.39",
"@types/interact.js": "^1.0.22",
"@types/jquery": "^2.0.49",
"@types/node": "^12.11.1",
"@types/select2": "^4.0.34",
"codelyzer": "^5.1.2",
"tslint": "~5.19.0",
"typescript": "~3.7.5"
}

[destus90]

This topic has been discussed lots of times...
npm ci should help you.

[clement911]

Was it documented anywhere? I dont see anything in the ng 9 migration instructions

[destus90]

@clement911
Not sure. More information can be found here #35399 and here #35480 (comment)

[clement911]

npm cache clean --force didn't help.
What do we do now ?

Is it recommended/safe to run npm ci?

[clement911]

Deleting node_modules and running npm install still results in the same error.

[amirensit]

Same problem for me.

[JoostK]

For everyone experiencing this issue even after deleting node_modules, what does your build process look like? If you're using Angular CLI then it should work out of the box, but if you're using a custom build pipeline then you'd have to ensure that the node_modules tree is prepared for the usage with Ivy using ngcc. Please refer to the docs for more info on ngcc.

For folks that are using the CLI, would someone be able to share details or ideally a reproduction so that we can investigate?

[clement911]

We use Angular CLI.
No custom build pipeling, precisely because we wanted to avoid this kind of cryptic errors and upgrade pains...