Angular 8 vs Angular 7 vs Angular 6 - What's New In Angular 6, 7, 8 Features?

What’s New In Angular 8?

Angular 8 being smaller, faster and easier to use and it will making Angular developers life easier. Angular version numbers have three parts: major.minor.patch. 

This release contains the following added and Improvements over the entire Angular platform including:-

=> Added Support for TypeScript 3.2

=> Added a Navigation Type Available during Navigation in the Router

=> Added pathParamsOrQueryParamsChange mode for runGuardsAndResolvers in the Router

=> Allow passing state to routerLink Directives in the Router

=> Allow passing state to NavigationExtras in the Router

=> Restore whole object when navigating back to a page managed by Angular Router

=> Added support for SASS

=> Resolve generated Sass/Less files to .css inputs

=> Added Predicate function mode for runGuardsAndResolvers:-

This option means guards and resolvers will ignore changes when a provided predicate function returns `false`. This supports use cases where an application needs to ignore some param updates but not others.

For example, changing a sort param in the URL might need to be ignored, whereas changing the `project` param might require re-run of guards and resolvers.

=> Added functionality to mark a control and its descendant controls as touched: - add markAllAsTouched () to AbstractControl

=> Added ng-new command that builds the project with Bazel

=> Use image based cache for windows BuildKite

=> Export NumberValueAccessor & RangeValueAccessor directives

=> Use shared DomElementSchemaRegistry instance for improve performance of platform-server(@angular/platform-server):-

