Skip to main content

What's New in Angular 12 | Features of Angular 12

Angular 12 will be smaller, faster, and easier to use. It will be making Angular developer's life easier. The full version of Angular 12 will be released sooner.


Angular receives a large number of feature requests, both from inside Google and from the broader open-source community i.e.

1)      Potential Performance Improvements

2)      Maintenance tasks,

3)      Code refactoring

4)      And so on.


Anticipated Features and Benefits of the Angular 12 Release:

1.      Better Developer Ergonomics @angular/forms

2.      Leverage Full Framework Capabilities with Zone.js Opt-Out

3.      Reducing Framework Overheard by Removing Legacy

4.      Improve Test Times and Automatic Test Environment Tear Down

5.      Support Adding Directives to Host Elements

6.      Revamp performance dashboards to detect regressions

7.      Simplified Angular Mental Model with Optional NgModules

8.      Update our e2e testing strategy

9.      Ergonomic Component Level Code-Splitting APIs

10.   Improve Build Performance With ngc as a tsc Plug-In Distribution

11.   Offer Google engineers better integration with Angular and Google's internal server stack

12.   Improved developer on-boarding with refreshed introductory documentation

13.   Faster apps by inlining critical styles in Universal applications

14.   Increased security with native Trusted Types in Angular

 

Better developer ergonomics with strict typing for @angular/forms:

The stricter type checking in the reactive forms will allow us:

1)      To catch more issues during development time

2)      To enable better text editor and IDE support

3)      To improve the type checking for reactive forms

 

Leverage full framework capabilities with Zone.js opt-out:

The Zone.js opt-out will be simplifies the framework, improve debugging, and reduce application bundle size.  

Additionally, this will also allow us to take advantage of native async and await syntax, which currently Zone.js does not support.

 

Reduce framework overhead by removing legacy View Engine:

After the transition of all our internal tooling to Ivy has completed, we have the implemented the following:

1)      Remove the legacy View Engine for smaller Angular conceptual overhead

2)      Smaller package size

3)      Lower maintenance cost

4)      Lower complexity of the codebase

 

Improved test times and debugging with automatic test environment tear down:

To improve test time and create better isolation across tests and change TestBed to automatically clean up and tear down the test environment after each test run.

 

Improved build performance with ngc as a tsc plugin distribution:

Distributing the Angular compiler as a plugin of the TypeScript compiler will substantially improve developers' build performance and reduce maintenance costs.

 

Support adding directives to host elements:

A long-standing feature request is to add the ability to add directives to host elements. The feature will allow us to augment their own components with additional behaviours without using inheritance.

 

Simplified Angular mental model with optional NgModules:

The NgModules is an optional and it allows us to develop standalone components and implement an alternative API for declaring the component’s compilation scope.

 

Ergonomic component level code-splitting APIs:

A common problem of the all web applications is their slow initial load time. A way to improve it is to apply more granular code-splitting on a component level.

 

Other capabilities eyed for Angular 12 include:

1.      Support for inline Sass in components

2.      CLI use of strict mode by default for new projects

3.      A new version of the Ivy language service that provides improved type checking

4.      Tearing down the test module and environment after each test and the revision would significantly improve test speed

 Reference link:

https://angular.io/guide/roadmap

By Anil Singh | Rating of this article (*****)

Popular posts from this blog

nullinjectorerror no provider for httpclient angular 17

In Angular 17 where the standalone true option is set by default, the app.config.ts file is generated in src/app/ and provideHttpClient(). We can be added to the list of providers in app.config.ts Step 1:   To provide HttpClient in a standalone app we could do this in the app.config.ts file, app.config.ts: import { ApplicationConfig } from '@angular/core'; import { provideRouter } from '@angular/router'; import { routes } from './app.routes'; import { provideClientHydration } from '@angular/platform-browser'; //This (provideHttpClient) will help us to resolve the issue  import {provideHttpClient} from '@angular/common/http'; export const appConfig: ApplicationConfig = {   providers: [ provideRouter(routes),  provideClientHydration(), provideHttpClient ()      ] }; The appConfig const is used in the main.ts file, see the code, main.ts : import { bootstrapApplication } from '@angular/platform-browser'; import { appConfig } from ...

Why doesn't App Module exist in Angular 17?

Today, I just started exploring Angular version 17 using ng new and found a problem for the newly created project using the command - ng new. The problem is: Path "/src/app/app.module.ts" does not exist while doing ng add in the Angular project. The ‘ng new’ does not generate app.module.ts in the src root folder Angular CLI 17.0.0. From Angular 17 onwards, standalone is now the new default for the CLI . So when we create a new project ‘ app.module.ts ’ file will not create Path " /src/app/app.module.ts ". Run the following command to create the new project including the file ‘app.module.ts’ in your project: ng new AngularMap  --no-standalone Note: Here ‘AngularMap’ is the project name I created. Standalone components are a feature introduced in Angular version 14. Now the changes applied in angular 17 default, the Angular team strongly recommends using them as they are easier to use, and understand.

25 Best Vue.js 2 Interview Questions and Answers

What Is Vue.js? The Vue.js is a progressive JavaScript framework and used to building the interactive user interfaces and also it’s focused on the view layer only (front end). The Vue.js is easy to integrate with other libraries and others existing projects. Vue.js is very popular for Single Page Applications developments. The Vue.js is lighter, smaller in size and so faster. It also supports the MVVM ( Model-View-ViewModel ) pattern. The Vue.js is supporting to multiple Components and libraries like - ü   Tables and data grids ü   Notifications ü   Loader ü   Calendar ü   Display time, date and age ü   Progress Bar ü   Tooltip ü   Overlay ü   Icons ü   Menu ü   Charts ü   Map ü   Pdf viewer ü   And so on The Vue.js was developed by “ Evan You ”, an Ex Google software engineer. The latest version is Vue.js 2. The Vue.js 2 is very similar to Angular because Evan ...

How To Optimizing Database Performance: Tips and Techniques for Developers

Best Practices for Optimizing Database Performance: Tips and Techniques for Developers Navigating the labyrinth of database performance optimization can often seem like a daunting task for many professionals. Especially for database developers, mastering this critical skill has immense value, as it enhances both the efficiency and responsiveness of their applications.  Effective database performance optimization leads to faster data retrieval and smoother transactions.  A key challenge, however, lies in knowing  how to hire database developers who are well-versed in optimization techniques. The market is flooded with many professionals, but finding the right expert who understands the intricacies of database performance can be like looking for a needle in a haystack. Employers need to seek those who are not only proficient in their craft but also updated with the latest optimization practices. This guide, therefore, not only aims to provide developers with a compre...

SOLID Principle - Dependency Inversion Principle (DIP)

The SOLID Principles are the design principles that enable us to manage several software design problems. These principles provide us with ways to move from tightly coupled code to loosely coupled and encapsulated real business needs properly. Also readable, adaptable, and scalable code. The SOLID Principles  guide developers as they write readable, adaptable, and scalable code or design an application. The SOLID Principles can be applied to any OOP program. The SOLID Principles were developed by computer science instructor and author Robert C. Martin. Now, SOLID principles have also been adopted in both agile development and adaptive software development. The 5 principles of SOLID are: 1.       Single-Responsibility Principle (SRP) 2.       Open-closed principle (OCP) 3.       Liskov Substitution Principle (LSP) 4.       Interface Segregation Principle (ISP) 5.    ...