What’s new in Angular 10
First point release of Angular 10 offers fixes and enhancements to address performance regressions, core and router bugs, and more
Angular 10.1.0, a follow-up point release to Angular 10, is now in development, with beta releases arriving with new capabilities and a fix for performance regressions in incremental program reuse.
Angular 10 became generally available as a production release on June 24. The major upgrade TypeScript-based framework puts more emphasis on quality, tool, and ecosystem improvements than new features
Angular version 10 is smaller than previous versions of Angular. New capabilities include a replacement date range picker within the Angular Material UI component library and warnings for CommonJS imports.
In addition, optional stricter settings offer a more-strict project setup when creating a new workspace with ng new, via ng new --strict. Enabling this flag initializes a replacement project with new settings to enhance maintainability, help catch bugs, and permit the CLI to try to advanced optimizations on an app.
How to upgrade current Angular version
|
ng update @angular/cli @angular/core |
Angular 10 Features
- The addition of dependency information and ng-content selectors to metadata. This proposed compiler feature would provide additional metadata useful for tools such as the Angular Language Service, offering the ability to provide suggestions for directives/components defined in libraries.
- Propagation of the correct value span in an ExpressionBinding of a micro syntax expression to ParsedProperty, which in turn would propagate the span to the template ASTs (both VE and Ivy). This proposal also is for the compiler.
- In a fix to the core, logic would be added to undecorated-class migration to decorate derived classes of undecorated classes that use Angular features.
- In a breaking change, Urlmatcher’s type will reflect that it could always return null.
- For the service-worker, a fix has been put in for a situation in which there was a chance that the service worker will never register when there is a long-running task or recurring timeout.
- A number of bug fixes have been made including the compiler avoiding undefined expressions in a holey array and the core avoiding a migration error when a non-existent symbol is imported