Everything You Need to Know About Angular’s Standalone
In-Depth Exploration: Angular’s Standalone Feature
Hi there 👋
Angular has undergone many significant changes lately, including signals, standalone, deferrable views, new built-in control flow, etc. This article is dedicated to one of these features: the standalone feature. It’s a must-know for every Angular developer, as it transforms the way we code and structure our application.
👀 Video version available at the end of this article.
🚀It started in Angular 14
The standalone feature was initially introduced in the developer preview of Angular 14. This feature marks a shift from a module-based app, where components must be declared in a module to be used, to a fully component-based app.
As of Angular 17, the Angular CLI schematics fully support the standalone feature, and it is now the default option (you don’t need to enable it with —standalone
flag. With this feature, you can generate a complete standalone app, standalone pipe, component, directive, and even convert your code to standalone.