Book Image

Modern JavaScript Web Development Cookbook

By : Federico Kereki
Book Image

Modern JavaScript Web Development Cookbook

By: Federico Kereki

Overview of this book

JavaScript has evolved into a language that you can use on any platform. Modern JavaScript Web Development Cookbook is a perfect blend of solutions for traditional JavaScript development and modern areas that developers have lately been exploring with JavaScript. This comprehensive guide teaches you how to work with JavaScript on servers, browsers, mobile phones and desktops. You will start by exploring the new features of ES8. You will then move on to learning the use of ES8 on servers (with Node.js), with the objective of producing services and microservices and dealing with authentication and CORS. Once you get accustomed to ES8, you will learn to apply it to browsers using frameworks, such as React and Redux, which interact through Ajax with services. You will then understand the use of a modern framework to develop the UI. In addition to this, development for mobile devices with React Native will walk you through the benefits of creating native apps, both for Android and iOS. Finally, you’ll be able to apply your new-found knowledge of server-side and client-side tools to develop applications with Electron.
Table of Contents (15 chapters)

Configuring your server for different environments

No matter what you develop, it's certain that you'll work at least with a couple of environments, development and production, and settings for your code won't be the same. For example, you won't use the same configuration for security, to access a database, to log errors, or to connect to analytics services, and so on: when running in your development environment, you'll need a certain setup, and for production there may be many changes.

You could set everything up in your code, but having users, passwords, IPs, and other sensitive data in plain text and saved in a source code repository that might get hacked isn't a good recipe for security. You should deal exclusively with your development configuration and leave the actual deployment to production to a different team, which will safely deal with...