4 ms·

I hear most Angular projects being stuck at around version 15 due not being able to migrate away from Angular Material "Legacy".

tietjens 3y ago
This seems to be true for many and happened to me. It is an absolute nightmare trying to upgrade Material. Now I’ve convinced my team to move to a different framework.
the_cramer 3y ago
There are still issues with density not working well with some angular Material controls. This forced us to do some hacky css stuff. Some of the github issues have been open a long time now...
peer2pay 3y ago
You can upgrade all the way to Angular 17 without having to adopt the new MDC components. Only this May with Angular 18 support for the legacy components will be dropped completely. That’s the reason we’re currently migrating all our remaining usages of Material components to ng-zorro.
- tubthumper8 3y ago
  They previously announced [1] these would be removed in v17, did that change? [1] https://blog.angular.io/angular-v16-is-here-4d7a28ec680d https://blog.angular.io/angular-v16-is-here-4d7a28ec680d
  - peer2pay 3y ago
    No but Angular 17 is backwards compatible with @angular/material@16 so you can upgrade Angular without having to upgrade Material [1]. We currently run @angular/core@17.0.8 and @angular/material@16.2.12 in production without problems. In the end this only buys you another 6 months but helped us get ready for Angular 18 in May. [1] https://blog.angular.io/introducing-angular-v17-4d7033312e4b https://blog.angular.io/introducing-angular-v17-4d7033312e4b
- bags43 3y ago
  Where did you get info for Angular 18?
  - peer2pay 3y ago
    The announcement post for Angular 17 included a few sentences about this [1] We deprecated legacy components in v15 to be removed in v17. Even though they’ll not be part of the Angular Material v17 package, you can still update your apps to Angular v17 and use the v16 Angular Material package. This will be an option until v18, after which Angular Material v16 will no longer be compatible with newer versions of Angular. [1] https://blog.angular.io/introducing-angular-v17-4d7033312e4b https://blog.angular.io/introducing-angular-v17-4d7033312e4b
mcgl 3y ago
After angular17 came out, my project has been upgraded from v11 to v17. I don’t think there are any problems.

tietjens 3y ago

This seems to be true for many and happened to me. It is an absolute nightmare trying to upgrade Material. Now I’ve convinced my team to move to a different framework.

the_cramer 3y ago

There are still issues with density not working well with some angular Material controls. This forced us to do some hacky css stuff. Some of the github issues have been open a long time now...

peer2pay 3y ago

You can upgrade all the way to Angular 17 without having to adopt the new MDC components. Only this May with Angular 18 support for the legacy components will be dropped completely. That’s the reason we’re currently migrating all our remaining usages of Material components to ng-zorro.

tubthumper8 3y ago
They previously announced [1] these would be removed in v17, did that change? [1] https://blog.angular.io/angular-v16-is-here-4d7a28ec680d https://blog.angular.io/angular-v16-is-here-4d7a28ec680d
- peer2pay 3y ago
  No but Angular 17 is backwards compatible with @angular/material@16 so you can upgrade Angular without having to upgrade Material [1]. We currently run @angular/core@17.0.8 and @angular/material@16.2.12 in production without problems. In the end this only buys you another 6 months but helped us get ready for Angular 18 in May. [1] https://blog.angular.io/introducing-angular-v17-4d7033312e4b https://blog.angular.io/introducing-angular-v17-4d7033312e4b
bags43 3y ago
Where did you get info for Angular 18?
- peer2pay 3y ago
  The announcement post for Angular 17 included a few sentences about this [1] We deprecated legacy components in v15 to be removed in v17. Even though they’ll not be part of the Angular Material v17 package, you can still update your apps to Angular v17 and use the v16 Angular Material package. This will be an option until v18, after which Angular Material v16 will no longer be compatible with newer versions of Angular. [1] https://blog.angular.io/introducing-angular-v17-4d7033312e4b https://blog.angular.io/introducing-angular-v17-4d7033312e4b

mcgl 3y ago

After angular17 came out, my project has been upgraded from v11 to v17. I don’t think there are any problems.