(Truly!?) Component oriented Angular application using Standalone components

What’s wrong with NgModule?

For a long time, there was a debate — why do we need NgModules? Many seasoned developers find NgModules approach bit complicated, whereas for newbie it is a test to comprehend. Though NgModule brings in many features like a single place to maintain service dependencies, logical grouping of components, providing encapsulation etc., there was an ask to make it optional and build Angular application directly component based.

Comparing NgModule vs Standalone application

In traditional Angular application, the application is bootstrapped with NgModule and it’s bootstrap property specifying the root component.

--

--

Get the Medium app

A button that says 'Download on the App Store', and if clicked it will lead you to the iOS App store
A button that says 'Get it on, Google Play', and if clicked it will lead you to the Google Play store