Angular 17 is finally here, with a lot of new features and a big breaking change. Check out this video to see all the new features and find out what it means for your projects! Highlights of this video - Note - Appologies, Signals based components are delayed and will not be the part of Angular 17 release. I wasn't aware of this update at the time of recording this video. But given information is still correct. TypeScript 5.2 CSS Is Removed Automatically New Template Syntax Signals based components View Transitions API Improved support for server-side rendering Deferrable views New declarative control flow Some Router Properties Moved To provideRouter and RouterModule.forRoot “Go to definition” For StyleUrl Files Errors When Lazy Loaded Images Slow Down Page Render Node.js 18.13.0 Required New Way To Set Up Routes For Testing
Agree, but Other breaking changes are equally important because - Signals and Zone.js Removal: Signals are coming as an optional feature, so if they remove Zone.js or make it optional, how will the other non-signal components trigger the change detection? Of course, there will be a way, but how much effort will be required from the developer's side to learn and bug-fix due to these changes? New Template Syntax: It's going to replace the existing structural directive. Okay, but how convenient will it be to migrate to these? When you upgrade to Angular 17, will it make these changes automatically, or will developers need to make this change across the application? Now, think about the efforts involved here. Functional Interceptors, Guards, and Others: Again, when you upgrade, is it automatically going to update the class-based guards or interceptors, or will developers have to do this? Node.js: You are already aware of it :)
Great content! A suggestion - please reduce the volume of the background music. After 10 minutes I nearly stopped watching because it was so annoying. But still, very valuable content.🤓
I'm grateful for your kind words and feedback! Your suggestion to reduce the volume of the background music is duly noted. I'll make sure to improve the audio balance in my upcoming videos. Thank you for watching and finding the content valuable!
These things are just for making Hype about dying Angular. What's new in these features? They are just copied from other frameworks like React and Svelte. 😒😒
Angular has been rumored to be dying since 2016, but I can see it is still very much alive. Yes, it's incorporating features from other frameworks, but it has its own solid architecture that others don't have. This makes Angular a comprehensive framework, including all the new features that other libraries provide. 🙂
Angular still has a good share in the market. Seems like there is a good number of people looking hard to see Angular dying, but unfortunately it is not.
Angular 17 is finally here, with a lot of new features and a big breaking change. Check out this video to see all the new features and find out what it means for your projects!
Highlights of this video -
Note - Appologies, Signals based components are delayed and will not be the part of Angular 17 release. I wasn't aware of this update at the time of recording this video. But given information is still correct.
TypeScript 5.2
CSS Is Removed Automatically
New Template Syntax
Signals based components
View Transitions API
Improved support for server-side rendering
Deferrable views
New declarative control flow
Some Router Properties Moved To provideRouter and RouterModule.forRoot
“Go to definition” For StyleUrl Files
Errors When Lazy Loaded Images Slow Down Page Render
Node.js 18.13.0 Required
New Way To Set Up Routes For Testing
None of the breaking changes apart from Node are breaking. They are all optional.
Agree, but Other breaking changes are equally important because -
Signals and Zone.js Removal: Signals are coming as an optional feature, so if they remove Zone.js or make it optional, how will the other non-signal components trigger the change detection? Of course, there will be a way, but how much effort will be required from the developer's side to learn and bug-fix due to these changes?
New Template Syntax: It's going to replace the existing structural directive. Okay, but how convenient will it be to migrate to these? When you upgrade to Angular 17, will it make these changes automatically, or will developers need to make this change across the application? Now, think about the efforts involved here.
Functional Interceptors, Guards, and Others: Again, when you upgrade, is it automatically going to update the class-based guards or interceptors, or will developers have to do this?
Node.js: You are already aware of it :)
How convenient are new structural directives, cos I found them HARD.
Ha ha ha.. But something new must be coming to replace that approach. Wait for functional components in Angular 18.
Thanks for your comment! It's always exciting to see what new features and approaches are introduced in the latest versions of Angular.
How to stop the automatic removal of CSS?
Keep it up buddy 🎉
Thank you 🙂
Good review 👍🏿
Thank you!
Great content! A suggestion - please reduce the volume of the background music. After 10 minutes I nearly stopped watching because it was so annoying. But still, very valuable content.🤓
I'm grateful for your kind words and feedback! Your suggestion to reduce the volume of the background music is duly noted. I'll make sure to improve the audio balance in my upcoming videos. Thank you for watching and finding the content valuable!
Looks like they are following React. 🤔
ew react
These things are just for making Hype about dying Angular. What's new in these features? They are just copied from other frameworks like React and Svelte. 😒😒
Angular has been rumored to be dying since 2016, but I can see it is still very much alive. Yes, it's incorporating features from other frameworks, but it has its own solid architecture that others don't have. This makes Angular a comprehensive framework, including all the new features that other libraries provide. 🙂
Angular still has a good share in the market. Seems like there is a good number of people looking hard to see Angular dying, but unfortunately it is not.
I felt the same. Now nothing new left for Angular.
Svelte and React don't have signals.
@@theanswer1993 changing name doesn't change its behaviour. React has useState Hook for that