Logo
Digital Openers
Request a Call: +91-9509040731, 8696105555 Working: Monday - Saturday: 9am - 6:30pm
founder
120
blog images

Web and Mobile applications have become an integral part of our personal and professional lives. This revolutionary change has led various development companies to look for a better option for building mobile & web apps and Angular is one of them.

Angular is a javascript structure that is written in typescript. It was created by Google and dispatched to decouple an application's rationale from DOM control. It is mainstream as "Superheroic JavaScript MVW Framework" for the incredible and astounding highlights that it has.

The incredible features assist designers with making some rich, superior applications without any problem. It is going to stick around for quite some time as it is created by Google. Angular released the latest stable version on the 12th of May, while the current version Angular 11 was launched on November 11. In the analysis of Angular 9 vs 10, we can see their differences in upgradation and deprecation and become a study material for a lot of web app development companies.

In this blog, we are going to study the comparison between Angular 11 vs Angular 12. Let’s have a look at their features and performances and major differences.

Angular 11 Features

Updated Hot Module Replacement (HMR) Support

The Angular v11 of Google-developed web framework is a production release and released on 14th November 2020. Some of the major features of this version include automatic inlining of fonts, router performance improvements, and stricter types. Let’s study more about it:

One of the significant elements of Angular 11 is the Hot Module Replacement component that aides in supplanting the modules without a full program revive. It is an old idea for Angular specialists where the gathering has worked with HMR in the prior variants of Angular. Precise 11 backings HMR with the necessary arrangement and plan and fuses the code so that adjustments of Angular code look not so great. With HMR the movements to pacomponentsrts, styles, and configurations are quickly refreshed into the running application without invigorating the full page.

Updates on Operation Byelog

The Angular gathering has contributed some basic planning effort on Operation Byelog where they focussed on the triaging issues and PRs and having an unrivaled perception of the broad local area needs. With Angular 11, every one of the issues have now been effectively triaged in all of the three monorepos that continue with the new issues that get reported. This cooperation additionally helps with two or three popular worries, all things considered. The issues in Angular 11 will be triaged in around fourteen days from the date of the occasion, which assists with diminishing the size of the Angular excess.

Automatic Inlining of Fonts

Angular 11 highlights programmed text style inlining that happens each time customers banner in the angular.json. Precise inlining helps the Google Fonts to change over in a way that inlines the record HTML. The inline text styles get downloaded in the Angular CLI during gather time that is utilized and is associated in the application. The elements of Angular 11 endeavor the default improvement for the form to run on the CI whenever the web is open.

Component Test Harnesses

The Component Test Harnesses gives a mind blowing and clear API surface that assists with testing the Angular Material parts. It gives a method for managing engineers to talk with Angular Material parts by utilizing the kept up with API while testing. This component was first introduced in Angular 9. The distinction in part Test Harnesses in Angular 9 versus Angular 11 is that Angular 11 goes with an equivalent limit, execution redesigns, and new APIs. The manual change identification work helps the architects with crippling the modified change acknowledgment in unit tests just as profit the better-grained control of progress location.

Updated Language Service Preview

The Angular Language Service in Angular 11 gives steady gadgets to making helpfulness and fun inside the Angular climate. The current kind of language association relies on View Engine that gives much more vital and definite understanding for architects. Rakish 11 changes the standard for the language association to definitively surmise non-restrictive sorts in formats and designs precisely like how the TypeScript compiler does. This component actually being created gives another even more noteworthy and exact Ivy-based language organization.

Angular V11: Breaking Changes and New Deprecations
  • Angular 11 supports Typescript 4.0 and has dropped the support for TypeScript 3.9.
  • The roadmap has been updated allowing the developers to provide early feedback for the final release.
  • Angular 11 has fixed the typing for date and number pipe.
  • The value for an undefined input in the async pipe will not return null anymore.
  • IE 9, 10, and IE mobile browser support is removed.
  • CollectionChangeRecord is deprecated and replaced by IterableChangeRecord.
  • The Angular Universal in Angular 11 vs Angular 12 needs to have the baseUrl parameter for using useAbsoluteUrl baseUrl for overriding the port.
  • Angular 11 has enabled all the strict checks generating the angular application.
  • The extra package.json will no longer be created to avoid confusion in the performance of Angular 11.
  • Angular CLI generator for resolvers will go as ng g r/resolve

Angular 12 Features

Angular version 12 released on 12th May, is the latest and the newest version of the Google-developed web framework as a stable one. Some of the major improvements of this version are improvement in styling, Typescript 4.2, webpack 5 support, etc. Let’s study the features in detail.

Ivy Everywhere

Among numerous censures in the Angular climate, the belittling of the View Engine in Angular 12 is surely the most significant of the multitude of expostulations. This censure will be wiped out in future critical deliveries also. The Ivy wherever alludes to the procedure that pursues the target of consolidating the Angular environment on Ivy. The View Engines are being utilized by the designers, nonetheless, the designers are needing to change to Ivy as quickly as time permits.

Migrating from legacy i18n message IDs

Since Angular variant 11, new errands are ordinarily planned to utilize the new message ids and they at this point have the tooling to move existing undertakings with existing translations. In the current rendition, various heritage message-id plans are being utilized in the i18n framework. These legacy message-ids are delicate as issues can emerge subject to whitespace and the straightening out associations and ICU verbalizations. To deal with this issue the local area is creating some distance from them. The new standard message-id setup is fundamentally more limit and normal. This game plan will diminish the silly understanding refutation and related retranslation cost in applications where translations don't work with due to whitespace changes for instance.

