Angular Interview Questions and Answers
Angular Interview Questions and Answers
AngularJS Angular
This uses use JavaScript to build the Introduced the typescript to write the
application application
3. What is TypeScript?
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
i. Component: These are the basic building blocks of angular application to control
HTML views.
ii. 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.
iii. Templates: This represent the views of an Angular application.
iv. Services: It is used to create components which can be shared across the entire
application.
v. Metadata: This can be used to add more data to an Angular class.
Now this directive extends HTML element behavior with a yellow background as below
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
@Component ({
selector: 'my-app',
template: ` <div>
<h1>{{title}}</h1>
<div>Learn Angular6 with examples</div>
</div> `,
})
Component Directive
Only one component can be present per Many directives can be used per DOM
DOM element element
9. What is a template?
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,
@Component ({
selector: 'my-app',
template: '
<div>
<h1>{{title}}</h1>
<div>Learn Angular</div>
</div>
'
})
@Component ({
selector: 'my-app',
templateUrl: 'app/app.component.html'
})
@NgModule ({
imports: [ BrowserModule ],
declarations: [ AppComponent ],
bootstrap: [ AppComponent ]
})
export class AppModule { }
i. The imports option is used to import other dependent modules. The BrowserModule
is required by default for any web based angular application
ii. The declarations option is used to define components in the respective module
iii. The bootstrap option tells Angular which Component to bootstrap in the application
representation as follows,
i. ngOnChanges: When the value of a data bound property changes, then this method
is called.
ii. ngOnInit: This is called whenever the initialization of the directive/component after
Angular first displays the data-bound properties happens.
iii. ngDoCheck: This is for the detection and to act on changes that Angular can't or
won't detect on its own.
iv. ngAfterContentInit: This is called in response after Angular projects external
content into the component's view.
v. ngAfterContentChecked: This is called in response after Angular checks the content
projected into the component.
vi. ngAfterViewInit: This is called in response after Angular initializes the component's
views and child views.
vii. ngAfterViewChecked: This is called in response after Angular checks the
component's views and child views.
viii. 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.
i. From the Component to the DOM: Interpolation: {{ value }}: Adds the value of a
property from the component
Property binding: [property]=”value”: The value is passed from the component to the
specified property or simple HTML attribute
ii. 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>
Metadata is used to decorate a class so that it can configure the expected behavior of the
class. The metadata is represented by decorators
@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!');
}
}
ii. Property decorators Used for properties inside classes, e.g. @Input and @Output
@Component({
selector: 'my-component',
template: '<div>Property decorator</div>'
})
iii. Method decorators Used for methods inside classes, e.g. @HostListener
@Component({
selector: 'my-component',
template: '<div>Method decorator</div>'
})
export class MyComponent {
@HostListener('click', ['$event'])
onHostClick(event: Event) {
// clicked, `event` available
}
}
iv. Parameter decorators Used for parameters inside class constructors, e.g. @Inject
@Component({
selector: 'my-component',
template: '<div>Parameter decorator</div>'
})
export class MyComponent {
constructor(@Inject(MyService) myService) {
console.log(myService); // MyService
}
}
14. What is angular CLI?
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,
Below are the list of few commands, which will come handy while creating angular projects
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,
ngOnInit(){
//called after the constructor and called after the first ngOnChanges()
}
}
fetchAll(){
return this.http.get('https://api.github.com/repositories');
}
}
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)
);
}
20. What is the option to choose between inline and external
template file?
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,
We use Angular ngFor directive in the template to display each item in the list. For example,
here we iterate over list of users,
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.
<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.
In the above expression, editProfile is a template statement. The below JavaScript syntax
expressions are not allowed.
i. new
ii. increment and decrement operators, ++ and --
iii. operator assignment, such as += and -=
iv. the bitwise operators | and &
v. the template expression operators
1. {{expression}} 2.
From the source-to- [target]="expression" Interpolation, Property, Attribute,
view(One-way) 3. bind- Class, Style
target="expression"
1. (target)="statement"
From view-to-source(One-
2. on- Event
way)
target="statement"
View-to-source-to- 1. Two-way
view(Two-way) [(target)]="expression"
Data direction Syntax Type
2. bindon-
target="expression"
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.
@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):
@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,
i. A pipe is a class decorated with pipe metadata @Pipe decorator, which you import
from the core Angular library For example,
@Pipe({name: 'myCustomPipe'})
ii. 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
}
iii. The @Pipe decorator allows you to define the pipe name that you'll use within
template expressions. It must be a valid JavaScript identifier.
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,
@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';
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.
36. What is HttpClient and its benefits?
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/http package. You can import in your root
module as below,
import { HttpClientModule } from '@angular/common/http';
Below are the steps need to be followed for the usage of HttpClient.
@Injectable()
export class UserProfileService {
constructor(private http: HttpClient) { }
getUserProfile() {
return this.http.get(this.userProfileUrl);
}
}
iii. 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.
40. What is RxJS?
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.
// Execute with the observer object and Prints out each item
source.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,
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.
Observable Promise
Subscribe method is used for error handling which makes Push errors to the child
centralized and predictable error handling promises
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.
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,
50. What will happen if you do not supply handler for observer?
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.
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 CustomElementRegistry of 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.
55. Explain how custom elements works internally?
57. What are the mapping rules between Angular component and
custom element?
The Component properties and logic maps directly into HTML attributes and the browser's
event system. Let us describe them in two steps,
@Component(...)
class MyContainer {
@Input() message: string;
}
After applying types typescript validates input value and their types,
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.
You can use CLI command ng generate directive to 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.
@Directive({
selector: '[appHighlight]'
})
export class HighlightDirective {
constructor(el: ElementRef) {
el.nativeElement.style.backgroundColor = 'red';
}
}
ii. Apply the attribute directive as an attribute to the host element(for example,
iii. Run the application to see the highlight behavior on paragraph element
ng serve
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 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>
@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,
i. NavigationStart,
ii. RouteConfigLoadStart,
iii. RouteConfigLoadEnd,
iv. RoutesRecognized,
v. GuardsCheckStart,
vi. ChildActivationStart,
vii. ActivationStart,
viii. GuardsCheckEnd,
ix. ResolveStart,
x. ResolveEnd,
xi. ActivationEnd
xii. ChildActivationEnd
xiii. NavigationEnd,
xiv. NavigationCancel,
xv. NavigationError
xvi. 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's imports array.
@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
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.
i. Just-in-Time (JIT)
ii. 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 --aot option 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.
79. Why do we need compilation process?
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.
In Angular, You must write metadata with the following general constraints,
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()
}]
})
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.
86. Can I use any javascript feature for expression syntax in AOT?
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
@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.
A Subject is like an Observable, but can multicast to many Observers. Subjects are like
EventEmitters: they maintain a registry of many listeners.
subject.subscribe({
next: (v) => console.log(`observerA: ${v}`)
});
subject.subscribe({
next: (v) => console.log(`observerB: ${v}`)
});
subject.next(1);
subject.next(2);
Note: A chrome browser also opens and displays the test output in the "Jasmine HTML Reporter".
i. 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.
ii. 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.
iii. 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.
iv. 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.
v. Angular 5 • Angular 5 makes angular faster. It improved the loading time and execution
time. • Shipped with new build optimizer. • Supports Typescript 2.5.
vi. Angular 6 • It is released in May 2018. • Includes Angular Command Line Interface (CLI),
Component Development KIT (CDK), Angular Material Package.
vii. 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.
viii. Angular 8 • It is released in October 2018 • Angular 8: Angular 8 supports TypeScript 3.4•
•Angular 8 supports Web Workers • The new compiler for Angular 8 is Ivy Rendering Engine
•Angular 8 provides dynamic imports for lazy-loaded modules • Improvement of
ngUpgrade
ng v
ng version
ng -v
ng --version
Browser Version
Chrome latest
Firefox latest
IE Mobile 11
You can access the current RouterState from anywhere in the Angular app using the Router service
and the routerState property.
Angular CLI creates a folder called my-custom-feature with a file inside called my-custom-
feature.module.ts with the following contents
import { NgModule } from '@angular/core';
import { CommonModule } from '@angular/common';
@NgModule({
imports: [
CommonModule
],
declarations: []
})
export class MyCustomFeature { }
@Injectable({
providedIn: 'root', //Angular provide the service in root injector
})
export class MyService {
}
@Injectable({
providedIn: SomeModule,
})
export class SomeService {
}
@NgModule({
providers: [SomeService],
})
export class SomeModule {
}