I am currently in the process of upgrading angular, including angular material to v17. I am following the angular.dev guide on this, which can be found here https://angular.dev/update-guide?v=16.0-17.0&l=2 (you must check the boxes "I use Angular Material" and "I use Windows"). ng update @angular/core@17 @angular/cli@17 goes through without a problem. When I try to execute the ng update @angular/material@17, the angular/cdk is at first glance successfully update to version 17.3.10, but the same cannot be said for angular material. The version of angular material is changed to 17.3.10 in the package.json, but for some odd reason the migrations cannot be successfully executed on that package. It stays frozen as you can see in the logs and after a couple of hours it finally says that javascript is out of heap memory. Here is the logs during ng update @angular/material@17 PS C:\Users\MyUser\Documents\Project\frontend> .\node_modules\.bin\ng update @angular/material@17 Using package manager: npm Collecting installed dependencies... Found 55 dependencies. Fetching dependency metadata from registry... Updating package.json with dependency @angular/cdk @ "17.3.10" (was "16.2.14")... Updating package.json with dependency @angular/material @ "17.3.10" (was "16.2.14")... Updating package.json with dependency @angular/material-moment-adapter @ "17.3.10" (was "16.2.14")... UPDATE package.json (3626 bytes) ✔ Packages successfully installed. ** Executing migrations of package '@angular/cdk' ** > Updates the Angular CDK to v17. ✓ Updated Angular CDK to version 17 Migration completed (No changes made). ** Executing migrations of package '@angular/material' ** > Updates Angular Material to v17. I am using node 18.13.0 and here is also a list of the dependencies up until the update of the angular material package is started: "private": true, "dependencies": { "@angular/animations": "^17.3.12", **"@angular/cdk": "^16.2.14",** "@angular/common": "^17.3.12", "@angular/compiler": "^17.3.12", "@angular/core": "^17.3.12", "@angular/forms": "^17.3.12", **"@angular/material": "^16.2.14",** **"@angular/material-moment-adapter": "^16.2.14",** "@angular/platform-browser": "^17.3.12", "@angular/platform-browser-dynamic": "^17.3.12", "@angular/router": "^17.3.12", "@ngxs/logger-plugin": "^18.0.0", "@ngxs/store": "^18.0.0", "jsnlog": "^2.30.0", "moment": "^2.29.1", "pdfmake": "^0.2.4", "rxjs": "~7.4.0", "tslib": "^2.3.1", "uuid": "^8.3.2", "zone.js": "~0.14.10" }, "devDependencies": { "@angular-devkit/build-angular": "^17.3.11", "@angular-eslint/builder": "^13.0.1", "@angular-eslint/eslint-plugin": "^13.0.1", "@angular-eslint/eslint-plugin-template": "^13.0.1", "@angular/cli": "^17.3.11", "@angular/compiler-cli": "^17.3.12", "@angular/language-service": "^17.3.12", "@ngxs/devtools-plugin": "^18.0.0", "@types/jasmine": "^3.10.12", "@types/node": "^16.11.12", "@types/pdfmake": "^0.1.19", "@types/uuid": "^8.3.3", "@typescript-eslint/eslint-plugin": "^5.62.0", "@typescript-eslint/parser": "^5.62.0", "codelyzer": "^6.0.2", "eslint": "^8.57.1", "eslint-config-prettier": "^8.3.0", "eslint-plugin-angular": "^4.1.0", "eslint-plugin-import": "^2.25.3", "eslint-plugin-jasmine": "^4.1.3", "eslint-plugin-jsdoc": "^37.1.0", "eslint-plugin-prefer-arrow": "^1.2.3", "jasmine-core": "~3.10.1", "jasmine-spec-reporter": "~7.0.0", "karma": "^6.3.20", "karma-chrome-launcher": "^3.1.1", "karma-coverage": "^2.2.1", "karma-jasmine": "^4.0.2", "karma-jasmine-html-reporter": "^1.7.0", "karma-spec-reporter": "0.0.32", "prettier": "^2.5.1", "ts-node": "~10.4.0", "typescript": "^5.4.5", "webpack-sources": "^3.2.2" } I tried different permutations on the versions of nodejs, typescript, typescript-eslint, ts-node, etc., but still stuck at the same problem. Any ideas on why this would freeze up or how I can manage through? Continue reading...
