Book Image

TypeScript Blueprints

By : Ivo Gabe de Wolff
Book Image

TypeScript Blueprints

By: Ivo Gabe de Wolff

Overview of this book

TypeScript is the future of JavaScript. Having been designed for the development of large applications, it is now being widely incorporated in cutting-edge projects such as Angular 2. Adopting TypeScript results in more robust software - software that is more scalable and performant. It's scale and performance that lies at the heart of every project that features in this book. The lessons learned throughout this book will arm you with everything you need to build some truly amazing projects. You'll build a complete single page app with Angular 2, create a neat mobile app using NativeScript, and even build a Pac Man game with TypeScript. As if fun wasn't enough, you'll also find out how to migrate your legacy codebase from JavaScript to TypeScript. This book isn't just for developers who want to learn - it's for developers who want to develop. So dive in and get started on these TypeScript projects.
Table of Contents (16 chapters)
TypeScript Blueprints
Credits
About the Author
About the Reviewer
www.PacktPub.com
Preface

Adding authentication


In lib/server/index.ts, we will first add sessions. A session is a place to store data, which is persistent for a client on the server. On the client side, a cookie will be saved, which contains an identifier of the session. If a request contains a valid cookie with such an identifier, you will get the same session object. Otherwise, a new session will be created:

import { Server, ServerRequest, ServerResponse, ServerError, StatusCode, SessionStore } from "phaethon"; 
import { ObjectID } from "mongodb"; 
import { User, login, logout } from "./user"; 
import * as note from "./note"; 

Tip

With import { ... }, we can import a set of entities from another file. With import * as ..., we import the whole file as an object. The following two snippets are equivalent: import * as foo from "./foo"; foo.bar(); import { bar } from "./foo"; bar();

We define the type of the content of the session as follows:

export interface Session { 
  userId: ObjectID; ...