Angular 14 might change the way we write Angular components!

Angular 14 was released and it introduces two exciting new features / changes:
- Typed (Reactive) Forms
- Standalone Components

Especially standalone components could change the way we build Angular apps forever - at least once the feature is fully stable and out of "Developer Preview" (in which it currently still is).
Writing Angular apps might become easier and require less boilerplate code. 🙂

I did also add a brand-new section about "Standalone Components" to my "Angular - The Complete Guide" course.

----------

• Follow @maxedapps and @academind_real on Twitter

See you in the videos!

----------

[TheOraclesOfRevival]

As you and your web application grow up, you realize that Angular is what you needed right from time.

[HuyLe-vvgo]

Since the release of IVY, Angular really stand its ground when compares to React, Vue, especially in the Enterprise world.

[eranbraun]

First feature looks great, second well I think most people will agree that for very small applications it is great but modules are actually something not that "stupid" and in larger applications it helps organizing and managing the application much easier of cource when you know how to divide well. At the end if every option is a blessing when you know how to use it.

[hexton]

I'm so excited for the stable update 😻

[alifepenneddown]

With standalone, I hope "load what is needed" functionality could also come out of the box, thereby solving one of the biggest issues with Angular bundles right now

[jayfox]

I think that I still prefer the modules pattern. It makes so much more sense since you can organise your app by groups which for me, is what makes angular shine.

[Tsukasa]

I ready finished, I will retake, the way you explain its really easy to understand, I also was able to make a dashboard connected to an API y write my self in node

[josephuwagwu]

Standalone components is the way to go. Super excited!

[lshikhov]

TypedForms - great step towards binding html and code. i hope it will help reduce number of possible errors during writings code-behind.
Standalone components - looks interesting, but has a lot of questions... lazy loading support? routing?

[mridulsetia]

Instead of just adding imports in the Module file we'll have to add imports in all of our components using some extra flags. Doesn't that sound more cumbersome? The present approach looks just fine to me. On the positive side, it might affect the way we import components to other components, which could help in a lot of ways.

[theanswer]

Angular team again taking care for the painless upgrade to the new version :) Love this framework.

[dmitriysahno]

Even now, when angular 16, it’s very good explanation! Thanks!

[nikhilhukkerikar]

Just wondering if the new standalone components architecture would lead to more cyclic dependencies in a larger application 🧐 modules really helped identifying these issues tbh!

[cancelbubble]

Thanks much for this video. Very nice to see this and hear your Angular course is - and will be - updated for new Angular features.

[kareemreda]

can't wait,
export modules and import in each other .
even for Route and Form .. etc
some time is so confusing


I enrolled in course since 2017, and i still following the new section

I hope to see angular material section, or a new course for it
thanks Maximilian,

[rvg]

Thanks for the great explanation. Your VS code theme looks stunning, do you mind sharing which extension its based on?

[sourire]

thanks Max for all these explanations. Reactiv forms should be a really appreciated new features but standalone components, as an Angular developer I do not really see how it simplifies the code.
I really like to used modules to classify properly all the different parts. When you used to work with Module, I think this new feature will bring more confusions than advantages in fact.

[siya.abc]

Nice ! The standalone components will definitely help make Angular less enterprisey. Not quite there yet but in the right direction

[diego_sabbagh]

Hi Max, thanks for the update. Unless the majority of people in the comments, I'm more interested in the typed forms. I wonder what happens now when we access the FormControls themselves instead of the values within.
What happens to the form.get('email') approach, for example in the scenario of accessing valueChanges? Is this typed feature available only on the form value (form.value.email) or can we benefit from it elsewhere?
Another related question is what happens if we use the FormBuilder. Can we still have a typed form in that case? And how, considering we don't manually create the individual FormControls?
Thanks again

[Alex-bcxe]

Angular is KING for me Angular and Nest JS forever