Difference between revisions of "Angular Js 5"
(Created page with "==Angular 5 Release: What's New?== Angular is an all-encompassing JavaScript framework that is frequently used by developers all over the world for building web, desktop, and...") |
|||
Line 60: | Line 60: | ||
</source> | </source> | ||
+ | |||
+ | ====Improved Decorator Support in Angular 5==== | ||
+ | Angular 5 now supports expression lowering in decorators for lambdas, and the value of useValue, useFactory, and data in object literals. Furthermore, a lambda can be used instead of a named function like so: | ||
+ | |||
+ | In Angular 5: | ||
+ | <source> | ||
+ | |||
+ | Component({ | ||
+ | provider: [{provide: 'token', useFactory: () => null}] | ||
+ | }) | ||
+ | export class MyClass {} | ||
+ | </source> | ||
+ | |||
+ | Before Angular 5 | ||
+ | <source> | ||
+ | Component({ | ||
+ | provider: [{provide: 'token', useValue: calculated()}] | ||
+ | }) | ||
+ | export class MyClass {} | ||
+ | </source> | ||
+ | |||
+ | ====Build Optimization==== | ||
+ | The Angular team focused on making Angular 5 faster, smaller, and easier to use. In Angular 5, production builds created with the Angular CLI will now apply to the build optimizer by default. The build optimizer removes Angular decorators from your app's runtime codes thereby reducing the size of your bundle and increasing the boot speed of your application. In addition, the build optimizer removes part of your application that is not needed during runtime via tree-shaking. This action leads to a decreased bundle size and faster application speed. | ||
+ | |||
+ | ====Angular Universal Transfer API==== | ||
+ | The Angular Universal team has added Domino to the platform-server. This simply means more DOM manipulations can happen out of the box within server-side contexts. | ||
+ | |||
+ | Furthermore, two modules, ServerTransferStateModule and BrowserTransferModule have been added to Angular Universal. These modules allow you to generate information as part of your rendering with platform-server and then transfer it to the client side to avoid regeneration of the same information. In summary, it transfers state from the server which means developers do not need to make a second HTTP request once the application makes it to the client. | ||
+ | |||
+ | ====Faster Compiler in Angular 5==== | ||
+ | A lot of improvements have been made to the Angular compiler to make it faster. The Angular compiler now leverages TypeScript transforms. You can take advantage of it by running: | ||
+ | <source> | ||
+ | ng serve --aot | ||
+ | </source> | ||
+ | |||
+ | Angular.io was used as a case study and the compiler pipeline saved 95% of the build time when an incremental AOT build was performed on it. | ||
+ | |||
+ | ====Forms Validation in Angular 5==== | ||
+ | In Angular 5, forms now have the ability to decide when the validity and value of a field or form are updated via on blur or on submit, instead of every input event. | ||
+ | |||
+ | Example Usage : | ||
+ | <source> | ||
+ | <input name="nickName" ngModel [ngModelOptions]="{updateOn: 'blur'}"> | ||
+ | </source> | ||
+ | |||
+ | Another Example: | ||
+ | <source> | ||
+ | <form [ngFormOptions]="{updateOn: 'submit'}"> | ||
+ | </source> | ||
+ | |||
+ | In the case of Reactive forms, you can add the option like so: | ||
+ | |||
+ | <source> | ||
+ | ngOnInit() { | ||
+ | this.newUserForm = this.fb.group({ | ||
+ | userName: ['Bob', { updateOn: 'blur', validators: [Validators.required] }] | ||
+ | }); | ||
+ | } | ||
+ | </source> | ||
+ | |||
+ | ====Animations in Angular 5==== | ||
+ | In Angular 5, we have two new transition aliases, :increment and :decrement. | ||
+ | |||
+ | <source> | ||
+ | |||
+ | ... | ||
+ | animations: [ | ||
+ | trigger('bannerAnimation', [ | ||
+ | transition(":increment", group([ | ||
+ | query(':enter', [ | ||
+ | style({ left: '100%' }), | ||
+ | animate('0.5s ease-out', style('*')) | ||
+ | ]), | ||
+ | query(':leave', [ | ||
+ | animate('0.5s ease-out', style({ left: '-100%' })) | ||
+ | ]) | ||
+ | ])), | ||
+ | transition(":decrement", group([ | ||
+ | query(':enter', [ | ||
+ | style({ left: '-100%' }), | ||
+ | animate('0.5s ease-out', style('*')) | ||
+ | ]), | ||
+ | query(':leave', [ | ||
+ | animate('0.5s ease-out', style({ left: '100%' })) | ||
+ | ]) | ||
+ | ])), | ||
+ | ]) | ||
+ | ] | ||
+ | </source> | ||
+ | |||
+ | Animation queries now support negative limits, in which case elements are matched from the end rather than from the beginning like so: | ||
+ | |||
+ | <source> | ||
+ | ... | ||
+ | animations: [ | ||
+ | trigger( | ||
+ | 'myAnimation', | ||
+ | [ | ||
+ | transition( | ||
+ | '* => go', | ||
+ | [ | ||
+ | query( | ||
+ | '.item', | ||
+ | [ | ||
+ | style({opacity: 0}), | ||
+ | animate('1s', style({opacity: 1})), | ||
+ | ], | ||
+ | {limit: -3}), | ||
+ | ]), | ||
+ | ]), | ||
+ | ] | ||
+ | ... | ||
+ | </source> | ||
+ | |||
+ | |||
+ | ====New Router Lifecycle Events in Angular 5==== | ||
+ | Some new lifecycle events have been added to the router. The events are GuardsCheckStart, ChildActivationStart, ActivationStart, GuardsCheckEnd, ResolveStart, ResolveEnd, ActivationEnd, and ChildActivationEnd. With these events, developers can track the cycle of the router from the start of running guards through to completion of activation. | ||
+ | |||
+ | Furthermore, you can now configure the router to reload a page when it receives a request to navigate to the same URL. | ||
+ | <soource> | ||
+ | providers: [ | ||
+ | // ... | ||
+ | RouterModule.forRoot(routes, { | ||
+ | onSameUrlNavigation: 'reload' | ||
+ | }) | ||
+ | ] | ||
+ | </source> | ||
+ | |||
+ | ====Better Support for Service Workers in Angular 5==== | ||
+ | |||
+ | In Angular 5, we have better support for service workers via the[@angular/service-worker](https://github.com/angular/angular/tree/master/ | ||
+ | |||
+ | packages/service-worker)package. The service worker package is a conceptual derivative of the @angular/service-worker package that was maintained at github.com/angular/mobile-toolkit, but has been rewritten to support use-cases across a much wider variety of applications. |
Revision as of 06:08, 28 June 2018
Contents
- 1 Angular 5 Release: What's New?
- 1.1 What's New?
- 1.1.1 Http Deprecated, HttpClient Here to Stay
- 1.1.2 Support for Multiple Export Alias in Angular 5
- 1.1.3 Internationalized Number, Date, and Currency Pipes
- 1.1.4 Improved Decorator Support in Angular 5
- 1.1.5 Build Optimization
- 1.1.6 Angular Universal Transfer API
- 1.1.7 Faster Compiler in Angular 5
- 1.1.8 Forms Validation in Angular 5
- 1.1.9 Animations in Angular 5
- 1.1.10 New Router Lifecycle Events in Angular 5
- 1.1.11 Better Support for Service Workers in Angular 5
- 1.1 What's New?
Angular 5 Release: What's New?
Angular is an all-encompassing JavaScript framework that is frequently used by developers all over the world for building web, desktop, and mobile applications. In this article, I'll cover the new features in Angular 5 and several other changes and deprecations.
Angular is built and maintained by Google. It is a platform that combines declarative templates, dependency injection, end-to-end tooling, and integrated best practices to solve development challenges. Web platforms such as Google Adwords, Google Fiber, Adsense, and Winc use Angular to build their user interfaces.
Angular 5 was announced to the world on November 1, 2017. The previous Angular version was 4.4.0. This release focused on making Angular smaller and faster to use. Let's go through the major changes in version 5.
What's New?
Http Deprecated, HttpClient Here to Stay
Before version 4.3, the @angular/http module was used for making HTTP requests in Angular applications. The Angular team has now deprecated Http in version 5. The HttpClient API from @angular/common/http package that shipped in version 4.3 is now recommended for use in all apps. The HttpClient API features include:
- Typed, synchronous response body access, including support for JSON body types.
- JSON is an assumed default and no longer needs to be explicitly parsed.
- Interceptors allow middleware logic to be inserted into the pipeline.
- Immutable request/response objects.
- Progress events for both request upload and response download.
- Post-request verification and flush-based testing framework.
import { HttpClientModule } from '@angular/common/http';
Support for Multiple Export Alias in Angular 5
In Angular 5, you can now give multiple names to your components and directives while exporting. Exporting a component with multiple names can help your users migrate without breaking changes.
Example Usage:
import { Component } from '@angular/core';
@Component({
selector: 'app-root',
templateUrl: './app.component.html',
styleUrls: ['./app.component.css'],
exportAs:'dashboard, logBoard'
})
export class AppComponent {
title = 'app';
}
Internationalized Number, Date, and Currency Pipes
Angular 5 ships with new number, date, and currency pipes that increase standardization across browsers and eliminate the need for i18n polyfills. The pipes rely on the CLDR to provide extensive locale support and configurations for any locales you want to support. To use the old pipes, you will have to import the DeprecatedI18NPipesModule after the CommonModule.
import { NgModule } from '@angular/core';
import { CommonModule, DeprecatedI18NPipesModule } from '@angular/common';
@NgModule({
imports: [
CommonModule,
// import deprecated module after
DeprecatedI18NPipesModule
]
})
export class AppModule { }
Improved Decorator Support in Angular 5
Angular 5 now supports expression lowering in decorators for lambdas, and the value of useValue, useFactory, and data in object literals. Furthermore, a lambda can be used instead of a named function like so:
In Angular 5:
Component({
provider: [{provide: 'token', useFactory: () => null}]
})
export class MyClass {}
Before Angular 5
Component({
provider: [{provide: 'token', useValue: calculated()}]
})
export class MyClass {}
Build Optimization
The Angular team focused on making Angular 5 faster, smaller, and easier to use. In Angular 5, production builds created with the Angular CLI will now apply to the build optimizer by default. The build optimizer removes Angular decorators from your app's runtime codes thereby reducing the size of your bundle and increasing the boot speed of your application. In addition, the build optimizer removes part of your application that is not needed during runtime via tree-shaking. This action leads to a decreased bundle size and faster application speed.
Angular Universal Transfer API
The Angular Universal team has added Domino to the platform-server. This simply means more DOM manipulations can happen out of the box within server-side contexts.
Furthermore, two modules, ServerTransferStateModule and BrowserTransferModule have been added to Angular Universal. These modules allow you to generate information as part of your rendering with platform-server and then transfer it to the client side to avoid regeneration of the same information. In summary, it transfers state from the server which means developers do not need to make a second HTTP request once the application makes it to the client.
Faster Compiler in Angular 5
A lot of improvements have been made to the Angular compiler to make it faster. The Angular compiler now leverages TypeScript transforms. You can take advantage of it by running:
ng serve --aot
Angular.io was used as a case study and the compiler pipeline saved 95% of the build time when an incremental AOT build was performed on it.
Forms Validation in Angular 5
In Angular 5, forms now have the ability to decide when the validity and value of a field or form are updated via on blur or on submit, instead of every input event.
Example Usage :
<input name="nickName" ngModel [ngModelOptions]="{updateOn: 'blur'}">
Another Example:
<form [ngFormOptions]="{updateOn: 'submit'}">
In the case of Reactive forms, you can add the option like so:
ngOnInit() {
this.newUserForm = this.fb.group({
userName: ['Bob', { updateOn: 'blur', validators: [Validators.required] }]
});
}
Animations in Angular 5
In Angular 5, we have two new transition aliases, :increment and :decrement.
...
animations: [
trigger('bannerAnimation', [
transition(":increment", group([
query(':enter', [
style({ left: '100%' }),
animate('0.5s ease-out', style('*'))
]),
query(':leave', [
animate('0.5s ease-out', style({ left: '-100%' }))
])
])),
transition(":decrement", group([
query(':enter', [
style({ left: '-100%' }),
animate('0.5s ease-out', style('*'))
]),
query(':leave', [
animate('0.5s ease-out', style({ left: '100%' }))
])
])),
])
]
Animation queries now support negative limits, in which case elements are matched from the end rather than from the beginning like so:
...
animations: [
trigger(
'myAnimation',
[
transition(
'* => go',
[
query(
'.item',
[
style({opacity: 0}),
animate('1s', style({opacity: 1})),
],
{limit: -3}),
]),
]),
]
...
New Router Lifecycle Events in Angular 5
Some new lifecycle events have been added to the router. The events are GuardsCheckStart, ChildActivationStart, ActivationStart, GuardsCheckEnd, ResolveStart, ResolveEnd, ActivationEnd, and ChildActivationEnd. With these events, developers can track the cycle of the router from the start of running guards through to completion of activation.
Furthermore, you can now configure the router to reload a page when it receives a request to navigate to the same URL. <soource> providers: [
// ... RouterModule.forRoot(routes, { onSameUrlNavigation: 'reload' })
] </source>
Better Support for Service Workers in Angular 5
In Angular 5, we have better support for service workers via the[@angular/service-worker](https://github.com/angular/angular/tree/master/
packages/service-worker)package. The service worker package is a conceptual derivative of the @angular/service-worker package that was maintained at github.com/angular/mobile-toolkit, but has been rewritten to support use-cases across a much wider variety of applications.