Now that the Angular version 10.0.0 is here, we are providing you exclusive details of what makes this version better than its predecessors. Angular 9.0 released 4 months ago, but the new version release includes changes in the entire platform that includes the framework, the CLI, and the Angular Material. Angular 10 is a superior upgrade compared to the previous versions. The popular web development framework puts additional emphasis on tools, quality, and ecosystem improvements. The feature upgrades have been minimal compared to the previous versions but performance and capabilities are sure to increase thanks to this type-script based Google framework
A look at what’s new
New Date range picker
We have given the image of the new Date Range Picker of Angular 10 version.
What’s special about the new Date range picker is that it will allow users to pick a range of dates instead of a single date. End-users can now make use of mat-date-range picker components that carry an almost similar working pattern like mat-datepicker and the basic date-picker input. The input components need two input values for both start and end dates as given below:
The component is the new pop-up module to select dates offering an almost equivalent functionality as compared to
The users have to connect the range picker and range input with the rangePicker component:
Now that Angular version 10 is here, we cannot help but talk about how strict and more granular the project set-up has become thanks to Ng-New.
When the above command is flagged, the new project gets started with new settings that heighten the intensity of overall flexibility and easy maintenance. If there are bugs, it warns the user much ahead of its occurrences. It lets CLI perform advanced optimizations on your application with great functionalities like:
- The moment the project is flagged in the strict mode, it also gets enabled in TypeScript
- Bundle Budgets have considerably reduced
- Tree-shaking relieves the bundle of unused codes
Common JS imports warning
Common JS is nothing but the module formatting system which are small bits of codes included in a particular file and exported to another file present in the system. CommonJS comes with a dependency that paves the way for a slower application, not at all required in today’s faster working environments. Angular developers are of the opinion that it is much better to choose the ECMAScript module or ESM bundle if there are warnings for dependencies.
Novel updates everyone should know
The updates look like these:
- TSLib is the runtime library for TypeScript that has been updated to V2.0. which has all the TypeScript helper functions.
- TSLint is the extensible static tool that checks TypeAScript Code for readability and errors if there are any. The systems so generated are unique because they can be customized with the innate lint configurations, rules, and formatters. This functionality has been further augmented to V6.
- The Primary language for Angular Application and its typescript is the superset of JS and has design-time support for type safety. Under the Angular 10 version, Typescript has now been expanded to Typescript 3.9. In this version. When Angular 9 name the typescript 3.7 support which was further augmented to 3.8 in Angular V3.91 version. This version’s typescript comes with great performance improvements meaning that larger projects that use Angular are going to get benefited with this update. Developers can get their hands on the latest Typescript features and trouble-fixes with a grander configuration.
The layout of the project has undergone a major transformation. A new
Even the project layout has been updated. A completely new will help with putting newer tsconfig.json files which will provide excellent functionality and will build better tooling resolve type and configuration.
Newer projects will benefit from the updated configurations that Angular 10 gives. The older and stagnant browsers will be shown the exit door. A comparison of V9 and V10 defaults can be seen from the illustrations below:
As can be seen, this can possibly disable the ES5 building by default for new projects. In order to ensure builds for browsers like IE or UC then more browsers can be added in the .browserslistrc file.
What has been taken off the version
The earlier versions of Angular used to compile static method returns with type without the necessity for generic type due to the influence of files that possess the requisite information for compilation. But right after Ivy, since this is not required as a compulsion, Angular checks the generic type helping it for type validation.
The earlier applications took the benefit of inheritance from classes that used Angular features like decorators and dependency injections. But now they will have to decorate base classes also. If these classes are not decorated an error of the missing decorator will be displayed on the parent. Let us see how this happens.
As per the error made on the missing directive decorator, the error message will be:
points out that the result of Pipe transformation has undergone a change even when the reference has not changed. It is deprecated and could be removed when the version 12 arrives. errors as Angular development will not show any error when wrapped values were analyzed as equal.
The increased complexities and larger bundle sizes have led to the deprecation for the support of IE9, IE10 & IE10 mobile.
Due to the increased bundle size and heightened complexities, the support for IE9, IE10, and IE Mobile has been deprecated. This will eventually be dropped in other versions.
Splendid features of Angular 10
- Compiler interface is now a part which compiles the actual NGTSC compiler, a language-specific interface that administers and controls multiple typecheck fuels with scripotinfos and interface.
- Browser configurations for newer applications have become a part of the new version while the older browsers have been removed with IE9,10 and IE mobile support deprecated.
- The new version does not include ESM5 OR FESM5 bundles which has great benefits in the long term because it saves a lot of time in downloads and installation while concurrently running npm and install for angular packages.
- The version has also relived the autocompletion from HTML entities. & also has been removed because it has lacked in performance and has not really added value.
- As we have seen earlier Typescript3.9 is a part of the new version which is one of the biggest changes in features. The new compiler feature will render the tool with additional metadata which is required for Angular Language service which provides suggestions for directives expressed fairly in the library.
- The entry point manifest also has been reduced thereby leading to better performances. Entrypoint manifest now will conduct caching dependencies which will be directly read instead of any need for computation.
- The closure compiler in this version has called for advanced optimizations. The usage of Angular packages have been optimized directly from the sources instead of versions found on NPM