MEAN Cookbook

By : McClay

3 (1)

Buy this Book

MEAN Cookbook

3 (1)

By: McClay

Buy this Book

Overview of this book

The MEAN Stack is a framework for web application development using JavaScript-based technologies; MongoDB, Express, Angular, and Node.js. If you want to expand your understanding of using JavaScript to produce a fully functional standalone web application, including the web server, user interface, and database, then this book can help guide you through that transition. This book begins by configuring the frontend of the MEAN stack web application using the Angular JavaScript framework. We then implement common user interface enhancements before moving on to configuring the server layer of our MEAN stack web application using Express for our backend APIs. You will learn to configure the database layer of your MEAN stack web application using MongoDB and the Mongoose framework, including modeling relationships between documents. You will explore advanced topics such as optimizing your web application using WebPack as well as the use of automated testing with the Mocha and Chai frameworks. By the end of the book, you should have acquired a level of proficiency that allows you to confidently build a full production-ready and scalable MEAN stack application.

Preface

What this book covers

What you need for this book

Who this book is for

Sections

Conventions

Reader feedback

Customer support

Free Chapter

Working with Angular 4

Introduction

Upgrading to Angular 4 using NPM

Generating a new Angular project using Angular-CLI

Configuring Angular-CLI project settings

Working with generators in Angular-CLI

Ejecting Angular-CLI from your project

Generating new routes in Angular-CLI

Defining a home page in your Angular routes

Handling 404 errors in an Angular project

Creating nesting routes in Angular

Creating sibling routes in Angular

Programmatic page redirection in Angular

Route preloading with Angular modules

Running tests in Angular-CLI

Enhancing Your User Interface

Introduction

Configuring Sass in Angular

Working with Angular component styles

Using Sass variables for style reusability

Using Sass nesting for better style specificity

Using Sass partials for style organization

Working with Bootstrap in Sass

Customizing Bootstrap for Angular

Using Bootstrap Responsive layouts

Working with Bootstrap components in Angular

Working with Font-Awesome icons in Angular

Internationalization with Angular i18n

Setting your language with Angular i18n

How to Localize dates in Angular

Working with Data

Introduction

Working with actions and events in Angular

Working with form input and models in Angular

Validating data with Angular form properties

Creating services for data in Angular

Using promises to create asynchronous services in Angular

Retrieving API data using HTTP services in Angular

Querying API sources using HTTP services in Angular

Creating Concurrent API requests in Angular

Handling API errors and invalid responses in Angular

HTTP service optimization through client-side caching

Using Express Web Server

Introduction

Creating a new Express project with express-generator

Working with routes in Express

Serving an Angular web application with Express

Working with headers in Express

Working with cookies in Express

Creating Express middleware for routes

Logging traffic and activity with Morgan

Running your Express web server with Forever

Securing your Express web server

REST APIs and Authentication

Introduction

Building REST APIs with Express

Configuring JSON API in Express

Creating a user authentication API in Express

Building a login page with Angular

Using JWT authentication with Express and Angular

Cloud Service Integrations

Introduction

Uploading large multi-part files with Express

Uploading images to Cloudinary from Express

Securing image downloads from Cloudinary

Resizing images and transformations with Cloudinary

Working with Stripe payment processor in Express

Accepting credit card payments in Angular with Stripe

MongoDB and Mongoose

Introduction

How to set up and create a MongoDB database

Connecting to MongoDB through Mongoose

Working with data model in MongoDB and Mongoose

Querying for data using Mongoose query selectors

Relationships

Introduction

Working with data validations and virtuals in Mongoose

Creating sub-documents in Mongoose models

Using pre-save hooks and custom methods in Mongoose Models

Creating embedded documents in MongoDB with objectId

Creating relational documents in MongoDB with population

Build Systems and Optimizations

Introduction

Using ES6 and Typescript with Express.js and Node.js

Configuring WebPack for use in Node.js applications

Optimizing asset delivery with gzip compression in Express

Optimizing images for delivery with WebPack

Optimizing Font-Awesome with custom font generation

Debugging

Introduction

Debugging Node.js using the debug module

Debugging Node.js using node-inspector in Google Chrome

Debugging Node.js using JetBrain's WebStorm IDE

Production error tracking and debugging with Sentry.io

Automated Testing

Introduction

Creating unit tests for Node.js using the Mocha testing library

Creating integration tests for Express REST APIs

Integrating an ESLint test suite into your Mocha tests

Cross-browser and device testing with BrowserSync

Whats new in Angular 4

Angular 4 Improvements and New Features

Angular 4 Deprecations and API Changes

Customer Reviews

3 (1)

5 star

4 star

3 star

100%

2 star

1 star

Handling 404 errors in an Angular project

A common problem with web applications is a user landing on an invalid URI; this error, known as the venerable 404 - page not found error, is a common fallback error case when the application is unable to redirect or resolve a route in an application. Let's configure our Angular application to handle these error cases.

How to do it...

In Angular, we can use our RouterModule configuration to catch any route that doesn't match our configuration by defining a wildcard route in our configuration, as follows:

RouterModule.forRoot([
  ...
    {
      path: "**",
      component: PageNotFoundComponent
    }
])

How it works...

By setting the path as **, we will catch any route that is not first served by the routes defined above this wildcard route configuration. We then direct the user to a new component we generated with ng g component page-not-found to serve the user a 404 message informing them that the page they have attempted to reach is not available.

Your notes and bookmarks

MEAN Cookbook

By : McClay

MEAN Cookbook

By: McClay

Overview of this book

Delete Bookmark