Tutorial built with Angular 6.1.7 and Webpack 4.8

Other versions available:

In this tutorial we'll go through an example of how to build a simple user registration and login system using Angular 6, TypeScript and webpack 4.

The project is available on GitHub at https://github.com/cornflourblue/angular-6-registration-login-example.

Angular CLI version is available at https://github.com/cornflourblue/angular-6-registration-login-example-cli.

Here it is in action: (See on StackBlitz at https://stackblitz.com/edit/angular-6-registration-login-example)

Update History:

14 Sep 2018 - Updated tutorial to Angular 6.1.7

09 Jul 2018 - Added Angular CLI version of the tutorial code and instructions on how to run

26 Jun 2018 - Created real backend API with ASP.NET Core 2.1 at ASP.NET Core 2.1 - Simple API for Authentication, Registration and User Management

21 Jun 2018 - Updated tutorial to Angular 6.0.6 and added auto-logout on "401 Unauthorized" response from the server api

and added auto-logout on "401 Unauthorized" response from the server api 14 Jun 2018 - Created real backend API with NodeJS and MongoDB at NodeJS + MongoDB - Simple API for Authentication, Registration and User Management

16 May 2018 - Built tutorial with Angular 6.0.2



Running the Angular 6 Login Tutorial Example Locally

The tutorial example uses Webpack 4.8 to transpile the TypeScript code and bundle the Angular 6 modules together, and the webpack dev server is used as the local web server, to learn more about using webpack with TypeScript you can check out the webpack docs.

Install NodeJS and NPM from https://nodejs.org/en/download/. Download or clone the tutorial project source code from https://github.com/cornflourblue/angular-6-registration-login-example Install all required npm packages by running npm install from the command line in the project root folder (where the package.json is located). Start the application by running npm start from the command line in the project root folder. Your browser should automatically open at http://localhost:8080 with the demo Angular 6 login page displayed.



Running the Angular CLI Version of the Tutorial Example Locally

This version of the tutorial example is pretty much the same as the Webpack version above, I've just copied it into the project structure generated by Angular CLI (6.0.8) to make it easier for anybody that's using Angular CLI.

For more information about the Angular CLI check out the official website at https://cli.angular.io/.

Install NodeJS and NPM from https://nodejs.org/en/download/. Install Angular CLI by running npm install -g @angular/cli Download the project source code from https://github.com/cornflourblue/angular-6-registration-login-example-cli Install all required npm packages by running npm install from the command line in the project root folder (where the package.json is located). Start the application by running ng serve --open from the command line in the project root folder. Your browser should automatically open at http://localhost:4200 with the demo Angular 6 login page displayed.



Running the Tutorial Example with a Real Backend API

The tutorial uses a fake backend that stores users in HTML5 local storage, to switch to using a real web service simply remove the fake backend providers in the app.module.ts file below the comment // providers used to create fake backend .

You can build your own backend api or start with one of the below options:



Angular 6 Tutorial Project Structure

The project and code structure of the tutorial mostly follows the best practice recommendations in the official Angular Style Guide, with a few of my own tweaks here and there.

The project structure has a folder per feature (home, login & register), while other shared/common code (services, models, guards, directives & helpers) is placed in folders prefixed with an underscore "_" to easily differentiate between shared code and feature specific code, the prefix also groups shared component folders together at the top of the folder structure.

The index.ts files in each folder are barrel files that group the exported modules from a folder together so they can be imported using the folder path instead of the full module path and to enable importing multiple modules in a single import (e.g. import { AlertService, UserService } from '../_services' ).

Here's the tutorial project structure:



Below is all the tutorial project code along with brief descriptions of each file to explain how it all fits together.

Angular 6 Alert Component Template

Path: /src/app/_directives/alert.component.html

The alert component template contains the html for displaying alert messages at the top of the page.

<div *ngIf="message" [ngClass]="{ 'alert': message, 'alert-success': message.type === 'success', 'alert-danger': message.type === 'error' }">{{message.text}}</div>

Angular 6 Alert Component

Path: /src/app/_directives/alert.component.ts

The alert component passes alert messages to the template whenever a message is received from the alert service. It does this by subscribing to the alert service's getMessage() method which returns an Observable.

import { Component, OnInit, OnDestroy } from '@angular/core'; import { Subscription } from 'rxjs'; import { AlertService } from '../_services'; @Component({ selector: 'alert', templateUrl: 'alert.component.html' }) export class AlertComponent implements OnInit, OnDestroy { private subscription: Subscription; message: any; constructor(private alertService: AlertService) { } ngOnInit() { this.subscription = this.alertService.getMessage().subscribe(message => { this.message = message; }); } ngOnDestroy() { this.subscription.unsubscribe(); } }

Angular 6 Auth Guard

Path: /src/app/_guards/auth.guard.ts

The auth guard is used to prevent unauthenticated users from accessing restricted routes, in this example it's used in app.routing.ts to protect the home page route. For more information about angular 2 guards you can check out this post on the thoughtram blog.

NOTE: While technically it's possible to bypass this client side authentication check by manually adding a 'currentUser' object to local storage using browser dev tools, this would only give access to the client side routes/components, it wouldn't give access to any real secure data from the server api because a valid authentication token (JWT) is required for this.

import { Injectable } from '@angular/core'; import { Router, CanActivate, ActivatedRouteSnapshot, RouterStateSnapshot } from '@angular/router'; @Injectable() export class AuthGuard implements CanActivate { constructor(private router: Router) { } canActivate(route: ActivatedRouteSnapshot, state: RouterStateSnapshot) { if (localStorage.getItem('currentUser')) { // logged in so return true return true; } // not logged in so redirect to login page with the return url this.router.navigate(['/login'], { queryParams: { returnUrl: state.url }}); return false; } }

Angular 6 Fake Backend Provider

Path: /src/app/_helpers/fake-backend.ts

The fake backend provider enables the example to run without a backend / backendless, it uses HTML5 local storage for storing registered user data and provides fake implementations for authentication and CRUD methods, these would be handled by a real api and database in a production application.

It's implemented using the HttpInterceptor class that was introduced in Angular 4.3 as part of the new HttpClientModule. By extending the HttpInterceptor class you can create a custom interceptor to modify http requests before they get sent to the server. In this case the FakeBackendInterceptor intercepts certain requests based on their URL and provides a fake response instead of going to the server.

import { Injectable } from '@angular/core'; import { HttpRequest, HttpResponse, HttpHandler, HttpEvent, HttpInterceptor, HTTP_INTERCEPTORS } from '@angular/common/http'; import { Observable, of, throwError } from 'rxjs'; import { delay, mergeMap, materialize, dematerialize } from 'rxjs/operators'; @Injectable() export class FakeBackendInterceptor implements HttpInterceptor { constructor() { } intercept(request: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> { // array in local storage for registered users let users: any[] = JSON.parse(localStorage.getItem('users')) || []; // wrap in delayed observable to simulate server api call return of(null).pipe(mergeMap(() => { // authenticate if (request.url.endsWith('/users/authenticate') && request.method === 'POST') { // find if any user matches login credentials let filteredUsers = users.filter(user => { return user.username === request.body.username && user.password === request.body.password; }); if (filteredUsers.length) { // if login details are valid return 200 OK with user details and fake jwt token let user = filteredUsers[0]; let body = { id: user.id, username: user.username, firstName: user.firstName, lastName: user.lastName, token: 'fake-jwt-token' }; return of(new HttpResponse({ status: 200, body: body })); } else { // else return 400 bad request return throwError({ error: { message: 'Username or password is incorrect' } }); } } // get users if (request.url.endsWith('/users') && request.method === 'GET') { // check for fake auth token in header and return users if valid, this security is implemented server side in a real application if (request.headers.get('Authorization') === 'Bearer fake-jwt-token') { return of(new HttpResponse({ status: 200, body: users })); } else { // return 401 not authorised if token is null or invalid return throwError({ status: 401, error: { message: 'Unauthorised' } }); } } // get user by id if (request.url.match(/\/users\/\d+$/) && request.method === 'GET') { // check for fake auth token in header and return user if valid, this security is implemented server side in a real application if (request.headers.get('Authorization') === 'Bearer fake-jwt-token') { // find user by id in users array let urlParts = request.url.split('/'); let id = parseInt(urlParts[urlParts.length - 1]); let matchedUsers = users.filter(user => { return user.id === id; }); let user = matchedUsers.length ? matchedUsers[0] : null; return of(new HttpResponse({ status: 200, body: user })); } else { // return 401 not authorised if token is null or invalid return throwError({ status: 401, error: { message: 'Unauthorised' } }); } } // register user if (request.url.endsWith('/users/register') && request.method === 'POST') { // get new user object from post body let newUser = request.body; // validation let duplicateUser = users.filter(user => { return user.username === newUser.username; }).length; if (duplicateUser) { return throwError({ error: { message: 'Username "' + newUser.username + '" is already taken' } }); } // save new user newUser.id = users.length + 1; users.push(newUser); localStorage.setItem('users', JSON.stringify(users)); // respond 200 OK return of(new HttpResponse({ status: 200 })); } // delete user if (request.url.match(/\/users\/\d+$/) && request.method === 'DELETE') { // check for fake auth token in header and return user if valid, this security is implemented server side in a real application if (request.headers.get('Authorization') === 'Bearer fake-jwt-token') { // find user by id in users array let urlParts = request.url.split('/'); let id = parseInt(urlParts[urlParts.length - 1]); for (let i = 0; i < users.length; i++) { let user = users[i]; if (user.id === id) { // delete user users.splice(i, 1); localStorage.setItem('users', JSON.stringify(users)); break; } } // respond 200 OK return of(new HttpResponse({ status: 200 })); } else { // return 401 not authorised if token is null or invalid return throwError({ status: 401, error: { message: 'Unauthorised' } }); } } // pass through any requests not handled above return next.handle(request); })) // call materialize and dematerialize to ensure delay even if an error is thrown (https://github.com/Reactive-Extensions/RxJS/issues/648) .pipe(materialize()) .pipe(delay(500)) .pipe(dematerialize()); } } export let fakeBackendProvider = { // use fake backend in place of Http service for backend-less development provide: HTTP_INTERCEPTORS, useClass: FakeBackendInterceptor, multi: true };

Angular 6 Http Error Interceptor

Path: /src/app/_helpers/error.interceptor.ts

The Error Interceptor intercepts http responses from the api to check if there were any errors. If there is a 401 Unauthorized response the user is automatically logged out of the application, all other errors are re-thrown to be caught by the calling service so an alert can be displayed to the user.

It's implemented using the HttpInterceptor class that was introduced in Angular 4.3 as part of the new HttpClientModule. By extending the HttpInterceptor class you can create a custom interceptor to catch all error responses from the server in a single location.

Http interceptors are added to the request pipeline in the providers section of the app.module.ts file.

import { Injectable } from '@angular/core'; import { HttpRequest, HttpHandler, HttpEvent, HttpInterceptor } from '@angular/common/http'; import { Observable, throwError } from 'rxjs'; import { catchError } from 'rxjs/operators'; import { AuthenticationService } from '../_services'; @Injectable() export class ErrorInterceptor implements HttpInterceptor { constructor(private authenticationService: AuthenticationService) {} intercept(request: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> { return next.handle(request).pipe(catchError(err => { if (err.status === 401) { // auto logout if 401 response returned from api this.authenticationService.logout(); location.reload(true); } const error = err.error.message || err.statusText; return throwError(error); })) } }

Angular 6 JWT Interceptor

Path: /src/app/_helpers/jwt.interceptor.ts

The JWT Interceptor intercepts http requests from the application to add a JWT auth token to the Authorization header if the user is logged in.

It's implemented using the HttpInterceptor class that was introduced in Angular 4.3 as part of the new HttpClientModule. By extending the HttpInterceptor class you can create a custom interceptor to modify http requests before they get sent to the server.

Http interceptors are added to the request pipeline in the providers section of the app.module.ts file.

import { Injectable } from '@angular/core'; import { HttpRequest, HttpHandler, HttpEvent, HttpInterceptor } from '@angular/common/http'; import { Observable } from 'rxjs'; @Injectable() export class JwtInterceptor implements HttpInterceptor { intercept(request: HttpRequest<any>, next: HttpHandler): Observable<HttpEvent<any>> { // add authorization header with jwt token if available let currentUser = JSON.parse(localStorage.getItem('currentUser')); if (currentUser && currentUser.token) { request = request.clone({ setHeaders: { Authorization: `Bearer ${currentUser.token}` } }); } return next.handle(request); } }

Angular 6 User Model

Path: /src/app/_models/user.ts

The user model is a small class that defines the properties of a user.

export class User { id: number; username: string; password: string; firstName: string; lastName: string; }

Angular 6 Alert Service

Path: /src/app/_services/alert.service.ts

The alert service enables any component in the application to display alert messages at the top of the page via the alert component.

It has methods for displaying success and error messages, and a getMessage() method that returns an Observable that is used by the alert component to subscribe to notifications for whenever a message should be displayed.

import { Injectable } from '@angular/core'; import { Router, NavigationStart } from '@angular/router'; import { Observable, Subject } from 'rxjs'; @Injectable() export class AlertService { private subject = new Subject<any>(); private keepAfterNavigationChange = false; constructor(private router: Router) { // clear alert message on route change router.events.subscribe(event => { if (event instanceof NavigationStart) { if (this.keepAfterNavigationChange) { // only keep for a single location change this.keepAfterNavigationChange = false; } else { // clear alert this.subject.next(); } } }); } success(message: string, keepAfterNavigationChange = false) { this.keepAfterNavigationChange = keepAfterNavigationChange; this.subject.next({ type: 'success', text: message }); } error(message: string, keepAfterNavigationChange = false) { this.keepAfterNavigationChange = keepAfterNavigationChange; this.subject.next({ type: 'error', text: message }); } getMessage(): Observable<any> { return this.subject.asObservable(); } }

Angular 6 Authentication Service

Path: /src/app/_services/authentication.service.ts

The authentication service is used to login and logout of the application, to login it posts the users credentials to the api and checks the response for a JWT token, if there is one it means authentication was successful so the user details including the token are added to local storage.

The logged in user details are stored in local storage so the user will stay logged in if they refresh the browser and also between browser sessions until they logout. If you don't want the user to stay logged in between refreshes or sessions the behaviour could easily be changed by storing user details somewhere less persistent such as session storage or in a property of the authentication service.

import { Injectable } from '@angular/core'; import { HttpClient } from '@angular/common/http'; import { map } from 'rxjs/operators'; @Injectable() export class AuthenticationService { constructor(private http: HttpClient) { } login(username: string, password: string) { return this.http.post<any>(`${config.apiUrl}/users/authenticate`, { username: username, password: password }) .pipe(map(user => { // login successful if there's a jwt token in the response if (user && user.token) { // store user details and jwt token in local storage to keep user logged in between page refreshes localStorage.setItem('currentUser', JSON.stringify(user)); } return user; })); } logout() { // remove user from local storage to log user out localStorage.removeItem('currentUser'); } }

Angular 6 User Service

Path: /src/app/_services/user.service.ts

The user service contains a standard set of CRUD methods for managing users, it acts as the interface between the Angular application and the backend api.

import { Injectable } from '@angular/core'; import { HttpClient } from '@angular/common/http'; import { User } from '../_models'; @Injectable() export class UserService { constructor(private http: HttpClient) { } getAll() { return this.http.get<User[]>(`${config.apiUrl}/users`); } getById(id: number) { return this.http.get(`${config.apiUrl}/users/` + id); } register(user: User) { return this.http.post(`${config.apiUrl}/users/register`, user); } update(user: User) { return this.http.put(`${config.apiUrl}/users/` + user.id, user); } delete(id: number) { return this.http.delete(`${config.apiUrl}/users/` + id); } }

Angular 6 Home Component Template

Path: /src/app/home/home.component.html

The home component template contains html and angular 6 template syntax for displaying a simple welcome message, a list of users and a logout link.

<h1>Hi {{currentUser.firstName}}!</h1> <p>You're logged in with Angular 6!!</p> <h3>All registered users:</h3> <ul> <li *ngFor="let user of users"> {{user.username}} ({{user.firstName}} {{user.lastName}}) - <a (click)="deleteUser(user.id)" class="text-danger">Delete</a> </li> </ul> <p><a [routerLink]="['/login']">Logout</a></p>

Angular 6 Home Component

Path: /src/app/home/home.component.ts

The home component gets the current user from local storage and all users from the user service, and makes them available to the template.

import { Component, OnInit } from '@angular/core'; import { first } from 'rxjs/operators'; import { User } from '../_models'; import { UserService } from '../_services'; @Component({templateUrl: 'home.component.html'}) export class HomeComponent implements OnInit { currentUser: User; users: User[] = []; constructor(private userService: UserService) { this.currentUser = JSON.parse(localStorage.getItem('currentUser')); } ngOnInit() { this.loadAllUsers(); } deleteUser(id: number) { this.userService.delete(id).pipe(first()).subscribe(() => { this.loadAllUsers() }); } private loadAllUsers() { this.userService.getAll().pipe(first()).subscribe(users => { this.users = users; }); } }

Angular 6 Login Component Template

Path: /src/app/login/login.component.html

The login component template contains a login form with username and password fields. It displays validation messages for invalid fields when the submit button is clicked. The form submit event is bound to the onSubmit() method of the login component.

The component uses reactive form validation to validate the input fields, for more information about angular reactive form validation check out Angular 6 - Reactive Forms Validation Example.

<h2>Login</h2> <form [formGroup]="loginForm" (ngSubmit)="onSubmit()"> <div class="form-group"> <label for="username">Username</label> <input type="text" formControlName="username" class="form-control" [ngClass]="{ 'is-invalid': submitted && f.username.errors }" /> <div *ngIf="submitted && f.username.errors" class="invalid-feedback"> <div *ngIf="f.username.errors.required">Username is required</div> </div> </div> <div class="form-group"> <label for="password">Password</label> <input type="password" formControlName="password" class="form-control" [ngClass]="{ 'is-invalid': submitted && f.password.errors }" /> <div *ngIf="submitted && f.password.errors" class="invalid-feedback"> <div *ngIf="f.password.errors.required">Password is required</div> </div> </div> <div class="form-group"> <button [disabled]="loading" class="btn btn-primary">Login</button> <img *ngIf="loading" src="data:image/gif;base64,R0lGODlhEAAQAPIAAP///wAAAMLCwkJCQgAAAGJiYoKCgpKSkiH/C05FVFNDQVBFMi4wAwEAAAAh/hpDcmVhdGVkIHdpdGggYWpheGxvYWQuaW5mbwAh+QQJCgAAACwAAAAAEAAQAAADMwi63P4wyklrE2MIOggZnAdOmGYJRbExwroUmcG2LmDEwnHQLVsYOd2mBzkYDAdKa+dIAAAh+QQJCgAAACwAAAAAEAAQAAADNAi63P5OjCEgG4QMu7DmikRxQlFUYDEZIGBMRVsaqHwctXXf7WEYB4Ag1xjihkMZsiUkKhIAIfkECQoAAAAsAAAAABAAEAAAAzYIujIjK8pByJDMlFYvBoVjHA70GU7xSUJhmKtwHPAKzLO9HMaoKwJZ7Rf8AYPDDzKpZBqfvwQAIfkECQoAAAAsAAAAABAAEAAAAzMIumIlK8oyhpHsnFZfhYumCYUhDAQxRIdhHBGqRoKw0R8DYlJd8z0fMDgsGo/IpHI5TAAAIfkECQoAAAAsAAAAABAAEAAAAzIIunInK0rnZBTwGPNMgQwmdsNgXGJUlIWEuR5oWUIpz8pAEAMe6TwfwyYsGo/IpFKSAAAh+QQJCgAAACwAAAAAEAAQAAADMwi6IMKQORfjdOe82p4wGccc4CEuQradylesojEMBgsUc2G7sDX3lQGBMLAJibufbSlKAAAh+QQJCgAAACwAAAAAEAAQAAADMgi63P7wCRHZnFVdmgHu2nFwlWCI3WGc3TSWhUFGxTAUkGCbtgENBMJAEJsxgMLWzpEAACH5BAkKAAAALAAAAAAQABAAAAMyCLrc/jDKSatlQtScKdceCAjDII7HcQ4EMTCpyrCuUBjCYRgHVtqlAiB1YhiCnlsRkAAAOwAAAAAAAAAAAA==" /> <a [routerLink]="['/register']" class="btn btn-link">Register</a> </div> </form>

Angular 6 Login Component

Path: /src/app/login/login.component.ts

The login component uses the authentication service to login and logout of the application. It automatically logs the user out when it initializes (ngOnInit) so the login page can also be used to logout.

The loginForm: FormGroup object defines the form controls and validators, and is used to access data entered into the form. The FormGroup is part of the Angular Reactive Forms module and is bound to the login template above with the [formGroup]="loginForm" directive.

import { Component, OnInit } from '@angular/core'; import { Router, ActivatedRoute } from '@angular/router'; import { FormBuilder, FormGroup, Validators } from '@angular/forms'; import { first } from 'rxjs/operators'; import { AlertService, AuthenticationService } from '../_services'; @Component({templateUrl: 'login.component.html'}) export class LoginComponent implements OnInit { loginForm: FormGroup; loading = false; submitted = false; returnUrl: string; constructor( private formBuilder: FormBuilder, private route: ActivatedRoute, private router: Router, private authenticationService: AuthenticationService, private alertService: AlertService) {} ngOnInit() { this.loginForm = this.formBuilder.group({ username: ['', Validators.required], password: ['', Validators.required] }); // reset login status this.authenticationService.logout(); // get return url from route parameters or default to '/' this.returnUrl = this.route.snapshot.queryParams['returnUrl'] || '/'; } // convenience getter for easy access to form fields get f() { return this.loginForm.controls; } onSubmit() { this.submitted = true; // stop here if form is invalid if (this.loginForm.invalid) { return; } this.loading = true; this.authenticationService.login(this.f.username.value, this.f.password.value) .pipe(first()) .subscribe( data => { this.router.navigate([this.returnUrl]); }, error => { this.alertService.error(error); this.loading = false; }); } }

Angular 6 Register Component Template

Path: /src/app/register/register.component.html

The register component template contains a simple registration form with fields for first name, last name, username and password. It displays validation messages for invalid fields when the submit button is clicked. The form submit event is bound to the onSubmit() method of the register component.

The component uses reactive form validation to validate the input fields, for more information about angular reactive form validation check out Angular 6 - Reactive Forms Validation Example.

<h2>Register</h2> <form [formGroup]="registerForm" (ngSubmit)="onSubmit()"> <div class="form-group"> <label for="firstName">First Name</label> <input type="text" formControlName="firstName" class="form-control" [ngClass]="{ 'is-invalid': submitted && f.firstName.errors }" /> <div *ngIf="submitted && f.firstName.errors" class="invalid-feedback"> <div *ngIf="f.firstName.errors.required">First Name is required</div> </div> </div> <div class="form-group"> <label for="lastName">Last Name</label> <input type="text" formControlName="lastName" class="form-control" [ngClass]="{ 'is-invalid': submitted && f.lastName.errors }" /> <div *ngIf="submitted && f.lastName.errors" class="invalid-feedback"> <div *ngIf="f.lastName.errors.required">Last Name is required</div> </div> </div> <div class="form-group"> <label for="username">Username</label> <input type="text" formControlName="username" class="form-control" [ngClass]="{ 'is-invalid': submitted && f.username.errors }" /> <div *ngIf="submitted && f.username.errors" class="invalid-feedback"> <div *ngIf="f.username.errors.required">Username is required</div> </div> </div> <div class="form-group"> <label for="password">Password</label> <input type="password" formControlName="password" class="form-control" [ngClass]="{ 'is-invalid': submitted && f.password.errors }" /> <div *ngIf="submitted && f.password.errors" class="invalid-feedback"> <div *ngIf="f.password.errors.required">Password is required</div> <div *ngIf="f.password.errors.minlength">Password must be at least 6 characters</div> </div> </div> <div class="form-group"> <button [disabled]="loading" class="btn btn-primary">Register</button> <img *ngIf="loading" src="data:image/gif;base64,R0lGODlhEAAQAPIAAP///wAAAMLCwkJCQgAAAGJiYoKCgpKSkiH/C05FVFNDQVBFMi4wAwEAAAAh/hpDcmVhdGVkIHdpdGggYWpheGxvYWQuaW5mbwAh+QQJCgAAACwAAAAAEAAQAAADMwi63P4wyklrE2MIOggZnAdOmGYJRbExwroUmcG2LmDEwnHQLVsYOd2mBzkYDAdKa+dIAAAh+QQJCgAAACwAAAAAEAAQAAADNAi63P5OjCEgG4QMu7DmikRxQlFUYDEZIGBMRVsaqHwctXXf7WEYB4Ag1xjihkMZsiUkKhIAIfkECQoAAAAsAAAAABAAEAAAAzYIujIjK8pByJDMlFYvBoVjHA70GU7xSUJhmKtwHPAKzLO9HMaoKwJZ7Rf8AYPDDzKpZBqfvwQAIfkECQoAAAAsAAAAABAAEAAAAzMIumIlK8oyhpHsnFZfhYumCYUhDAQxRIdhHBGqRoKw0R8DYlJd8z0fMDgsGo/IpHI5TAAAIfkECQoAAAAsAAAAABAAEAAAAzIIunInK0rnZBTwGPNMgQwmdsNgXGJUlIWEuR5oWUIpz8pAEAMe6TwfwyYsGo/IpFKSAAAh+QQJCgAAACwAAAAAEAAQAAADMwi6IMKQORfjdOe82p4wGccc4CEuQradylesojEMBgsUc2G7sDX3lQGBMLAJibufbSlKAAAh+QQJCgAAACwAAAAAEAAQAAADMgi63P7wCRHZnFVdmgHu2nFwlWCI3WGc3TSWhUFGxTAUkGCbtgENBMJAEJsxgMLWzpEAACH5BAkKAAAALAAAAAAQABAAAAMyCLrc/jDKSatlQtScKdceCAjDII7HcQ4EMTCpyrCuUBjCYRgHVtqlAiB1YhiCnlsRkAAAOwAAAAAAAAAAAA==" /> <a [routerLink]="['/login']" class="btn btn-link">Cancel</a> </div> </form>

Angular 6 Register Component

Path: /src/app/register/register.component.ts

The register component creates a new user with the user service when the register form is submitted.

The registerForm: FormGroup object defines the form controls and validators, and is used to access data entered into the form. The FormGroup is part of the Angular Reactive Forms module and is bound to the login template above with the [formGroup]="registerForm" directive.

import { Component, OnInit } from '@angular/core'; import { Router } from '@angular/router'; import { FormBuilder, FormGroup, Validators } from '@angular/forms'; import { first } from 'rxjs/operators'; import { AlertService, UserService } from '../_services'; @Component({templateUrl: 'register.component.html'}) export class RegisterComponent implements OnInit { registerForm: FormGroup; loading = false; submitted = false; constructor( private formBuilder: FormBuilder, private router: Router, private userService: UserService, private alertService: AlertService) { } ngOnInit() { this.registerForm = this.formBuilder.group({ firstName: ['', Validators.required], lastName: ['', Validators.required], username: ['', Validators.required], password: ['', [Validators.required, Validators.minLength(6)]] }); } // convenience getter for easy access to form fields get f() { return this.registerForm.controls; } onSubmit() { this.submitted = true; // stop here if form is invalid if (this.registerForm.invalid) { return; } this.loading = true; this.userService.register(this.registerForm.value) .pipe(first()) .subscribe( data => { this.alertService.success('Registration successful', true); this.router.navigate(['/login']); }, error => { this.alertService.error(error); this.loading = false; }); } }

Angular 6 App Component Template

Path: /src/app/app.component.html

The app component template is the root component template of the application, it contains a router-outlet directive for displaying the contents of each view based on the current route, and an alert directive for displaying alert messages from anywhere in the system.

<!-- main app container --> <div class="jumbotron"> <div class="container"> <div class="row"> <div class="col-sm-6 offset-sm-3"> <alert></alert> <router-outlet></router-outlet> </div> </div> </div> </div>

Angular 6 App Component

Path: /src/app/app.component.ts

The app component is the root component of the application, it defines the root tag of the app as <app></app> with the selector property.

import { Component } from '@angular/core'; @Component({ selector: 'app', templateUrl: 'app.component.html' }) export class AppComponent { }

Angular 6 App Module

Path: /src/app/app.module.ts

The app module defines the root module of the application along with metadata about the module. For more info about angular modules check out this page on the official docs site.

This is where the fake backend provider is added to the application, to switch to a real backend simply remove the providers located below the comment // providers used to create fake backend .

import { NgModule } from '@angular/core'; import { BrowserModule } from '@angular/platform-browser'; import { ReactiveFormsModule } from '@angular/forms'; import { HttpClientModule, HTTP_INTERCEPTORS } from '@angular/common/http'; // used to create fake backend import { fakeBackendProvider } from './_helpers'; import { AppComponent } from './app.component'; import { routing } from './app.routing'; import { AlertComponent } from './_directives'; import { AuthGuard } from './_guards'; import { JwtInterceptor, ErrorInterceptor } from './_helpers'; import { AlertService, AuthenticationService, UserService } from './_services'; import { HomeComponent } from './home'; import { LoginComponent } from './login'; import { RegisterComponent } from './register'; @NgModule({ imports: [ BrowserModule, ReactiveFormsModule, HttpClientModule, routing ], declarations: [ AppComponent, AlertComponent, HomeComponent, LoginComponent, RegisterComponent ], providers: [ AuthGuard, AlertService, AuthenticationService, UserService, { provide: HTTP_INTERCEPTORS, useClass: JwtInterceptor, multi: true }, { provide: HTTP_INTERCEPTORS, useClass: ErrorInterceptor, multi: true }, // provider used to create fake backend fakeBackendProvider ], bootstrap: [AppComponent] }) export class AppModule { }

Angular 6 App Routing

Path: /src/app/app.routing.ts

The app routing file defines the routes of the application, each route contains a path and associated component. The home route is secured by passing the AuthGuard to the canActivate property of the route.

import { Routes, RouterModule } from '@angular/router'; import { HomeComponent } from './home'; import { LoginComponent } from './login'; import { RegisterComponent } from './register'; import { AuthGuard } from './_guards'; const appRoutes: Routes = [ { path: '', component: HomeComponent, canActivate: [AuthGuard] }, { path: 'login', component: LoginComponent }, { path: 'register', component: RegisterComponent }, // otherwise redirect to home { path: '**', redirectTo: '' } ]; export const routing = RouterModule.forRoot(appRoutes);

Angular 6 Main Index Html File

Path: /src/index.html

The main index.html file is the initial page loaded by the browser that kicks everything off. Webpack bundles all of the javascript files together and injects them into the body of the index.html page so the scripts get loaded and executed by the browser.

<!DOCTYPE html> <html> <head> <base href="/" /> <title>Angular 6 User Registration and Login Example</title> <meta name="viewport" content="width=device-width, initial-scale=1"> <!-- bootstrap css --> <link href="//netdna.bootstrapcdn.com/bootstrap/4.1.1/css/bootstrap.min.css" rel="stylesheet" /> <style> a { cursor: pointer } </style> </head> <body> <app>Loading...</app> </body> </html>

Angular 6 Main (Bootstrap) File

Path: /src/main.ts

The main file is the entry point used by angular to launch and bootstrap the application.

import './polyfills'; import { platformBrowserDynamic } from '@angular/platform-browser-dynamic'; import { AppModule } from './app/app.module'; platformBrowserDynamic().bootstrapModule(AppModule);

Angular 6 Polyfills

Path: /src/polyfills.ts

Some features used by Angular 6 are not yet supported natively by all major browsers, polyfills are used to add support for features where necessary so your Angular 6 application works across all major browsers.

import 'core-js/es6/reflect'; import 'core-js/es7/reflect'; import 'zone.js/dist/zone';

Angular 6 Custom Typings File

Path: /src/typings.d.ts

A custom typings file is used to declare types that are created outside of your angular application, so the TypeScript compiler is aware of them and doesn't give you errors about unknown types. This typings file contains a declaration for the global config object that is created by webpack (see webpack.config.js below).

// so the typescript compiler doesn't complain about the global config object declare var config: any;

npm package.json

Path: /package.json

The package.json file contains project configuration information including package dependencies which get installed when you run npm install . Full documentation is available on the npm docs website.

{ "name": "angular-6-registration-login-example-webpack", "version": "1.0.0", "repository": { "type": "git", "url": "https://github.com/cornflourblue/angular-6-registration-login-example-webpack.git" }, "scripts": { "build": "webpack --mode production", "start": "webpack-dev-server --mode development --open" }, "license": "MIT", "dependencies": { "@angular/common": "^6.0.0", "@angular/compiler": "^6.0.0", "@angular/core": "^6.0.0", "@angular/forms": "^6.0.0", "@angular/platform-browser": "^6.0.0", "@angular/platform-browser-dynamic": "^6.0.0", "@angular/router": "^6.0.0", "core-js": "^2.5.5", "rxjs": "^6.1.0", "zone.js": "^0.8.26" }, "devDependencies": { "@types/node": "^10.0.4", "angular2-template-loader": "^0.6.2", "html-webpack-plugin": "^3.2.0", "raw-loader": "^0.5.1", "ts-loader": "^4.3.0", "typescript": "^2.8.3", "webpack": "4.8.1", "webpack-cli": "^2.1.3", "webpack-dev-server": "3.1.4" } }

TypeScript tsconfig.json

Path: /tsconfig.json

The tsconfig.json file configures how the TypeScript compiler will convert TypeScript into JavaScript that is understood by the browser. More information is available on the TypeScript docs.

{ "compilerOptions": { "emitDecoratorMetadata": true, "experimentalDecorators": true, "lib": [ "es2015", "dom" ], "module": "commonjs", "moduleResolution": "node", "noImplicitAny": true, "sourceMap": true, "suppressImplicitAnyIndexErrors": true, "target": "es5" } }

Webpack 4 Config

Path: /webpack.config.js

Webpack 4.8 is used to compile and bundle all the project files so they're ready to be loaded into a browser, it does this with the help of loaders and plugins that are configured in the webpack.config.js file. For more info about webpack check out the webpack docs.

This is a minimal webpack.config.js for bundling an Angular 6 application, it compiles TypeScript files using ts-loader , loads angular templates with raw-loader , and injects the bundled scripts into the body of the index.html page using the HtmlWebpackPlugin . It also defines a global config object with the plugin webpack.DefinePlugin .