Protractor: planning for future

The destiny of the protractor is currently with the Angular group and the local area. They are presently now examining the info partook in the RFC and sorting out the best future for Protractor. The gathering has chosen to forbid it in new assignments and, considering everything, outfit choices with acclaimed pariah plans in the Angular CLI. The gathering is at this point working with Cypress, WebdriverIO, and TestCafe to help angularjs advancement organization with getting elective courses of action. More data to come as this creates.

Improvements in styling

In Angular v12, Components will have support for inline Sass in the styles field of the @Component decorator. Rakish CDK and Angular Material have accepted Sass' new module framework inside. Assuming that your application utilizes Angular CDK or Angular Material, it is critical to change from hub backtalk to the backtalk npm bundle. The hub backtalk bundle is unmaintained and no longer stays aware of new component increments to the Sass language.

Deprecating support for IE11

The evergreen foundation of Angular recommends that it stays aware of the moving web environment. Killing assistance for heritage programs licenses them to zero in on giving current courses of action and better help to planners and clients. The group has furthermore joined another expostulation cautioning message as another Angular 12 component — and killed support for IE11 in Angular v13.

Support from the Community

The precise local area has moved forward to turn out determinedly for working on the Angular experience. They are continually attempting to further develop the Angular learning experience for planners. As a piece of Angular 12 new features, they have done some colossal moves up to their documentation. They have furthermore revived the angular.io patron's aide that will help individuals needing to work on the docs.

Typescript 4.2

The help of Typescript 4.2 is one of the significant updates of Angular 12.2. It was delivered on the 23rd of February for certain interesting highlights and breaking changes that have affected the designers and Angular 12. A portion of the elements of Typescript 4.2 are changes in tuple types, dynamic develop marks, enhancements for in administrator, further developed sort false name, upgrades to the accumulate cycle.

Nullish Coalescing

This Feature of Angular 12 has assisted engineers with composing cleaner code in TypeScript classes. Precise formats in v12 can in any event, carry the power of nullish combining with the new grammar structure which can be used by the engineers to further develop the complex conditionals.

For instance:{{age !== null && age !== undefined ? age : calculateAge() }}
Becomes:
{{ age ?? calculateAge() }}

New Dev Tools

A few days after the Angular 12 delivery date, the Angular group has definite the availability of Angular Dev Tools for Google Chrome. The embedded profiler can see and record the change acknowledgment occasions which can be checked in regards to which location cycle and parts took the main period of time. Earlier the Angular people group had semi-official Dev Tools which were not practical with Ivy. So this is a commonly useful answer for all.

ng API improvements

The ng investigating API is one of the further developed elements of Angular 12. There are a few functionalities that have been executed explicitly getDirectiveMetadata and esetProfiler to explore APIs for essential audit of uses. The getDirectiveMetadata can be utilized to recover data about parts and mandates. The esetProfiler can be used to follow design creation lengths, lifecycle snares getting ready, and arrangement refreshes. The API additionally can give information into the working of the applications at runtime.

Angular Version 12 vs 11 : Breaking Changes and New Deprecations:
  • The HMR in Angular 11 vs Angular 12 is enabled while initiating an application with ng serve.
  • The automatic lining of Fonts.
  • Improved logging and reporting better CLI readability.
  • minified UMDs are not generating in Ng_package anymore.
  • fine-tuned control is added in routerLinkActiveOptions.
  • The strict mode of Angular 12 vs Angular 11 has now been enabled by default in the CLI.
  • legacy i18n message-ids are no longer generated through linked libraries.
  • Migration from opt-in service to default Ivy-based Language Service. 
  • Improved component tests harness in Angular 12 has now been added.
  • Improved Ng build command as a default to a production build.
  • Http improvements for requests and interceptors, HttpParams and HttpStatusCode.
  • Updated the roadmap for developers to keep them updated about the priorities of the Angular team. 
How to Upgrade Your Angular Application to Latest Version

Here is the quick guide to update your Angular application from angular 11 to angular 12 or the latest version.

Update Angular CLI and Node globally

First, check your current Node version and Angular CLI version. Upgrading Node helps us avoid vulnerability issues and update Angular CLI to the latest stable NPM packages.

Download & Install Latest Node.js version from: https://nodejs.org/en/download/ (for windows)

To install node.js on Linux use the following command:

sudo apt install nodejs

Once installed, verify it by checking the installed version using the command:

node -v or node –version

To install NPM, use the following commands:

sudo apt install npm or npm install -g npm

Upgrade Typescript to the latest version using the following npm command:

npm install -g typescript@latest or
npm update -g typescript

Once installed, verify it by checking the installed version using the command:

tsc -v

Now, we will update the Angular version and package JSON Dependencies using below npm command:

ng update @angular/core@12 @angular/cli@12 or
ng install @angular/cli @angular/core

Install the latest stable version of Angular Material. If you would like to target a specific version, you would have to specify it by adding the version to the end after an @ symbol.

ng update @angular/material

Now it will upgrade your dependencies including typescript v4.2 to Angular 12 or the latest version released i,e Angular 12.2. Now, after this command, whenever you create a new Angular application, it will create with Angular/CLI 12.

The last step is to check and test the unit test case, as the ng update command migrates all the files including .spec.ts.

founder

Comments:

Client
Client
Client