Business
Jobs
  • About Us
  • Solutions
    • Job Postings
      Post your job and receive qualified candidates in 48h.
    • Candidate Assessments
      500+ technical and psychological tests, plus anti-fraud.
    • Headhunting
      Tailor-made executive search from start to finish.
    • Payroll + EOR
      Payroll dispersal and EOR across 15+ LATAM countries.
  • Pricing
  • Jobs

0

534
Views
Angular 9 mat-progress-buttons error: ERROR in Failed to compile entry-point mat-progress-buttons (es2015 as esm2015) due to compilation errors

Getting an error with mat-progress-button given below after updating from Angular 8 to Angular 9. It was working fine with Angular 8. Is MatProgressButton incompatible with Angular 9?

node_modules/mat-progress-buttons/esm2015/mat-progress-buttons.js:181:26 - error NG1010: Value at position 1 in the NgModule.imports of MatProgressButtonsModule is not a reference: [object Object]

The import looks like: import { MatProgressButtonsModule } from 'mat-progress-buttons';

My package.json looks like this:

  "dependencies": {
    "@angular/animations": "^9.0.2",
    "@angular/cdk": "^9.1.0",
    "@angular/common": "~9.0.2",
    "@angular/compiler": "~9.0.2",
    "@angular/core": "~9.0.2",
    "@angular/forms": "~9.0.2",
    "@angular/material": "^9.1.0",
    ...
    "@angular/router": "~9.0.2",
    "core-js": "^2.5.4",
    "mat-file-upload": "^1.3.2",
    "mat-progress-buttons": "^8.0.7",
    "rxjs": "~6.5.4",
    "tslib": "^1.10.0",
    "zone.js": "~0.10.2"
  },
  "devDependencies": {
    "@angular-devkit/build-angular": "~0.900.3",
    "@angular/cli": "~9.0.3",
    "@angular/compiler-cli": "~9.0.2",
    "@angular/language-service": "~9.0.2",
   ...
    "typescript": "^3.7.5"
  }
}

over 4 years ago · Santiago Trujillo
2 answers
Answer question

0

I had the same issue. It seems like there was some kind of error with the versions of the installed modules. I resolved it by deleting the node_module folder and reinitiating it with npm install.

over 4 years ago · Santiago Trujillo Report

0

Deleted node_modules folder, dist folder, and package-lock.json file

npm cache clean --force
npm cache verify
npm i

Then it worked for me!

over 4 years ago · Santiago Trujillo Report
Answer question
Find remote jobs

Discover the new way to find a job!

Top jobs
Top job categories
Business
Post vacancy Pricing Sales
Legal
Terms and conditions Privacy policy
© 2026 PeakU Inc. All Rights Reserved.
Andres GPT
Show me some job opportunities
There's an error!