chore: update to Angular 15 #398
Conversation
|
Nice, thank you for the PR @Yberion. Will review it soon. |
| @@ -1,8 +1,8 @@ | |||
| import { LayoutModule } from '@angular/cdk/layout'; | |||
| import { ComponentFixture, TestBed, waitForAsync } from '@angular/core/testing'; | |||
| import { MatButtonModule } from '@angular/material/button'; | |||
| import { MatLegacyButtonModule as MatButtonModule } from '@angular/material/legacy-button'; | |||
There was a problem hiding this comment.
is it possible to use mdc based components? I know we don't provide CSS out of the box, but may break the user app if they have some :ng-deep
There was a problem hiding this comment.
https://material.angular.io/guide/mdc-migration there is a migration guide.
There was a problem hiding this comment.
I think it is harder for people to migrate to MDC as it require quite a lot of CSS update.
If people were customizing your components, it would be easier for them if you don't switch for MDC yet.
Maybe you can do 2 versions, one without MDC (7.0.0) and one with MDC (7.1.0) ?
Up to you, do I migrate this PR to use MDC?
|
Awesome, I will prepare the MDC PR. |
|
BTW just release V7 with Angular 15 changes |
|
Yeah I noticed, thank you for that 😊 |
Hello,
This PR does:
typescript@types/node^15browserlistrcwas removednpx browserslist --update-dbto updatecaniuse-liteenvironmentfiles have been deletedangular.jsonwas update to reflect thatscssfiles in the prettieresbuild@angular-devkit/build-angular:browserto@angular-devkit/build-angular:browser-esbuildFeel free to also remove other PR/branche related to packages update for cleaning purpose.
If everything is ok, I can make a new commit to bump the version.
Could you release a new version following this PR? (This would be much appreciated heh)
Have a good day.
cc @santoshyadavdev