Last Updated on March 6, 2023
05 min read
Google is the genius behind the typescript-grounded web operation framework known as Angular. It has made available Angular 14, which is the most recent interpretation. Then, we’ll bandy the upgrades and capabilities that Angular 14 has to offer Angular inventors. Without further ado, let’s get started on it.
Let’s look at the new features that the Angular 14 release brings for all of us first.
By reducing the need for Ng Modules, standalone factors do nothing but speed up the creation of Angular apps. In the inventor exercise of Angular 14, standalone factors are available. Once set, you can use them in your operations for the exploration and development process. However, it’s possible that APIs will not be stable and may change in ways unconnected to the standard backward comity fashion. Also, the frame will continue to develop schematics (like ng new app-name-standalone) and record use cases and the literacy process for this revised, simplified internal model.
The perpetration of strict type for the Angular Reactive Forms Package, which was the top GitHub issue for Angular, is resolved in interpretation 14. The values contained in form controls, groups, and arrays are type-safe over the full API face thanks to compartmented forms. This makes forms safer, especially for complex cases with deep nesting. Sonu Kapoor, Netanel Basel, and Cédric Exbrayat, among others, contributed to the Angular community by prototyping, working, and testing this point specifically in response to public calls for commentary and design reviews. Update schematics allow you to gradationally add codifying to being forms while maintaining full backward comity, aiding in the gradational migration to compartmented forms.
Let’s look at the new features that the Angular 14 release brings for all of us first.
To give you an adaptable foundation that gives you fresh sapience into your templates and how to enhance them, new extended diagnostics have been developed. Diagnostics produces precise, practicable advice for your templates at figure time, discovering crimes before run time.
Then, Angular 14 is prepared to help you in passing commodity that’s plainly made to make you feel comfortable. The erected-in tools in Angular v14, from routing to your law editor, enable inventors to produce high-quality apps. These features are available starting with streamlined revision discovery instructions onangular.io.
Making sure that the runner titles in your operation communicate in a unique way
Another advised stylish practice is to make sure that the runner titles in your operation communicate in a unique way. This is made easier by the new Route.Title trait in the Angular Router in interpretation 13.2. The addition of a title is explosively compartmented and doesn’t bear any fresh significances.
In a two-way list, flipping the classes and hiatuses, iting (()) rather (()), is a typical inventor alphabet error. It was dubbed the “banana in a box” error because the banana should go in the box and () kind of resembles a banana and () kind of resembles a box.
The framework’s CLI can accept that this error is only sometimes what inventors prepare for as it’s technically correct syntax. The preface of thorough messaging on this error and instructions on how to fix it, both within the CLI and your law editor, was made in the v13.2 release.
There are new runtime fault canons included in this interpretation of Angular 14. Strong error canons make it fairly easy and quick to identify and relate to information on how to remedy your crimes. This makes it possible to produce an optimizer that retains error canons while tree-shaking lengthy strings of error dispatches from product packets.
When troubleshooting a product issue, Angular advises consulting the Angular reference volumes and bluffing the error in a development terrain. Developers will continue to gradationally restructure being miscalculations in order to use this revised syntax in coming editions.
Also, crimes for meaningless nullish coalescing drivers(??) in Angular templates are caused by extended diagnostics. This issue specifically appears when the input is “nullable,” meaning that its type doesn’t include null or undetermined.
During ng figure, ng serves, and in real-time with the Angular Language Service, extended diagnostics are displayed as warnings. It’s possible to configure the diagnostics in tsconfig.json, where it’s possible to specify whether to treat diagnostics as a warning, error, or repression.
Angular 14 has TypeScript 4.7 support and now by default targets ES2020, allowing the CLI to compile lower code without down leveling. Additionally, Angular 14 should emphasize the following three featurettes:
You may now directly bind defended element members from your templates in Angular. This gives you further control over the applicable factors’ public API face.
When creating an embedded view using ViewContainerRef.createEmbeddedView and TemplateRef.createEmbeddedView, Angular 14 now supports specifying a voluntary injector. The injector also makes it possible for the dependence geste within the particular template to be customized.
Last but not least, a community donation resolves a major problem and guarantees that updates to NgModel are reflected in the UI for OnPush factors.
The Angular CLI has better thickness thanks to standardized CLI argument parsing, and every flag now uses the-lower-skewer-case format. Disapproved camel case arguments support has been removed from Angular 14 and use support for mixed aliases has been added.
Real-time bus-completion for commands like ng serve has been included in Angular 14. Typos are one of the main causes of command-line crimes every time you encounter one. But Angular 14 has released a new ng completion and added real-time type-ahead autocompletion to address this problem! The CLI’ll prompt you to choose to conclude-in to autocomplete during your first command prosecution in Angular 14 to make sure that all Angular inventors are apprehensive of this.
All credit for the offline functionality in the Angular DevTools debugging extension goes to Keith Li for his community effort. Users of Firefox can locate the extension under the Mozilla Add-ons section.
To install Angular v14 using npm, use the following command-line interface:
npm install -g @angular/cli@latestAfter that, execute the command below to install the latest version of Angular:
ng new my-angular-projectYou can quickly install the Angular CLI version that everyone is using with this command on your development workstation.
You can upgrade from Angular 13 to Angular 14 by following this guide:
Now that you are familiar with the capabilities of Angular 14, you must be eager to use them in your development process. We will return to this topic if Google surprises us with another Angular release.
