Click ⭐if you like the project. Pull Request are highly appreciated. Follow me @SudheerJonna for technical updates.
-
Angular is a TypeScript-based open-source front-end platform that makes it easy to build applications with in web/mobile/desktop. The major features of this framework such as declarative templates, dependency injection, end to end tooling, and many more other features are used to ease the development.
-
Angular is a completely revived component-based framework in which an application is a tree of individual components.
Some of the major difference in tabular form
AngularJS Angular It is based on MVC architecture This is based on Service/Controller This uses use JavaScript to build the application Introduced the typescript to write the application Based on controllers concept This is a component based UI approach Not a mobile friendly framework Developed considering mobile platform Difficulty in SEO friendly application development Ease to create SEO friendly applications -
TypeScript is a typed superset of JavaScript created by Microsoft that adds optional types, classes, async/await, and many other features, and compiles to plain JavaScript. Angular built entirely in TypeScript and used as a primary language. You can install it globally as
npm install -g typescriptLet's see a simple example of TypeScript usage,
function greeter(person: string) { return "Hello, " + person; } let user = "Sudheer"; document.body.innerHTML = greeter(user);
The greeter method allows only string type as argument.
-
The main building blocks of an Angular application is shown in the below diagram
-
Angular has the below key components,
- Component: These are the basic building blocks of angular application to control HTML views.
- Modules: An angular module is set of angular basic building blocks like component, directives, services etc. An application is divided into logical pieces and each piece of code is called as "module" which perform a single task.
- Templates: This represent the views of an Angular application.
- Services: It is used to create components which can be shared across the entire application.
- Metadata: This can be used to add more data to an Angular class.
-
Directives add behaviour to an existing DOM element or an existing component instance.
import { Directive, ElementRef, Input } from '@angular/core'; @Directive({ selector: '[myHighlight]' }) export class HighlightDirective { constructor(el: ElementRef) { el.nativeElement.style.backgroundColor = 'yellow'; } }
Now this directive extends HTML element behavior with a yellow background as below
<p myHighlight>Highlight me!</p>
-
Components are the most basic UI building block of an Angular app which formed a tree of Angular components. These components are subset of directives. Unlike directives, components always have a template and only one component can be instantiated per an element in a template. Let's see a simple example of Angular component
import { Component } from '@angular/core'; @Component ({ selector: 'my-app', template: ` <div> <h1>{{title}}</h1> <div>Learn Angular6 with examples</div> </div> `, }) export class AppComponent { title: string = 'Welcome to Angular world'; }
-
In a short note, A component(@component) is a directive-with-a-template.
Some of the major differences are mentioned in a tabular form
Component Directive To register a component we use @Component meta-data annotation To register directives we use @Directive meta-data annotation Components are typically used to create UI widgets Directive is used to add behavior to an existing DOM element Component is used to break up the application into smaller components Directive is use to design re-usable components Only one component can be present per DOM element Many directives can be used per DOM element @View decorator or templateurl/template are mandatory Directive doesn't use View -
A template is a HTML view where you can display data by binding controls to properties of an Angular component. You can store your component's template in one of two places. You can define it inline using the template property, or you can define the template in a separate HTML file and link to it in the component metadata using the @Component decorator's templateUrl property. Using inline template with template syntax,
import { Component } from '@angular/core'; @Component ({ selector: 'my-app', template: ' <div> <h1>{{title}}</h1> <div>Learn Angular</div> </div> ' }) export class AppComponent { title: string = 'Hello World'; }
Using separate template file such as app.component.html
import { Component } from '@angular/core'; @Component ({ selector: 'my-app', templateUrl: 'app/app.component.html' }) export class AppComponent { title: string = 'Hello World'; }
-
Modules are logical boundaries in your application and the application is divided into separate modules to separate the functionality of your application. Lets take an example of app.module.ts root module declared with @NgModule decorator as below,
import { NgModule } from '@angular/core'; import { BrowserModule } from '@angular/platform-browser'; import { AppComponent } from './app.component'; @NgModule ({ imports: [ BrowserModule ], declarations: [ AppComponent ], bootstrap: [ AppComponent ] }) export class AppModule { }
The NgModule decorator has three options
- The imports option is used to import other dependent modules. The BrowserModule is required by default for any web based angular application
- The declarations option is used to define components in the respective module
- The bootstrap option tells Angular which Component to bootstrap in the application
-
Angular application goes through an entire set of processes or has a lifecycle right from its initiation to the end of the application. The representation of lifecycle in pictorial representation as follows,
The description of each lifecycle method is as below,
- ngOnChanges: When the value of a data bound property changes, then this method is called.
- ngOnInit: This is called whenever the initialization of the directive/component after Angular first displays the data-bound properties happens.
- ngDoCheck: This is for the detection and to act on changes that Angular can't or won't detect on its own.
- ngAfterContentInit: This is called in response after Angular projects external content into the component's view.
- ngAfterContentChecked: This is called in response after Angular checks the content projected into the component.
- ngAfterViewInit: This is called in response after Angular initializes the component's views and child views.
- ngAfterViewChecked: This is called in response after Angular checks the component's views and child views.
- ngOnDestroy: This is the cleanup phase just before Angular destroys the directive/component.
-
Data binding is a core concept in Angular and allows to define communication between a component and the DOM, making it very easy to define interactive applications without worrying about pushing and pulling data. There are four forms of data binding(divided as 3 categories) which differ in the way the data is flowing.
- From the Component to the DOM: Interpolation: {{ value }}: Adds the value of a property from the component
<li>Name: {{ user.name }}</li> <li>Address: {{ user.address }}</li>
Property binding: [property]=”value”: The value is passed from the component to the specified property or simple HTML attribute
<input type="email" [value]="user.email">
- From the DOM to the Component: Event binding: (event)=”function”: When a specific DOM event happens (eg.: click, change, keyup), call the specified method in the component
<button (click)="logout()"></button>
- Two-way binding: Two-way data binding: [(ngModel)]=”value”: Two-way data binding allows to have the data flow both ways. For example, in the below code snippet, both the email DOM input and component email property are in sync
<input type="email" [(ngModel)]="user.email">
-
Metadata is used to decorate a class so that it can configure the expected behavior of the class. The metadata is represented by decorators
- Class decorators, e.g. @Component and @NgModule
import { NgModule, Component } from '@angular/core'; @Component({ selector: 'my-component', template: '<div>Class decorator</div>', }) export class MyComponent { constructor() { console.log('Hey I am a component!'); } } @NgModule({ imports: [], declarations: [], }) export class MyModule { constructor() { console.log('Hey I am a module!'); } }
- Property decorators Used for properties inside classes, e.g. @Input and @Output
import { Component, Input } from '@angular/core'; @Component({ selector: 'my-component', template: '<div>Property decorator</div>' }) export class MyComponent { @Input() title: string; }
- Method decorators Used for methods inside classes, e.g. @HostListener
import { Component, HostListener } from '@angular/core'; @Component({ selector: 'my-component', template: '<div>Method decorator</div>' }) export class MyComponent { @HostListener('click', ['$event']) onHostClick(event: Event) { // clicked, `event` available } }
- Parameter decorators Used for parameters inside class constructors, e.g. @Inject
import { Component, Inject } from '@angular/core'; import { MyService } from './my-service'; @Component({ selector: 'my-component', template: '<div>Parameter decorator</div>' }) export class MyComponent { constructor(@Inject(MyService) myService) { console.log(myService); // MyService } }
-
Angular CLI(Command Line Interface) is a command line interface to scaffold and build angular apps using nodejs style (commonJs) modules. You need to install using below npm command,
npm install @angular/cli@latestBelow are the list of few commands, which will come handy while creating angular projects
- Creating New Project: ng new
- Generating Components, Directives & Services: ng generate/g The different types of commands would be,
- ng generate class my-new-class: add a class to your application
- ng generate component my-new-component: add a component to your application
- ng generate directive my-new-directive: add a directive to your application
- ng generate enum my-new-enum: add an enum to your application
- ng generate module my-new-module: add a module to your application
- ng generate pipe my-new-pipe: add a pipe to your application
- ng generate service my-new-service: add a service to your application
- Running the Project: ng serve
-
TypeScript classes has a default method called constructor which is normally used for the initialization purpose. Whereas ngOnInit method is specific to Angular, especially used to define Angular bindings. Even though constructor getting called first, it is preferred to move all of your Angular bindings to ngOnInit method. In order to use ngOnInit, you need to implement OnInit interface as below,
export class App implements OnInit{ constructor(){ //called first time before the ngOnInit() } ngOnInit(){ //called after the constructor and called after the first ngOnChanges() } }
-
A service is used when a common functionality needs to be provided to various modules. Services allow for greater separation of concerns for your application and better modularity by allowing you to extract common functionality out of components. Let's create a repoService which can be used across components,
import { Injectable } from '@angular/core'; import { Http } from '@angular/http'; @Injectable({ // The Injectable decorator is required for dependency injection to work // providedIn option registers the service with a specific NgModule providedIn: 'root', // This declares the service with the root app (AppModule) }) export class RepoService{ constructor(private http: Http){ } fetchAll(){ return this.http.get('https://api.github.com/repositories'); } }
The above service uses Http service as a dependency.
-
Dependency injection (DI), is an important application design pattern in which a class asks for dependencies from external sources rather than creating them itself. Angular comes with its own dependency injection framework for resolving dependencies( services or objects that a class needs to perform its function).So you can have your services depend on other services throughout your application.
-
The AsyncPipe subscribes to an observable or promise and returns the latest value it has emitted. When a new value is emitted, the pipe marks the component to be checked for changes. Let's take a time observable which continuously updates the view for every 2 seconds with the current time.
@Component({ selector: 'async-observable-pipe', template: `<div><code>observable|async</code>: Time: {{ time | async }}</div>` }) export class AsyncObservablePipeComponent { time = new Observable(observer => setInterval(() => observer.next(new Date().toString()), 2000) ); }
-
You can store your component's template in one of two places. You can define it inline using the template property, or you can define the template in a separate HTML file and link to it in the component metadata using the @Component decorator's templateUrl property. The choice between inline and separate HTML is a matter of taste, circumstances, and organization policy. But normally we use inline template for small portion of code and external template file for bigger views. By default, the Angular CLI generates components with a template file. But you can override that with the below command,
ng generate component hero -it -
We use Angular ngFor directive in the template to display each item in the list. For example, here we iterate over list of users,
<li *ngFor="let user of users"> {{ user }} </li>
The user variable in the ngFor double-quoted instruction is a template input variable
-
Sometimes an app needs to display a view or a portion of a view only under specific circumstances. The Angular ngIf directive inserts or removes an element based on a truthy/falsy condition. Let's take an example to display a message if the user age is more than 18,
<p *ngIf="user.age > 18">You are not eligible for student pass!</p>
Note: Angular isn't showing and hiding the message. It is adding and removing the paragraph element from the DOM. That improves performance, especially in the larger projects with many data bindings.
-
Angular recognizes the value as unsafe and automatically sanitizes it, which removes the <script> tag but keeps safe content such as the text content of the <script> tag. This way it eliminates the risk of script injection attacks. If you still use it then it will be ignored and a warning appears in the browser console. Let's take an example of innerHtml property binding which causes XSS vulnerability,
export class InnerHtmlBindingComponent { // For example, a user/attacker-controlled value from a URL. htmlSnippet = 'Template <script>alert("0wned")</script> <b>Syntax</b>'; }
-
Interpolation is a special syntax that Angular converts into property binding. It’s a convenient alternative to property binding. It is represented by double curly braces({{}}). The text between the braces is often the name of a component property. Angular replaces that name with the string value of the corresponding component property. Let's take an example,
<h3> {{title}} <img src="{{url}}" style="height:30px"> </h3>
In the example above, Angular evaluates the title and url properties and fills in the blanks, first displaying a bold application title and then a URL.
-
A template expression produces a value similar to any Javascript expression. Angular executes the expression and assigns it to a property of a binding target; the target might be an HTML element, a component, or a directive. In the property binding, a template expression appears in quotes to the right of the = symbol as in [property]="expression". In interpolation syntax, the template expression is surrounded by double curly braces. For example, in the below interpolation, the template expression is {{username}},
<h3>{{username}}, welcome to Angular</h3>
The below javascript expressions are prohibited in template expression
- assignments (=, +=, -=, ...)
- new
- chaining expressions with ; or ,
- increment and decrement operators (++ and --)
-
A template statement responds to an event raised by a binding target such as an element, component, or directive. The template statements appear in quotes to the right of the = symbol like (event)="statement". Let's take an example of button click event's statement
<button (click)="editProfile()">Edit Profile</button>
In the above expression, editProfile is a template statement. The below JavaScript syntax expressions are not allowed.
- new
- increment and decrement operators, ++ and --
- operator assignment, such as += and -=
- the bitwise operators | and &
- the template expression operators
-
Binding types can be grouped into three categories distinguished by the direction of data flow. They are listed as below,
- From the source-to-view
- From view-to-source
- View-to-source-to-view
The possible binding syntax can be tabularized as below,
Data direction Syntax Type From the source-to-view(One-way) 1. {{expression}} 2. [target]="expression" 3. bind-target="expression" Interpolation, Property, Attribute, Class, Style From view-to-source(One-way) 1. (target)="statement" 2. on-target="statement" Event View-to-source-to-view(Two-way) 1. [(target)]="expression" 2. bindon-target="expression" Two-way -
A pipe takes in data as input and transforms it to a desired output. For example, let us take a pipe to transform a component's birthday property into a human-friendly date using date pipe.
import { Component } from '@angular/core'; @Component({ selector: 'app-birthday', template: `<p>Birthday is {{ birthday | date }}</p>` }) export class BirthdayComponent { birthday = new Date(1987, 6, 18); // June 18, 1987 }
-
A pipe can accept any number of optional parameters to fine-tune its output. The parameterized pipe can be created by declaring the pipe name with a colon ( : ) and then the parameter value. If the pipe accepts multiple parameters, separate the values with colons. Let's take a birthday example with a particular format(dd/mm/yyyy):
import { Component } from '@angular/core'; @Component({ selector: 'app-birthday', template: `<p>Birthday is {{ birthday | date:'dd/mm/yyyy'}}</p>` // 18/06/1987 }) export class BirthdayComponent { birthday = new Date(1987, 6, 18); }
Note: The parameter value can be any valid template expression, such as a string literal or a component property.
-
You can chain pipes together in potentially useful combinations as per the needs. Let's take a birthday property which uses date pipe(along with parameter) and uppercase pipes as below
import { Component } from '@angular/core'; @Component({ selector: 'app-birthday', template: `<p>Birthday is {{ birthday | date:'fullDate' | uppercase}} </p>` // THURSDAY, JUNE 18, 1987 }) export class BirthdayComponent { birthday = new Date(1987, 6, 18); }
-
Apart from built-inn pipes, you can write your own custom pipe with the below key characteristics,
- A pipe is a class decorated with pipe metadata @Pipe decorator, which you import from the core Angular library For example,
@Pipe({name: 'myCustomPipe'})
- The pipe class implements the PipeTransform interface's transform method that accepts an input value followed by optional parameters and returns the transformed value. The structure of pipeTransform would be as below,
interface PipeTransform { transform(value: any, ...args: any[]): any }
- The @Pipe decorator allows you to define the pipe name that you'll use within template expressions. It must be a valid JavaScript identifier.
template: `{{someInputValue | myCustomPipe: someOtherValue}}` -
You can create custom reusable pipes for the transformation of existing value. For example, let us create a custom pipe for finding file size based on an extension,
import { Pipe, PipeTransform } from '@angular/core'; @Pipe({name: 'customFileSizePipe'}) export class FileSizePipe implements PipeTransform { transform(size: number, extension: string = 'MB'): string { return (size / (1024 * 1024)).toFixed(2) + extension; } }
Now you can use the above pipe in template expression as below,
template: ` <h2>Find the size of a file</h2> <p>Size: {{288966 | customFileSizePipe: 'GB'}}</p> `
-
A pure pipe is only called when Angular detects a change in the value or the parameters passed to a pipe. For example, any changes to a primitive input value (String, Number, Boolean, Symbol) or a changed object reference (Date, Array, Function, Object). An impure pipe is called for every change detection cycle no matter whether the value or parameters changes. i.e, An impure pipe is called often, as often as every keystroke or mouse-move.
-
Every application has at least one Angular module, the root module that you bootstrap to launch the application is called as bootstrapping module. It is commonly known as AppModule. The default structure of AppModule generated by AngularCLI would be as follows,
/* JavaScript imports */ import { BrowserModule } from '@angular/platform-browser'; import { NgModule } from '@angular/core'; import { FormsModule } from '@angular/forms'; import { HttpClientModule } from '@angular/common/http'; import { AppComponent } from './app.component'; /* the AppModule class with the @NgModule decorator */ @NgModule({ declarations: [ AppComponent ], imports: [ BrowserModule, FormsModule, HttpClientModule ], providers: [], bootstrap: [AppComponent] }) export class AppModule { }
-
Observables are declarative which provide support for passing messages between publishers and subscribers in your application. They are mainly used for event handling, asynchronous programming, and handling multiple values. In this case, you define a function for publishing values, but it is not executed until a consumer subscribes to it. The subscribed consumer then receives notifications until the function completes, or until they unsubscribe.
-
Most of the Front-end applications communicate with backend services over HTTP protocol using either XMLHttpRequest interface or the fetch() API. Angular provides a simplified client HTTP API known as HttpClient which is based on top of XMLHttpRequest interface. This client is avaialble from
@angular/common/httppackage. You can import in your root module as below,import { HttpClientModule } from '@angular/common/http';
The major advantages of HttpClient can be listed as below,
- Contains testability features
- Provides typed request and response objects
- Intercept request and response
- Supports Observalbe APIs
- Supports streamlined error handling
-
Below are the steps need to be followed for the usage of HttpClient.
- Import HttpClient into root module:
import { HttpClientModule } from '@angular/common/http'; @NgModule({ imports: [ BrowserModule, // import HttpClientModule after BrowserModule. HttpClientModule, ], ...... }) export class AppModule {}
- Inject the HttpClient into the application: Let's create a userProfileService(userprofile.service.ts) as an example. It also defines get method of HttpClient
import { Injectable } from '@angular/core'; import { HttpClient } from '@angular/common/http'; const userProfileUrl: string = 'assets/data/profile.json'; @Injectable() export class UserProfileService { constructor(private http: HttpClient) { } getUserProfile() { return this.http.get(this.userProfileUrl); } }
- Create a component for subscribing service: Let's create a component called UserProfileComponent(userprofile.component.ts) which inject UserProfileService and invokes the service method,
fetchUserProfile() { this.userProfileService.getUserProfile() .subscribe((data: User) => this.user = { id: data['userId'], name: data['firstName'], city: data['city'] }); }
Since the above service method returns an Observable which needs to be subscribed in the component.
-
The response body doesn't may not return full response data because sometimes servers also return special headers or status code which which are important for the application workflow. Inorder to get full response, you should use observe option from HttpClient,
getUserResponse(): Observable<HttpResponse<User>> { return this.http.get<User>( this.userUrl, { observe: 'response' }); }
Now HttpClient.get() method returns an Observable of typed HttpResponse rather than just the JSON data.
-
If the request fails on the server or failed to reach the server due to network issues then HttpClient will return an error object instead of a successful reponse. In this case, you need to handle in the component by passing error object as a second callback to subscribe() method. Let's see how it can be handled in the component with an example,
fetchUser() { this.userService.getProfile() .subscribe( (data: User) => this.userProfile = { ...data }, // success path error => this.error = error // error path ); }
It is always a good idea to give the user some meaningful feedback instead of displaying the raw error object returned from HttpClient.
-
RxJS is a library for composing asynchronous and callback-based code in a functional, reactive style using Observables. Many APIs such as HttpClient produce and consume RxJS Observables and also uses operators for processing observables. For example, you can import observables and operators for using HttpClient as below,
import { Observable, throwError } from 'rxjs'; import { catchError, retry } from 'rxjs/operators';
-
An Observable instance begins publishing values only when someone subscribes to it. So you need to subscribe by calling the subscribe() method of the instance, passing an observer object to receive the notifications. Let's take an example of creating and subscribing to a simple observable, with an observer that logs the received message to the console.
Creates an observable sequence of 5 integers, starting from 1 const source = range(1, 5); // Create observer object const myObserver = { next: x => console.log('Observer got a next value: ' + x), error: err => console.error('Observer got an error: ' + err), complete: () => console.log('Observer got a complete notification'), }; // Execute with the observer object and Prints out each item myObservable.subscribe(myObserver); // => Observer got a next value: 1 // => Observer got a next value: 2 // => Observer got a next value: 3 // => Observer got a next value: 4 // => Observer got a next value: 5 // => Observer got a complete notification
-
An Observable is a unique Object similar to a Promise that can help manage async code. Observables are not part of the JavaScript language so we need to rely on a popular Observable library called RxJS. The observables are created using new keyword. Let see the simple example of observable,
import { Observable } from 'rxjs'; const observable = new Observable(observer => { setTimeout(() => { observer.next('Hello from a Observable!'); }, 2000); });
-
Observer is an interface for a consumer of push-based notifications delivered by an Observable. It has below structure,
interface Observer<T> { closed?: boolean; next: (value: T) => void; error: (err: any) => void; complete: () => void; }
A handler that implements the Observer interface for receiving observable notifications will be passed as a parameter for observable as below,
myObservable.subscribe(myObserver);
Note: If you don't supply a handler for a notification type, the observer ignores notifications of that type.
-
Below are the list of differences between promise and observable,
| Observable | Promise |
|---|---|
| Declarative: Computation does not start until subscription so that they can be run whenever you need the result | Execute immediately on creation |
| Provide multiple values over time | Provide only one |
| Subscribe method is used for error handling which makes centralized and predictable error handling | Push errors to the child promises |
| Provides chaining and subscription to handle complex applications | Uses only .then() clause |
-
Multi-casting is the practice of broadcasting to a list of multiple subscribers in a single execution. Let's demonstrate the multi-casting feature,
var source = Rx.Observable.from([1, 2, 3]); var subject = new Rx.Subject(); var multicasted = source.multicast(subject); // These are, under the hood, `subject.subscribe({...})`: multicasted.subscribe({ next: (v) => console.log('observerA: ' + v) }); multicasted.subscribe({ next: (v) => console.log('observerB: ' + v) }); // This is, under the hood, `s
-
You can handle errors by specifying an error callback on the observer instead of relying on try/catch which are ineffective in asynchronous environment. For example, you can define error callback as below,
myObservable.subscribe({ next(num) { console.log('Next num: ' + num)}, error(err) { console.log('Received an errror: ' + err)} });
-
The subscribe() method can accept callback function definitions in line, for next, error, and complete handlers is known as short hand notation or Subscribe method with positional arguments. For example, you can define subscribe method as below,
myObservable.subscribe( x => console.log('Observer got a next value: ' + x), err => console.error('Observer got an error: ' + err), () => console.log('Observer got a complete notification') );
-
The RxJS library also provides below utility functions for creating and working with observables.
- Converting existing code for async operations into observables
- Iterating through the values in a stream
- Mapping values to different types
- Filtering streams
- Composing multiple streams
-
RxJS provides creation functions for the process of creating observables from things such as promises, events, timers and Ajax requests. Let us explain each of them with an example,
- Create an observable from a promise
import { from } from 'rxjs'; // from function const data = from(fetch('/api/endpoint')); //Created from Promise data.subscribe({ next(response) { console.log(response); }, error(err) { console.error('Error: ' + err); }, complete() { console.log('Completed'); } });
- Create an observable that creates an AJAX request
import { ajax } from 'rxjs/ajax'; // ajax function const apiData = ajax('/api/data'); // Created from AJAX request // Subscribe to create the request apiData.subscribe(res => console.log(res.status, res.response));
- Create an observable from a counter
import { interval } from 'rxjs'; // interval function const secondsCounter = interval(1000); // Created from Counter value secondsCounter.subscribe(n => console.log(`Counter value: ${n}`));
- Create an observable from an event
import { fromEvent } from 'rxjs'; const el = document.getElementById('custom-element'); const mouseMoves = fromEvent(el, 'mousemove'); const subscription = mouseMoves.subscribe((e: MouseEvent) => { console.log(`Coordnitaes of mouse pointer: ${e.clientX} * ${e.clientY}`); });
-
Normally an observer object can define any combination of next, error and complete notification type handlers. If you don't supply a handler for a notification type, the observer just ignores notifications of that type.
-
Angular elements are Angular components packaged as custom elements(a web standard for defining new HTML elements in a framework-agnostic way). Angular Elements hosts an Angular component, providing a bridge between the data and logic defined in the component and standard DOM APIs, thus, providing a way to use Angular components in
non-Angular environments. -
Since Angular elements are packaged as custom elements the browser support of angular elements is same as custom elements support. This feature is is currently supported natively in a number of browsers and pending for other browsers.
Browser Angular Element Support Chrome Natively supported Opera Natively supported Safari Natively supported Firefox Natively supported from 63 version onwards. You need to enable dom.webcomponents.enabled and dom.webcomponents.customelements.enabled in older browsers Edge Currently it is in progress -
Custom elements (or Web Components) are a Web Platform feature which extends HTML by allowing you to define a tag whose content is created and controlled by JavaScript code. The browser maintains a
CustomElementRegistryof defined custom elements, which maps an instantiable JavaScript class to an HTML tag. Currently this feature is supported by Chrome, Firefox, Opera, and Safari, and available in other browsers through polyfills. -
No, custom elements bootstrap (or start) automatically when they are added to the DOM, and are automatically destroyed when removed from the DOM. Once a custom element is added to the DOM for any page, it looks and behaves like any other HTML element, and does not require any special knowledge of Angular.
-
Below are the steps in an order about custom elements functionality,
- App registers custom element with browser: Use the createCustomElement() function to convert a component into a class that can be registered with the browser as a custom element.
- App adds custom element to DOM: Add custom element just like a built-in HTML element directly into the DOM.
- Browser instantiate component based class: Browser creates an instance of the registered class and adds it to the DOM.
- Instance provides content with data binding and change detection: The content with in template is rendered using the component and DOM data.
The flow chart of the custom elements functionality would be as follows,
-
Transforming components to custom elements involves two major steps,
- Build custom element class: Angular provides the
createCustomElement()function for converting an Angular component (along with its dependencies) to a custom element. The conversion process implementsNgElementConstructorinterface, and creates a constructor class which is used to produce a self-bootstrapping instance of Angular component. - Register element class with browser: It uses
customElements.define()JS function, to register the configured constructor and its associated custom-element tag with the browser'sCustomElementRegistry. When the browser encounters the tag for the registered element, it uses the constructor to create a custom-element instance. The detailed structure would be as follows,
- Build custom element class: Angular provides the
-
The Component properties and logic maps directly into HTML attributes and the browser's event system. Let us describe them in two steps,
- The createCustomElement() API parses the component input properties with corresponding attributes for the custom element. For example, component @Input('myInputProp') converted as custom element attribute
my-input-prop. - The Component outputs are dispatched as HTML Custom Events, with the name of the custom event matching the output name. For example, component @Output() valueChanged = new EventEmitter() converted as custom element with dispatch event as "valueChanged".
- The createCustomElement() API parses the component input properties with corresponding attributes for the custom element. For example, component @Input('myInputProp') converted as custom element attribute
-
You can use the
NgElementandWithPropertiestypes exported from @angular/elements. Let's see how it can be applied by comparing with Angular component, The simple container with input property would be as below,@Component(...) class MyContainer { @Input() message: string; }
After applying types typescript validates input value and their types,
const container = document.createElement('my-container') as NgElement & WithProperties<{message: string}>; container.message = 'Welcome to Angular elements!'; container.message = true; // <-- ERROR: TypeScript knows this should be a string. container.greet = 'News'; // <-- ERROR: TypeScript knows there is no `greet` property on `container`. -
Dynamic components are the components in which components location in the application is not defined at build time.i.e, They are not used in any angular template. But the component is instantiated and placed in the application at runtime.
-
There are mainly three kinds of directives.
- Components — These are directives with a template.
- Structural directives — These directives change the DOM layout by adding and removing DOM elements.
- Attribute directives — These directives change the appearance or behavior of an element, component, or another directive.
-
You can use CLI command
ng generate directiveto create the directive class file. It creates the source file(src/app/components/directivename.directive.ts), the respective test file(.spec.ts) and declare the directive class file in root module. -
Let's take simple highlighter behavior as a example directive for DOM element. You can create and apply the attribute directive using below steps,
- Create HighlightDirective class with the file name
src/app/highlight.directive.ts. In this file, we need to import Directive from core library to apply the metadata and ElementRef in the directive's constructor to inject a reference to the host DOM element ,
import { Directive, ElementRef } from '@angular/core'; @Directive({ selector: '[appHighlight]' }) export class HighlightDirective { constructor(el: ElementRef) { el.nativeElement.style.backgroundColor = 'red'; } }
- Apply the attribute directive as an attribute to the host element(for example,
)
<p appHighlight>Highlight me!</p>
- Run the application to see the highlight behavior on paragraph element
ng serve
- Create HighlightDirective class with the file name
-
Angular Router is a mechanism in which navigation happens from one view to the next as users perform application tasks. It borrows the concepts or model of browser's application navigation.
-
The routing application should add element to the index.html as the first child in the tag inorder to indicate how to compose navigation URLs. If app folder is the application root then you can set the href value as below
<base href="/">
-
The Angular Router which represents a particular component view for a given URL is not part of Angular Core. It is available in library named
@angular/routerto import required router components. For example, we import them in app module as below,import { RouterModule, Routes } from '@angular/router';
-
The RouterOutlet is a directive from the router library and it acts as a placeholder that marks the spot in the template where the router should display the components for that outlet. Router outlet is used like a component,
<router-outlet></router-outlet> <!-- Routed components go here -->
-
The RouterLink is a directive on the anchor tags give the router control over those elements. Since the navigation paths are fixed, you can assign string values to router-link directive as below,
<h1>Angular Router</h1> <nav> <a routerLink="/todosList" >List of todos</a> <a routerLink="/completed" >Completed todos</a> </nav> <router-outlet></router-outlet>
-
RouterLinkActive is a directive that toggles css classes for active RouterLink bindings based on the current RouterState. i.e, the Router will add CSS classes when this link is active and and remove when the link is inactive. For example, you can add them to RouterLinks as below
<h1>Angular Router</h1> <nav> <a routerLink="/todosList" routerLinkActive="active">List of todos</a> <a routerLink="/completed" routerLinkActive="active">Completed todos</a> </nav> <router-outlet></router-outlet>
-
RouterState is a tree of activated routes. Every node in this tree knows about the "consumed" URL segments, the extracted parameters, and the resolved data. You can access the current RouterState from anywhere in the application using the
Router serviceand therouterStateproperty.@Component({templateUrl:'template.html'}) class MyComponent { constructor(router: Router) { const state: RouterState = router.routerState; const root: ActivatedRoute = state.root; const child = root.firstChild; const id: Observable<string> = child.params.map(p => p.id); //... } }
-
During each navigation, the Router emits navigation events through the Router.events property allowing you to track the lifecycle of the route. The sequence of router events is as below,
- NavigationStart,
- RouteConfigLoadStart,
- RouteConfigLoadEnd,
- RoutesRecognized,
- GuardsCheckStart,
- ChildActivationStart,
- ActivationStart,
- GuardsCheckEnd,
- ResolveStart,
- ResolveEnd,
- ActivationEnd
- ChildActivationEnd
- NavigationEnd,
- NavigationCancel,
- NavigationError
- Scroll
-
ActivatedRoute contains the information about a route associated with a component loaded in an outlet. It can also be used to traverse the router state tree. The ActivatedRoute will be injected as a router service to access the information. In the below example, you can access route path and parameters,
@Component({...}) class MyComponent { constructor(route: ActivatedRoute) { const id: Observable<string> = route.params.pipe(map(p => p.id)); const url: Observable<string> = route.url.pipe(map(segments => segments.join(''))); // route.data includes both `data` and `resolve` const user = route.data.pipe(map(d => d.user)); } }
-
A router must be configured with a list of route definitions. You configures the router with routes via the
RouterModule.forRoot()method, and adds the result to the AppModule'simportsarray.const appRoutes: Routes = [ { path: 'todo/:id', component: TodoDetailComponent }, { path: 'todos', component: TodosListComponent, data: { title: 'Todos List' } }, { path: '', redirectTo: '/todos', pathMatch: 'full' }, { path: '**', component: PageNotFoundComponent } ]; @NgModule({ imports: [ RouterModule.forRoot( appRoutes, { enableTracing: true } // <-- debugging purposes only ) // other imports here ], ... }) export class AppModule { }
-
If the URL doesn't match any predefined routes then it causes the router to throw an error and crash the app. In this case, you can use wildcard route. A wildcard route has a path consisting of two asterisks to match every URL. For example, you can define PageNotFoundComponent for wildcard route as below
{ path: '**', component: PageNotFoundComponent }
-
No, the Routing Module is a design choice. You can skip routing Module (for example, AppRoutingModule) when the configuration is simple and merge the routing configuration directly into the companion module (for example, AppModule). But it is recommended when the configuration is complex and includes specialized guard and resolver services.
-
Angular Universal is a server-side rendering module for Angular applications in various scenarios. This is a community driven project and available under @angular/platform-server package. Recently Angular Universal is integrated with Angular CLI.
-
Angular offers two ways to compile your application,
- Just-in-Time (JIT)
- Ahead-of-Time (AOT)
-
Just-in-Time (JIT) is a type of compilation that compiles your app in the browser at runtime. JIT compilation is the default when you run the ng build (build only) or ng serve (build and serve locally) CLI commands. i.e, the below commands used for JIT compilation,
ng build ng serve
-
Ahead-of-Time (AOT) is a type of compilation that compiles your app at build time. For AOT compilation, include the
--aotoption with the ng build or ng serve command as below,ng build --aot ng serve --aot
Note: The ng build command with the --prod meta-flag (
ng build --prod) compiles with AOT by default. -
The Angular components and templates cannot be understood by the browser directly. Due to that Angular applications require a compilation process before they can run in a browser. For example, In AOT compilation, both Angular HTML and TypeScript code converted into efficient JavaScript code during the build phase before browser runs it.
-
Below are the list of AOT benefits,
- Faster rendering: The browser downloads a pre-compiled version of the application. So it can render the application immediately without compiling the app.
- Fewer asynchronous requests: It inlines external HTML templates and CSS style sheets within the application javascript which eliminates separate ajax requests.
- Smaller Angular framework download size: Doesn't require downloading the Angular compiler. Hence it dramatically reduces the application payload.
- Detect template errors earlier: Detects and reports template binding errors during the build step itself
- Better security: It compiles HTML templates and components into JavaScript. So there won't be any injection attacks.
-
You can control your app compilation in two ways
- By providing template compiler options in the
tsconfig.jsonfile - By configuring Angular metadata with decorators
- By providing template compiler options in the
-
In Angular, You must write metadata with the following general constraints,
- Write expression syntax with in the supported range of javascript features
- The compiler can only reference symbols which are exported
- Only call the functions supported by the compiler
- Decorated and data-bound class members must be public.
-
The AOT compiler works in three phases,
- Code Analysis: The compiler records a representation of the source
- Code generation: It handles the interpretation as well as places restrictions on what it interprets.
- Validation: In this phase, the Angular template compiler uses the TypeScript compiler to validate the binding expressions in templates.
-
No, Arrow functions or lambda functions can’t be used to assign values to the decorator properties. For example, the following snippet is invalid:
@Component({ providers: [{ provide: MyService, useFactory: () => getService() }] })
To fix this, it has to be changed as following exported function:
function getService(){ return new MyService(); } @Component({ providers: [{ provide: MyService, useFactory: getService }] })
If you still use arrow function, it generates an error node in place of the function. When the compiler later interprets this node, it reports an error to turn the arrow function into an exported function. Note: From Angular5 onwards, the compiler automatically performs this rewriting while emitting the .js file.
-
The metadata.json file can be treated as a diagram of the overall structure of a decorator's metadata, represented as an abstract syntax tree(AST). During the analysis phase, the AOT collector scan the metadata recorded in the Angular decorators and outputs metadata information in .metadata.json files, one per .d.ts file.
-
No, the AOT collector understands a subset of (or limited) JavaScript features. If an expression uses unsupported syntax, the collector writes an error node to the .metadata.json file. Later point of time, the compiler reports an error if it needs that piece of metadata to generate the application code.
-
The compiler can only resolve references to exported symbols in the metadata. Where as some of the non-exported members are folded while generating the code. i.e Folding is a process in which the collector evaluate an expression during collection and record the result in the .metadata.json instead of the original expression. For example, the compiler couldn't refer selector reference because it is not exported
let selector = 'app-root'; @Component({ selector: selector })
Will be folded into inline selector
@Component({ selector: 'app-root' })
Remember that the compiler can’t fold everything. For example, spread operator on arrays, objects created using new keywords and function calls.
-
The AOT compiler supports macros in the form of functions or static methods that return an expression in a
single return expression. For example, let us take a below macro function,export function wrapInArray<T>(value: T): T[] { return [value]; }
You can use it inside metadata as an expression,
@NgModule({ declarations: wrapInArray(TypicalComponent) }) export class TypicalModule {}
The compiler treats the macro expression as it written directly
@NgModule({ declarations: [TypicalComponent] }) export class TypicalModule {}
-
Below are some of the errors encountered in metadata,
- Expression form not supported: Some of the language features outside of the compiler's restricted expression syntax used in angular metadata can produce this error.
Let's see some of these examples,
1. export class User { ... } const prop = typeof User; // typeof is not valid in metadata 2. { provide: 'token', useValue: { [prop]: 'value' } }; // bracket notation is not valid in metadata
- ** Reference to a local (non-exported) symbol:** The compiler encountered a referenced to a locally defined symbol that either wasn't exported or wasn't initialized.
Let's take example of this error,
You can fix this by either exporting or initializing the value,
// ERROR let username: string; // neither exported nor initialized @Component({ selector: 'my-component', template: ... , providers: [ { provide: User, useValue: username } ] }) export class MyComponent {}
export let username: string; // exported (or) let username = 'John'; // initialized
- Function calls are not supported: The compiler does not currently support function expressions or lambda functions. For example, you cannot set a provider's useFactory to an anonymous function or arrow function as below.
You can fix this with exported function
providers: [ { provide: MyStrategy, useFactory: function() { ... } }, { provide: OtherStrategy, useFactory: () => { ... } } ]
export function myStrategy() { ... } export function otherStrategy() { ... } ... // metadata providers: [ { provide: MyStrategy, useFactory: myStrategy }, { provide: OtherStrategy, useFactory: otherStrategy },
- Destructured variable or constant not supported: The compiler does not support references to variables assigned by destructuring.
For example, you cannot write something like this:
You can fix this by non-destructured values
import { user } from './user'; // destructured assignment to name and age const {name, age} = user; ... //metadata providers: [ {provide: Name, useValue: name}, {provide: Age, useValue: age}, ]
import { user } from './user'; ... //metadata providers: [ {provide: Name, useValue: user.name}, {provide: Age, useValue: user.age}, ]
- Expression form not supported: Some of the language features outside of the compiler's restricted expression syntax used in angular metadata can produce this error.
Let's see some of these examples,
-
Metadata rewriting is the process in which the compiler converts the expression initializing the fields such as useClass, useValue, useFactory, and data into an exported variable, which replaces the expression. Remember that the compiler does this rewriting during the emit of the .js file but not in definition files( .d.ts file).
-
Angular Compiler supports configuration inheritance through extends in the tsconfig.json on angularCompilerOptions. i.e, The configuration from the base file(for example, tsconfig.base.json) are loaded first, then overridden by those in the inheriting config file.
{ "extends": "../tsconfig.base.json", "compilerOptions": { "experimentalDecorators": true, ... }, "angularCompilerOptions": { "fullTemplateTypeCheck": true, "preserveWhitespaces": true, ... } }
-
The angular template compiler options are specified as members of the angularCompilerOptions object in the tsconfig.json file. These options will be specified adjecent to typescript compiler options.
{ "compilerOptions": { "experimentalDecorators": true, ... }, "angularCompilerOptions": { "fullTemplateTypeCheck": true, "preserveWhitespaces": true, ... } }
-
You can enable binding expression validation explicitly by adding the compiler option fullTemplateTypeCheck in the "angularCompilerOptions" of the project's tsconfig.json. It produces error messages when a type error is detected in a template binding expression. For example, consider the following component:
@Component({ selector: 'my-component', template: '{{user.contacts.email}}' }) class MyComponent { user?: User; }
This will produce the following error:
my.component.ts.MyComponent.html(1,1): : Property 'contacts' does not exist on type 'User'. Did you mean 'contact'?
-
You can disable binding expression type checking using $any() type cast function(by surrounding the expression). In the following example, the error Property contacts does not exist is suppressed by casting user to the any type.
template: '{{$any(user).contacts.email}}'The $any() cast function also works with this to allow access to undeclared members of the component.
template: '{{$any(this).contacts.email}}' -
You can use the non-null type assertion operator to suppress the Object is possibly 'undefined' error. In the following example, the user and contact properties are always set together, implying that contact is always non-null if user is non-null. The error is suppressed in the example by using contact!.email.
@Component({ selector: 'my-component', template: '<span *ngIf="user"> {{user.name}} contacted through {{contact!.email}} </span>' }) class MyComponent { user?: User; contact?: Contact; setData(user: User, contact: Contact) { this.user = user; this.contact = contact; } }
-
The expression used in an ngIf directive is used to narrow type unions in the Angular template compiler similar to if expression in typescript. So *ngIf allows the typeScript compiler to infer that the data used in the binding expression will never be undefined.
@Component({ selector: 'my-component', template: '<span *ngIf="user"> {{user.contact.email}} </span>' }) class MyComponent { user?: User; }
-
The dependencies section of package.json with in an angular application can be divided as follow,
- Angular packages: Angular core and optional modules; their package names begin @angular/.
- Support packages: Third-party libraries that must be present for Angular apps to run.
- Polyfill packages: Polyfills plug gaps in a browser's JavaScript implementation.
-
A Zone is an execution context that persists across async tasks. Angular relies on zone.js to run Angular's change detection processes when native JavaScript operations raise events
-
The commonly-needed services, pipes, and directives provided by @angular/common module. Apart from these HttpClientModule is available under @angular/common/http.
-
Codelyzer provides set of tslint rules for static code analysis of Angular TypeScript projects. ou can run the static code analyzer over web apps, NativeScript, Ionic etc. Angular CLI has support for this and it can be use as below,
ng new codelyzer ng lint
-
Angular's animation system is built on CSS functionality in order to animate any property that the browser considers animatable. These properties includes positions, sizes, transforms, colors, borders etc. The Angular modules for animations are @angular/animations and @angular/platform-browser and these dependencies are automatically added to your project when you create a project using Angular CLI.
-
You need to follow below steps to implement animation in your angular project,
- Enabling the animations module: Import BrowserAnimationsModule to add animation capabilities into your Angular root application module(for example, src/app/app.module.ts).
import { NgModule } from '@angular/core'; import { BrowserModule } from '@angular/platform-browser'; import { BrowserAnimationsModule } from '@angular/platform-browser/animations'; @NgModule({ imports: [ BrowserModule, BrowserAnimationsModule ], declarations: [ ], bootstrap: [ ] }) export class AppModule { }
- Importing animation functions into component files: Import required animation functions from @angular/animations in component files(for example, src/app/app.component.ts).
import { trigger, state, style, animate, transition, // ... } from '@angular/animations';
- Adding the animation metadata property: add a metadata property called animations: within the @Component() decorator in component files(for example, src/app/app.component.ts)
@Component({ selector: 'app-root', templateUrl: 'app.component.html', styleUrls: ['app.component.css'], animations: [ // animation triggers go here ] })
-
Angular's state() function is used to define different states to call at the end of each transition. This function takes two arguments: a unique name like open or closed and a style() function. For example, you can write a open state function
state('open', style({ height: '300px', opacity: 0.5, backgroundColor: 'blue' })),
-
The style function is used to define a set of styles to associate with a given state name. You need to use it along with state() function to set CSS style attributes. For example, in the close state, the button has a height of 100 pixels, an opacity of 0.8, and a background color of green.
state('close', style({ height: '100px', opacity: 0.8, backgroundColor: 'green' })),
Note: The style attributes must be in camelCase
-
Angular Animations are a powerful way to implement sophisticated and compelling animations for your Angular single page web application.
import { Component, OnInit, Input } from '@angular/core'; import { trigger, state, style, animate, transition } from '@angular/animations'; @Component({ selector: 'app-animate', templateUrl: `<div [@changeState]="currentState" class="myblock mx-auto"></div>`, styleUrls: `.myblock { background-color: green; width: 300px; height: 250px; border-radius: 5px; margin: 5rem; }`, animations: [ trigger('changeState', [ state('state1', style({ backgroundColor: 'green', transform: 'scale(1)' })), state('state2', style({ backgroundColor: 'red', transform: 'scale(1.5)' })), transition('*=>state1', animate('300ms')), transition('*=>state2', animate('2000ms')) ]) ] }) export class AnimateComponent implements OnInit { @Input() currentState; constructor() { } ngOnInit() { } }
-
The animation transition function is used to specify the changes that occur between one state and another over a period of time. It accepts two arguments: the first argument accepts an expression that defines the direction between two transition states, and the second argument accepts an animate() function. Let's take an example state transition from open to closed with an half second transition between states.
transition('open => closed', [ animate('500ms') ]),
-
Using DomSanitizer we can inject the dynamic Html,Style,Script,Url.
import { Component, OnInit } from '@angular/core'; import { DomSanitizer } from '@angular/platform-browser'; @Component({ selector: 'my-app', template: ` <div [innerHtml]="htmlSnippet"></div> `, }) export class App { constructor(protected sanitizer: DomSanitizer) {} htmlSnippet: string = this.sanitizer.bypassSecurityTrustScript("<script>safeCode()</script>"); } -
A service worker is a script that runs in the web browser and manages caching for an application. Starting from 5.0.0 version, Angular ships with a service worker implementation. Angular service worker is designed to optimize the end user experience of using an application over a slow or unreliable network connection, while also minimizing the risks of serving outdated content.
-
Below are the list of design goals of Angular's service workers,
- It caches an application just like installing a native application
- A running application continues to run with the same version of all files without any incompatible files
- When you refresh the application, it loads the latest fully cached version
- When changes are published then it immediately updates in the background
- Service workers saves the bandwidth by downloading the resources only when they changed.
-
Dependency injection is a common component in both AngularJS and Angular, but there are some key differences between the two frameworks in how it actually works. | AngularJS | Angular | |---- | --------- | Dependency injection tokens are always strings | Tokens can have different types. They are often classes and sometimes can be strings. | | There is exactly one injector even though it is a multi-module applications | There is a tree hierarchy of injectors, with a root injector and an additional injector for each component. |
-
Angular Ivy is a new rendering engine for Angular. You can choose to opt in a preview version of Ivy from Angular version 8.
- You can enable ivy in a new project by using the --enable-ivy flag with the ng new command
ng new ivy-demo-app --enable-ivy
- You can add it to an existing project by adding
enableIvyoption in theangularCompilerOptionsin your project'stsconfig.app.json.
{ "compilerOptions": { ... }, "angularCompilerOptions": { "enableIvy": true } }
-
You can expect below features with Ivy preview,
- Generated code that is easier to read and debug at runtime
- Faster re-build time
- Improved payload size
- Improved template type checking
-
Yes, it is a recommended configuration. Also, AOT compilation with Ivy is faster. So you need set the default build options(with in angular.json) for your project to always use AOT compilation.
{ "projects": { "my-project": { "architect": { "build": { "options": { ... "aot": true, } } } } } }
-
The Angular Language Service is a way to get completions, errors, hints, and navigation inside your Angular templates whether they are external in an HTML file or embedded in annotations/decorators in a string. It has the ability to autodetect that you are opening an Angular file, reads your
tsconfig.jsonfile, finds all the templates you have in your application, and then provides all the language services. -
You can install Angular Language Service in your project with the following npm command
npm install --save-dev @angular/language-service
After that add the following to the "compilerOptions" section of your project's tsconfig.json
"plugins": [ {"name": "@angular/language-service"} ]
Note: The completion and diagnostic services works for .ts files only. You need to use custom plugins for supporting HTML files.
-
Yes, Angular Language Service is currently available for Visual Studio Code and WebStorm IDEs. You need to install angular language service using an extension and devDependency respectively. In sublime editor, you need to install typescript which has has a language service plugin model.
-
Basically there are 3 main features provided by Angular Language Service,
- Autocompletion: Autocompletion can speed up your development time by providing you with contextual possibilities and hints as you type with in an interpolation and elements.
- Error checking: It can also warn you of mistakes in your code.
- Navigation: Navigation allows you to hover a component, directive, module and then click and press F12 to go directly to its definition.
-
You can add web worker anywhere in your application. For example, If the file that contains your expensive computation is
src/app/app.component.ts, you can add a Web Worker usingng generate web-worker appcommand which will createsrc/app/app.worker.tsweb worker file. This command will perform below actions,- Configure your project to use Web Workers
- Adds app.worker.ts to receive messages
addEventListener('message', ({ data }) => { const response = `worker response to ${data}`; postMessage(response); });
- The component
app.component.tsfile updated with web worker file
if (typeof Worker !== 'undefined') { // Create a new const worker = new Worker('./app.worker', { type: 'module' }); worker.onmessage = ({ data }) => { console.log('page got message: $\{data\}'); }; worker.postMessage('hello'); } else { // Web Workers are not supported in this environment. }
Note: You may need to refactor your initial scaffolding web worker code for sending messages to and from.
-
You need to remember two important things when using Web Workers in Angular projects,
- Some environments or platforms(like @angular/platform-server) used in Server-side Rendering, don't support Web Workers. In this case you need to provide a fallback mechanism to perform the computations to work in this environments.
- Running Angular in web worker using
@angular/platform-webworkeris not yet supported in Angular CLI.
-
In Angular8, the CLI Builder API is stable and available to developers who want to customize the
Angular CLIby adding or modifying commands. For example, you could supply a builder to perform an entirely new task, or to change which third-party tool is used by an existing command. -
A builder function ia a function that uses the
Architect APIto perform a complex process such as "build" or "test". The builder code is defined in an npm package. For example, BrowserBuilder runs a webpack build for a browser target and KarmaBuilder starts the Karma server and runs a webpack build for unit tests. -
The Angular CLI command
ng runis used to invoke a builder with a specific target configuration. The workspace configuration file,angular.json, contains default configurations for built-in builders. -
An App shell is a way to render a portion of your application via a route at build time. This is useful to first paint of your application that appears quickly because the browser can render static HTML and CSS without the need to initialize JavaScript. You can achieve this using Angular CLI which generates an app shell for running server-side of your app.
ng generate appShell [options] (or) ng g appShell [options]
-
Angular uses capitalization conventions to distinguish the names of various types. Angular follows the list of the below case types.
- camelCase : Symbols, properties, methods, pipe names, non-component directive selectors, constants uses lowercase on the first letter of the item. For example, "selectedUser"
- UpperCamelCase (or PascalCase): Class names, including classes that define components, interfaces, NgModules, directives, and pipes uses uppercase on the first letter of the item.
- dash-case (or "kebab-case"): The descriptive part of file names, component selectors uses dashes between the words. For example, "app-user-list".
- UPPER_UNDERSCORE_CASE: All constants uses capital letters connected with underscores. For example, "NUMBER_OF_USERS".
-
A class decorator is a decorator that appears immediately before a class definition, which declares the class to be of the given type, and provides metadata suitable to the type The following list of decorators comes under class decorators,
- @Component()
- @Directive()
- @Pipe()
- @Injectable()
- @NgModule()
-
The class field decorators are the statements declared immediately before a field in a class definition that defines the type of that field. Some of the examples are: @input and @output,
@Input() myProperty; @Output() myEvent = new EventEmitter();
-
Declarable is a class type that you can add to the declarations list of an NgModule. The class types such as components, directives, and pipes comes can be declared in the module.
-
Below classes shouldn't be declared,
- A class that's already declared in another NgModule
- Ngmodule classes
- Service classes
- Helper classes
-
A DI token is a lookup token associated with a dependency provider in dependency injection system. The injector maintains an internal token-provider map that it references when asked for a dependency and the DI token is the key to the map. Let's take example of DI Token usage,
const BASE_URL = new InjectionToken<string>('BaseUrl'); const injector = Injector.create({providers: [{provide: BASE_URL, useValue: 'http://some-domain.com'}]}); const url = injector.get(BASE_URL);
-
A domain-specific language (DSL) is a computer language specialized to a particular application domain. Angular has its own Domain Specific Language (DSL) which allows us to write Angular specific html-like syntax on top of normal html. It has its own compiler that compiles this syntax to html that the browser can understand. This DSL is defined in NgModules such as animations, forms, and routing and navigation. Basically you will see 3 main syntax in Angular DSL.
(): Used for Output and DOM events.[]: Used for Input and specific DOM element attributes.*: Structural directives(*ngFor or *ngIf) will affect/change the DOM structure.
-
An RxJS Subject is a special type of Observable that allows values to be multicasted to many Observers. While plain Observables are unicast (each subscribed Observer owns an independent execution of the Observable), Subjects are multicast.
A Subject is like an Observable, but can multicast to many Observers. Subjects are like EventEmitters: they maintain a registry of many listeners.
import { Subject } from 'rxjs'; const subject = new Subject<number>(); subject.subscribe({ next: (v) => console.log(`observerA: ${v}`) }); subject.subscribe({ next: (v) => console.log(`observerB: ${v}`) }); subject.next(1); subject.next(2);
-
Bazel is a powerful build tool developed and massively used by Google and it can keep track of the dependencies between different packages and build targets. In Angular8, you can build your CLI application with Bazel. Note: The Angular framework itself is built with Bazel.
-
Below are the list of key advantages of Bazel tool,
- It creates the possibility of building your back-ends and front-ends with the same tool
- The incremental build and tests
- It creates the possibility to have remote builds and cache on a build farm.
-
The @angular/bazel package provides a builder that allows Angular CLI to use Bazel as the build tool.
- Use in an existing applciation: Add @angular/bazel using CLI
ng add @angular/bazel
- Use in a new application: Install the package and create the application with collection option
npm install -g @angular/bazel ng new --collection=@angular/bazel
When you use ng build and ng serve commands, Bazel is used behind the scenes and outputs the results in dist/bin folder.
-
Sometimes you may want to bypass the Angular CLI builder and run Bazel directly using Bazel CLI. You can install it globally using @bazel/bazel npm package. i.e, Bazel CLI is available under @bazel/bazel package. After you can apply the below common commands,
bazel build [targets] // Compile the default output artifacts of the given targets. bazel test [targets] // Run the tests with *_test targets found in the pattern. bazel run [target]: Compile the program represented by target and then run it. -
A platform is the context in which an Angular application runs. The most common platform for Angular applications is a web browser, but it can also be an operating system for a mobile device, or a web server. The runtime-platform is provided by the @angular/platform-* packages and these packages allow applications that make use of
@angular/coreand@angular/commonto execute in different environments. i.e, Angular can be used as platform-independent framework in different environments, For example,- While running in the browser, it uses
platform-browserpackage. - When SSR(server-side rendering ) is used, it uses
platform-serverpackage for providing web server implementation.
- While running in the browser, it uses
-
If multiple modules imports the same module then angular evaluates it only once (When it encounters the module first time). It follows this condition even the module appears at any level in a hierarchy of imported NgModules.
-
You can use
@ViewChilddirective to access elements in the view directly. Let's take input element with a reference,<input #uname>
and define view child directive and access it in ngAfterViewInit lifecycle hook
@ViewChild('uname') input; ngAfterViewInit() { console.log(this.input.nativeElement.value); }
-
In Angular7, you can subscribe to router to detect the changes. The subscription for router events would be as below,
this.router.events.subscribe((event: Event) => {})
Let's take a simple component to detect router changes
import { Component } from '@angular/core'; import { Router, Event, NavigationStart, NavigationEnd, NavigationError } from '@angular/router'; @Component({ selector: 'app-root', template: `<router-outlet></router-outlet>` }) export class AppComponent { constructor(private router: Router) { this.router.events.subscribe((event: Event) => { if (event instanceof NavigationStart) { // Show loading indicator and perform an action } if (event instanceof NavigationEnd) { // Hide loading indicator and perform an action } if (event instanceof NavigationError) { // Hide loading indicator and perform an action console.log(event.error); // It logs an error for debugging } }); } }
-
You can directly pass object map for http client or create HttpHeaders class to supply the headers.
constructor(private _http: HttpClient) {} this._http.get('someUrl',{ headers: {'header1':'value1','header2':'value2'} }); (or) let headers = new HttpHeaders().set('header1', headerValue1); // create header object headers = headers.append('header2', headerValue2); // add a new header, creating a new object headers = headers.append('header3', headerValue3); // add another header let params = new HttpParams().set('param1', value1); // create params object params = params.append('param2', value2); // add a new param, creating a new object params = params.append('param3', value3); // add another param return this._http.get<any[]>('someUrl', { headers: headers, params: params })
-
From Angular8 release onwards, the applications are built using differential loading strategy from CLI to build two separate bundles as part of your deployed application.
- The first build contains ES2015 syntax which takes the advantage of built-in support in modern browsers, ships less polyfills, and results in a smaller bundle size.
- The second build contains old ES5 syntax to support older browsers with all necessary polyfills. But this results in a larger bundle size.
Note: This strategy is used to support multiple browsers but it only load the code that the browser needs.
-
Yes, Angular 8 supports dynamic imports in router configuration. i.e, You can use the import statement for lazy loading the module using
loadChildrenmethod and it will be understood by the IDEs(VSCode and WebStorm), webpack, etc. Previously, you have been written as below to lazily load the feature module. By mistake, if you have typo in the module name it still accepts the string and throws an error during build time.{path: ‘user’, loadChildren: ‘./users/user.module#UserModulee’},
This problem is resolved by using dynamic imports and IDEs are able to find it during compile time itself.
{path: ‘user’, loadChildren: () => import(‘./users/user.module’).then(m => m.UserModule)};
-
Lazy loading is one of the most useful concepts of Angular Routing. It helps us to download the web pages in chunks instead of downloading everything in a big bundle. It is used for lazy loading by asynchronously loading the feature module for routing whenever required using the property
loadChildren. Let's load bothCustomerandOrderfeature modules lazily as below,const routes: Routes = [ { path: 'customers', loadChildren: () => import('./customers/customers.module').then(module => module.CustomersModule) }, { path: 'orders', loadChildren: () => import('./orders/orders.module').then(module => module.OrdersModule) }, { path: '', redirectTo: '', pathMatch: 'full' } ];
-
Angular 8.0 release introduces Workspace APIs to make it easier for developers to read and modify the angular.json file instead of manually modifying it. Currently, the only supported storage3 format is the JSON-based format used by the Angular CLI. You can enable or add optimization option for build target as below,
import { NodeJsSyncHost } from '@angular-devkit/core/node'; import { workspaces } from '@angular-devkit/core'; async function addBuildTargetOption() { const host = workspaces.createWorkspaceHost(new NodeJsSyncHost()); const workspace = await workspaces.readWorkspace('path/to/workspace/directory/', host); const project = workspace.projects.get('my-app'); if (!project) { throw new Error('my-app does not exist'); } const buildTarget = project.targets.get('build'); if (!buildTarget) { throw new Error('build target does not exist'); } buildTarget.options.optimization = true; await workspaces.writeWorkspace(workspace, host); } addBuildTargetOption();
-
The Angular upgrade is quite easier using Angular CLI
ng updatecommand as mentioned below. For example, if you upgrade from Angular 7 to 8 then your lazy loaded route imports will be migrated to the new import syntax automatically.$ ng update @angular/cli @angular/core
-
Angular Material is a collection of Material Design components for Angular framework following the Material Design spec. You can apply Material Design very easily using Angular Material. The installation can be done through npm or yarn,
npm install --save @angular/material @angular/cdk @angular/animations (OR) yarn add @angular/material @angular/cdk @angular/animations
It supports the most recent two versions of all major browsers. The latest version of Angular material is 8.1.1
-
If you are using
$locationservice in your old AngularJS application, now you can useLocationUpgradeModule(unified location service) which puts the responsibilities of$locationservice toLocationservice in Angular. Let's add this module toAppModuleas below,// Other imports ... import { LocationUpgradeModule } from '@angular/common/upgrade'; @NgModule({ imports: [ // Other NgModule imports... LocationUpgradeModule.config() ] }) export class AppModule {}
-
NgUpgrade is a library put together by the Angular team, which you can use in your applications to mix and match AngularJS and Angular components and bridge the AngularJS and Angular dependency injection systems.
-
Angular CLI downloads and install everything needed with the Jasmine Test framework. You just need to run
ng testto see the test results. By default this command builds the app in watch mode, and launches theKarma test runner. The output of test results would be as below,10% building modules 1/1 modules 0 active ...INFO [karma]: Karma v1.7.1 server started at http://0.0.0.0:9876/ ...INFO [launcher]: Launching browser Chrome ... ...INFO [launcher]: Starting browser Chrome ...INFO [Chrome ...]: Connected on socket ... Chrome ...: Executed 3 of 3 SUCCESS (0.135 secs / 0.205 secs)
Note: A chrome browser also opens and displays the test output in the "Jasmine HTML Reporter".
-
The Angular CLI provides support for polyfills officially. When you create a new project with the ng new command, a
src/polyfills.tsconfiguration file is created as part of your project folder. This file includes the mandatory and many of the optional polyfills as JavaScript import statements. Let's categorize the polyfills,- Mandatory polyfills: These are installed automatically when you create your project with ng new command and the respective import statements enabled in 'src/polyfills.ts' file.
- Optional polyfills: You need to install its npm package and then create import statement in 'src/polyfills.ts' file.
For example, first you need to install below npm package for adding web animations (optional) polyfill.
and create import statement in polyfill file.
npm install --save web-animations-js
import 'web-animations-js';
-
You can inject either ApplicationRef or NgZone, or ChangeDetectorRef into your component and apply below specific methods to trigger change detection in Angular. i.e, There are 3 possible ways,
- ApplicationRef.tick(): Invoke this method to explicitly process change detection and its side-effects. It check the full component tree.
- NgZone.run(callback): It evaluate the callback function inside the Angular zone.
- ChangeDetectorRef.detectChanges(): It detects only the components and it's children.
-
Angular 1 • Angular 1 (AngularJS) is the first angular framework released in the year 2010. • AngularJS is not built for mobile devices. • It is based on controllers with MVC architecture. Angular 2 • Angular 2 was released in the year 2016. Angular 2 is a complete rewrite of Angular1 version. • The performance issues that Angular 1 version had has been addressed in Angular 2 version. • Angular 2 is built from scratch for mobile devices unlike Angular 1 version. • Angular 2 is components based. Angular 3 The following are the different package versions in Angular 2. • @angular/core v2.3.0 • @angular/compiler v2.3.0 • @angular/http v2.3.0 • @angular/router v3.3.0 The router package is already versioned 3 so to avoid confusion switched to Angular 4 version and skipped 3 version. Angular 4 • The compiler generated code file size in AOT mode is very much reduced. • With Angular 4 the production bundles size is reduced by hundreds of KB’s. • Animation features are removed from angular/core and formed as a separate package. • Supports Typescript 2.1 and 2.2. Angular 5 • Angular 5 makes angular faster. It improved the loading time and execution time. • Shipped with new build optimizer. • Supports Typescript 2.5. Angular 6 • It is released in May 2018. • Includes Angular Command Line Interface (CLI), Component Development KIT (CDK), Angular Material Package. Angular 7 • It is released in October 2018. • TypeScript 3.1 • RxJS 6.3 • New Angular CLI • CLI Prompts capability provide an ability to ask questions to the user before they run. It is like interactive dialog between the user and the CLI • With the improved CLI Prompts capability, it helps developers to make the decision. New ng commands ask users for routing and CSS styles types(SCSS) and ng add @angular/material asks for themes and gestures or animations.
