You're reading from Redux Made Easy with Rematch Reduce Redux boilerplate and apply best practices with Rematch

Product type Paperback

Published in Aug 2021

Publisher Packt

ISBN-13 9781801076210

Length 286 pages

Edition 1st Edition

Languages

JavaScript

Tools

Redux

Concepts

Front End Web Development

Author (1):

Sergio Moreno

View More author details

Table of Contents (18) Chapters

Preface

1. Section 1: Rematch Essentials

2. Chapter 1: Why Redux? An Introduction to Redux Architecture FREE CHAPTER

3. Chapter 2: Why Rematch over Redux? An Introduction to Rematch Architecture

4. Chapter 3: Redux First Steps – Creating a Simple To-Do App

5. Chapter 4: From Redux to Rematch – Migrating a To-Do App to Rematch

6. Section 2: Building Real-World Web Apps with Rematch

7. Chapter 5: React with Rematch – The Best Couple – Part I

8. Chapter 6: React with Rematch – The Best Couple – Part II

9. Chapter 7: Introducing Testing to Rematch

10. Chapter 8: The Rematch Plugins Ecosystem

11. Section 3: Diving Deeper into Rematch

12. Chapter 9: Composable Plugins – Create Your First Plugin

13. Chapter 10: Rewrite a Full Code Base from JavaScript to TypeScript

14. Chapter 11: Rematch with React Native and Expo – A Real-World Mobile App

15. Chapter 12: Rematch Performance Improvements and Best Practices

16. Chapter 13: Conclusion

17. Other Books You May Enjoy

Packt is searching for authors like you

Creating the shop business logic

As we explained in Chapter 5, React with Rematch – The Best Couple – Part I, in the Preparing the environment section, we're using an interesting NPM module named json-server (https://github.com/typicode/json-server) that converts static JavaScript Object Notation (JSON) files to API endpoints ready to use. This module is really powerful for this book because it will allow us to call a fake API to access the data. A real API recovers the data from a database, but in our case, this data is just static. However, the way this data is accessed from our side, on the frontend, is the same as would be employed in a real API.

When we start our application with yarn dev, it automatically runs a server on http://localhost:3000 to see the refreshed changes of our frontend application, while also running a server on http://localhost:8000. If we access this URL, we should see something like this: