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)

Routing and navigating

With the React router, you just used a <Link> component to navigate from one page to another, or used methods to programmatically open a different page. In RN, there is a different way of working, and the react-navigation package is practically the de facto standard. Here, you define a navigator (there are several kinds to pick from) and provide it with the screens (views) that it should handle, and then forget about it! The navigator will handle everything on its own, showing and hiding screens, adding tabs or a sliding drawer, or whatever it needs, and you don't have to do anything extra!

In this recipe, we'll revisit an example from earlier pages of this book, and show how the router is written differently, to highlight differences in style.

There's more to navigation than what we'll see here. Check out the API documentation...