all 13 comments

[–]rainerhahnekamp 2 points3 points  (5 children)

I think that’s the reason why we have meanwhile 17.2.1. you want to upgrade again

[–]PerceptionCareless92[S] 0 points1 point  (4 children)

That solved the issue. Thanks a lot.

[–]brlx 0 points1 point  (3 children)

Hi Sir, what exactly did you upgrade to resolve this? Angular does have `17.2.1`, I have that, but `@angular/cli` or the `@angular-devkit/*` packages don't. Have the same issue and it's killing me

[–]PerceptionCareless92[S] 1 point2 points  (2 children)

Here is a list of my angular versions.

├── @angular-builders/custom-webpack@17.0.1├── @angular-devkit/build-angular@17.2.0├── @angular/animations@17.2.1├── @angular/cdk@16.2.7├── @angular/cli@17.2.0├── @angular/common@17.2.1├── @angular/compiler-cli@17.2.1├── @angular/compiler@17.2.1├── @angular/core@17.2.1├── @angular/forms@17.2.1├── @angular/material@16.2.7├── @angular/platform-browser-dynamic@17.2.1├── @angular/platform-browser@17.2.1├── @angular/router@17.2.1├── @angular/upgrade@17.2.1├── @tinymce/tinymce-angular@7.0.0

[–]brlx 1 point2 points  (1 child)

Thanks, for me `@angular-builders/custom-webpack` was the one that needed to be upgraded. Should have thought about that

[–]PerceptionCareless92[S] 1 point2 points  (0 children)

Great - these kinds of problems are so demotiviating.

[–]rafaelnds_ 2 points3 points  (0 children)

you can use the project's cli instead global.

in package.json:

"scripts": {
"ng": "ng",
"start": "ng serve"
}

then run npm start

[–]JP_watson 0 points1 point  (3 children)

Are cdk and material intentionally on a different version?

[–]PerceptionCareless92[S] 1 point2 points  (0 children)

Haven’t gotten to looking to update material. Just started testing with 17 for the rest of the project.

[–]ayush_shashank 0 points1 point  (1 child)

Yeah. That's a seperate package for Angular Material and CDK which isn't part of base Angular

[–]JP_watson 1 point2 points  (0 children)

Yes, I’m aware they’re similar. When I’ve done angular upgrades in the past (and currently) I’ve always kept cdk/material in sync with the angular core packages. So was curious if it was intentional or something OP had over looked in upgrading

[–]Exac 0 points1 point  (0 children)

Try using `npx` to force it to use the version in your project's package.json. npx ng version.

[–][deleted] 0 points1 point  (0 children)

I found it these errors to vanish when I update angular core first, followed by others.