Right now the ServerRendererFactory2` creates a new instance of the `DomElementSchemaRegistry` for each and every request, which is quite costly (for the Tour of Heroes SSR example this takes around **15%** of the overall execution time)

=> Now the Performance Improvements on core, more consistent about “typeof checks”: -

When testing whether `value` is an object, use the ideal sequence of strictly not equal to `null` followed by `typeof value === 'object'` consistently. Specifically there's no point in using double equal with `null` since `undefined` is ruled out by the `typeof` check.

Also avoid the unnecessary ToBoolean check on `value.ngOnDestroy` in `hasOnDestroy()`, since the `typeof value.ngOnDestroy === 'function'` will only let closures pass and all closures are truish (with the notable exception of `document.all`, but that shouldn't be relevant for the `ngOnDestroy` hook)

=> In the Compiler-CLI, expose ngtsc as a TscPlugin

=> Restore whole object when navigating back to a page managed by Angular Router:-

This feature adds a few capabilities. First, when a `popstate` event fires the value of `history.state` will be read and passed into `NavigationStart`. In the past, only the `navigationId` would be passed here.

Additionally, `NavigationExtras` has a new public API called `state` which is any object that will be stored as a value in `history.state` on navigation.

For example, the object `{foo: 'bar'}` will be written to `history.state` here: -`router.navigateByUrl('/simple', {state: {foo: 'bar'}});`

What’s New In Angular 7?

Angular 7 being smaller, faster and easier to use and it will making developers life easier.  Now Angular 7 is released! This is a major release and expanding to the entire platform including-

1.      Core framework,

2.      Angular Material,

3.      CLI

Many  of new things are added in Angular 7 and also many of us will curious to know these new features and bug fixes.

Let’s introduce added and modified new features of Angular 7 -

1.      Added a new interface - UrlSegment[] to CanLoad interface

2.      Added a new interface -  DoBootstrap interface

3.      Angular 7 added a new compiler - Compatibility Compiler (ngcc)

4.      Introduce a new Pipe called - KeyValuePipe

5.      Angular 7 now supporting to TypeScript 2.9.

6.      Added a new elements features - enable Shadow DOM v1 and slots

7.      Added a new router features - warn if navigation triggered outside Angular zone

8.      Added a new mappings for ngfactory  and ngsummary files to their module names in AOT summary resolver.

9.      Added a new "original" placeholder value on extracted XMB

10. Added a new ability to recover from malformed URLs

11. Added a new compiler support dot (.) in import statements and also avoid a crash in ngc-wrapped

12. Update compiler to flatten nested template fns

How to update to Angular 7?

For updating Angular 6 to Angular 7, you should use a command -

ng update @angular/cli @angular/core

For more detail click on link - https://update.angular.io/

Explore in detail - What's New In Angular 7? Let’s Introduce Angular 7 New Features! 

Angular Future Releases –

Date	Stable Release	Compatibility*
September/October 2018	7.0.0	^6.0.0
March/April 2019	8.0.0	^7.0.0

Angular 6 frameworks is now feature complete, the CLI and Material/CDK parts of the v6 release and other integrations are still in works and It will be completed by the time.

Angular Team are working on lots of bug fixes, new features and added/update/remove/ re-introduce/ and may more things.

Let’s start to explore all changes of Angular 6 step by step!

Added ng update - This CLI commands will update your angular project dependencies to their latest versions. The ng update is normal package manager tools to identify and update other dependencies.

ng update

Angular 6 uses RxJS 6 - this is the third-party library (RxJS) and introduces two important changes as compared to RxJS 5.

1.      RxJS 6 introduces a new internal package structure

2.      Operator concept

Both are requires you to update your existing code

To update to RxJS 6, you simply run -

npm install --save rxjs@6

Simply run the blow command and update your existing Angular project-

npm install --save rxjs-compat

Alternatively, you can use the command - ng update rxjs to update RxJS and install the rxjs-compat package automatically.

RxJS 6 Related import paths -

Instead of -

import { Observable } from 'rxjs/Observable';

import { Subject } from 'rxjs/Subject';

Use a single import -

import { Observable, Subject } from 'rxjs';

So all from rxjs/Something imports become from one 'rxjs'

Operator imports have to change -

Instead of

import 'rxjs/add/operator/map';

import 'rxjs/add/operator/throttle';

Now you can use -

import { map, throttle } from 'rxjs/operators';

And

Instead of

import 'rxjs/add/observable/of';

Now you can use -

import { of } from 'rxjs';

RxJS 6 Changes - Changed Operator Usage

Instead of-

import 'rxjs/add/operator/map';

import 'rxjs/add/operator/throttle';

yourObservable.map(data => data * 2)

.throttle(...)

.subscribe(...);

You can use the new pipe () method,

import { map, throttle } from 'rxjs/operators';

yourObservable

  .pipe(map(data => data * 2), throttle(...))

  .subscribe(...);

CLI update and added a new project config file - Instead of “.angular-cli.json” using “angular.json”

Now in Angular 6 new projects use an “angular.json” file instead of “.angular-cli.json” file.

ng update @angular/cli --from=1 --migrate-only

The above command helps you to update your existing “.angular-cli.json” file to the new “angular.json” file.

The “angular.json” file contains the Properties -

1.      Version - This is integer file format version and it is currently 1.

2.      newProjectRoot - This is string path where new projects will be created.

3.      defaultProject - This is default project name used in commands.

4.      CLI - This is workspace configuration options for Angular CLI and it contains

a.      defaultCollection

b.      packageManager

c.       warnings

d.      And so on.

5.      Schematics - This is configuration options for Schematics.

6.      Projects - This is configuration options for each project in the workspace and it contains

a.      root

b.      sourceRoot

c.       projectType

d.      prefix

e.      schematics

f.        Architect - This is the project configuration for Architect targets.

The <template> deprecated, Now Angular 6 introduce <ng-template> –

Now in Angular 6, you should use <ng-template> instead of <template>

For example, previously you are using

<template [ngIf]="IsAdmin">

  <p>This template renders only if IsAdmin is true.</p>

</template>

Now in Angular 6, you should use <ng-template> instead of <template>

<ng-template [ngIf]="IsAdmin">

  <p>This template renders only if IsAdmin is true.</p>

</ng-template>

Service level changes (the way of marking a service as global) -

In the earlier versions, if you want to provide a service to the entire application –you should add it to providers [] in the AppModule but in the Angular 6 released you should not add in the providers [] in the AppModule.

Example for marking a service as global -

Instead of

//my.service.ts

export class MyService { }

//In app.module.ts

//JavaScript imports services

import { MyService } from './my-serice.service';

//AppModule class with the @NgModule decorator

@NgModule({

  declarations: [],

  providers: [MyService] //My services instances are now available across the entire app.

})

export class AppModule {

   //exporting app module

}

Use with Angular 6 released-

//my.service.ts

@Injectable({providedIn: 'root'})

export class MyService { }

@NgModule({

  declarations: [],

  providers: [] // Service does not need to be added here

})

export class AppModule {}

The second one obviously saves you some lines of code as compare to previous code.

Angular 6 introduces Angular Elements -

The elements are a feature that allows you to compile Angular components to native web components which you can use in your Angular application.

An angular element is a package which is part of the Angular framework @angular/elements.

For more detail kindly refer the click to Angular Elements

Angular 6 introduces new Ivy Renderer -

The new Ivy renders and it’s not stable for now and it’s only in beta version. It will stable in future for production.

Ivy Renderer is new rendering engine which is designed to be backward compatible with existing render and focused to improve the speed of rendering and it optimizes the size of the final package. 

The main goal of Ivy render is to speed up its loading time and reduce the bundle size of your applications. Also for uses a different approach for rendering Angular components.

For Angular, this will not be default renderer, but you can manually enable it in compiler options. 

Bazel Compiler -

The Bazel Complier is a build system used for nearly all software built at Google.

From Angular 6 release, will start having the Bazel compiler support and when you compile the code with Bazel Compiler, you will recompile entire code base, but it compiles only with necessary code.

The Bazel Complier uses advanced local and distributed caching, optimized dependency analysis and parallel execution.

For more detail kindly refer the Angular 6

Replace Context, Record and Injectors -

Replace ngOutletContext with ngTemplateOutletContext

Replace CollectionChangeRecord with IterableChangeRecord

Now use Renderer2, Instead of Renderer

Now use StaticInjector, Instead of ReflectiveInjector,

Angular 6 Renamed Operators -

The lists of renamed operators are –

1.      do() => tap()

2.      catch() => catchError()

3.      finally() => finalize()

4.      switch() => switchAll()

5.      throw() => throwError()

6.      fromPromise() => from()

Angular 6 introduces multiple validators for array method of FormBuilder –

import { Component } from '@angular/core';

import {FormsModule, FormBuilder, FormGroup} from '@angular/forms';

constructor(private fb: FormBuilder) {}

myForm: FormGroup;

ngOnInit() {

  this.myForm = this.fb.group({

      text: ['', Validators.required],

      options: this.fb.array([], [MyValidators.minCount, MyValidators.maxCount])

  });

}

Updates on NgModelChange - Now emitted after value and validity is updated on its control. Previously, it was emitted before updated.

Previously  -

<input [(ngModel)]="name" (ngModelChange)="onChange($event)">

And

onChange(value) {

  console.log(value);   // would log the updated value, not old value

}

Now Use -

<input #modelDir="ngModel" [(ngModel)]="name" (ngModelChange)="onChange(modelDir)">

And

onChange(NgModel: NgModel) {

  console.log(NgModel.value);// would log old value, not updated value

}

Let’s see in depths - https://www.code-sample.com/2018/01/whats-new-in-angular-6.html

I hope you are enjoying with this post! Please share with you friends. Thank you so much!