Skip to content

ng update v9 "MatProgressSpinnerModule" was not found in the Material library. #17715

@elvirdolic

Description

@elvirdolic

Reproduction

When I run ng update @angular/material@next I got following warnings where the import path can't be changed and needs to be done manually. It seems somehow related to MatProgressSpinnerModule because all warning are related to this Module

Here is one file which was not migrated:

import { CommonModule } from '@angular/common';
import { NgModule } from '@angular/core';
import { LoadingSpinnerComponent } from './loading-spinner.component';
import { MatProgressSpinnerModule } from '@angular/material';
import { LoadingSpinner } from './loading-spinner';

@NgModule({
  imports: [CommonModule, MatProgressSpinnerModule],
  declarations: [LoadingSpinnerComponent],
  exports: [LoadingSpinnerComponent],
  entryComponents: [LoadingSpinnerComponent],
  providers: [LoadingSpinner]
})
export class LoadingSpinnerModule {}

Expected Behavior

What behavior were you expecting to see?

That all files are migrated

Actual Behavior

What behavior did you actually see?

That some files are not migrated

Environment

Angular CLI: 9.0.0-rc.2
Node: 12.3.1
OS: win32 x64
Angular: 9.0.0-rc.2
... animations, cdk, cli, common, compiler, compiler-cli, core
... forms, language-service, material, material-moment-adapter
... platform-browser, platform-browser-dynamic, router
... service-worker

Package                           Version
-----------------------------------------------------------
@angular-devkit/architect         0.803.3
@angular-devkit/build-angular     0.900.0-rc.2
@angular-devkit/build-optimizer   0.900.0-rc.2
@angular-devkit/build-webpack     0.900.0-rc.2
@angular-devkit/core              9.0.0-rc.2
@angular-devkit/schematics        8.3.3
@angular/flex-layout              8.0.0-beta.26
@angular/pwa                      0.801.3
@ngtools/webpack                  9.0.0-rc.2
@schematics/angular               8.1.3
@schematics/update                0.900.0-rc.2
rxjs                              6.5.3
typescript                        3.6.4
webpack                           4.41.2

Metadata

Metadata

Assignees

Labels

P1Impacts a large percentage of users; if a workaround exists it is partial or overly painful

Type

No type

Projects

No projects

Relationships

None yet

Development

No branches or pull requests

Issue actions