The new update of Google’s well-known TypeScript based web App development framework has been launched in the month of May and is currently accessible as a production release. Among various enhancements, the upgrade deprecates the inheritance view engine assemblage and delivering pipelines for the more current Ivy technologies.
A new version of Angular version 12 is accessible on GitHub as well as following various beta deliveries and release candidates. Angular 12 draws nearer to an “Ivy all over” vision for the whole structure. Ivy is represented as a cutting-edge gathering and delivering pipeline as well as offering a quicker AOT compilation.
A group of Angular noticed that the view engine will be taken out in a future delivery. Current libraries of an Angular development utilizing view engine and will in any case of work with Ivy applications. However, the library creators are encouraged to begin transitioning to Ivy.
The current version of Angular was carrying the improvements to composing of regular lines and bug fixes that guarantee TestBed is not started up after the override provider; and It presents updates across the stage including structure, CLI, and components. The latest version of Angular follows similar upgrades with the contribution of stricter types and better router performance.
Features of Angular 12
Protractor: planning for future
The team is working with the community to decide the eventual fate of the Protractor. Now, they are exploring the feedback shared in the RFC and also sorting the best future for the Protractor. This is one of the latest features of Angular 12.
The team has been chosen to exclude it in new tasks and, all things considered, to furnish alternatives with famous 3rd party solutions in Angular CLI. Presently, the team is working with CyPress, WebdriverIO, and TestCafe to assist the AngularJS development company with receiving elective solutions.
Nullish Coalescing is one of the operators that has been assisting engineers with composing cleaner code in TypeScript classes for some time. One of the main things about this feature is that you are able to bring the force of Nullish Coalescing to Angular templates in v12! Now, in templates, developers can utilize the new syntax structure to improve the complex conditionals.
Improvements in styling
Components will have support for inline SAAS in the styles field of the @Component decorator In Angular v12. SAAS was just accessible in outside resources already because of the Angular compiler. You are able to empower this component in your current applications simply by adding one CSS to angular.json. Else, it will be accessible to new tasks utilizing SCSS.
Angular cloud development kit (CDK) and Angular Material have adopted a new module framework of SAAS internally. If your application utilizes Angular CDK or Angular Material, you need to ensure you’ve changed from node-sass to the sass npm package. The node-sass package is unmaintained and no longer stays aware of new feature additions to the SAAS language.
While you updating your application to the angular latest version, It will consequently change to the new SAAS API by refreshing your application with an ng update.
Deprecating support for IE11
Angular is an evergreen platform, implying that it keeps up with the advancing web ecosystem. Eliminating support for the legacy browsers permits us to focus on giving modern solutions and better help to engineers and clients. The team has also included a new deprecation warning message as another feature of Angular 12 — and eliminate support for IE11 in Angular v13.
Strict by default
The strict mode of Angular has now been enabled by the default in the CLI as one of the features of Angular 12. Strict mode improves maintainability and assists you with catching the bugs early in the process. Also, strict mode applications are simple to statically examine and can help the ng update command refactor code more securely and accurately when you are updating to the latest versions of Angular.
Angular 12 features a number of upgrades around its HTTP support. Let’s have a look:
Metadata for Requests and Interceptors
To start with, the HttpClient would now be able to be utilized to store and recover custom metadata for requests. This is helpful for the HTTP interceptors. This capacity can be utilized through the new HttpContext.
Now, the distinctive HTTP strategies are given by HttpClient incorporate another specific circumstance: the HttpContext alternative, which we can use to pass in a map.
Angular 12 features its own list of intelligible names for HTTP status codes, in the form of a const enum. Because of this new element, we are able to now utilize HttpStatusCode instead of introducing our own solution to have human-readable names.
One of the major updates in the feature of Angular 12 is the support of Typescript 4.2. The stable version was released in February. There are some exciting features and breaking changes in this version. Let’s find out the features of Typescript 4.2 and how this version will impact developers and Angular 12.
Angular 12 has arrived with a pile of improvements to its performance, compiler, language service, form validation, and much more. The deprecation of the view engine and incorporation of the Ivy ecosystem is certainly one of the major enhancements considered in version 12. Additionally, Angular 12 features an affecting the compiler, core, variety of bug fixes, router, as well as language service, etc.