Book Image

JavaScript Design Patterns

By : Hugo Di Francesco
Book Image

JavaScript Design Patterns

By: Hugo Di Francesco

Overview of this book

Unlock the potential of JavaScript design patterns, the foundation for development teams seeking structured and reusable solutions to common software development challenges in this guide to improving code maintainability, scalability, and performance. Discover how these patterns equip businesses with cleaner and more maintainable code, promote team collaboration, reduce errors, and save time and costs. This book provides a comprehensive view of design patterns in modern (ES6+) JavaScript with real-world examples of their deployment in professional settings. You’ll start by learning how to use creational, structural, and behavioral design patterns in idiomatic JavaScript, and then shift focus to the architecture and UI patterns. Here, you’ll learn how to apply patterns for libraries such as React and extend them further to general web frontend and micro frontend approaches. The last section of the book introduces and illustrates sets of performance and security patterns, including messaging and events, asset and JavaScript loading strategies, and asynchronous programming performance patterns. Throughout the book, examples featuring React and Next.js, in addition to JavaScript and Web API examples, will help you choose and implement proven design patterns across diverse web ecosystems, transforming the way you approach development.
Table of Contents (16 chapters)
Part 1:Design Patterns
Part 2:Architecture and UI Patterns
Part 3:Performance and Security Patterns

Static generation with dynamic paths

It can be useful to pre-generate pages with dynamic paths and contents.

We could use getServerSideProps and render the pages on demand. In the context that we’re working in, that would be valid for a “cart” page.

getServerSideProps is server-side rendering, as we’ve seen previously. The reason a cart page should probably be server-rendered is that it can change very quickly, based on end user interaction. An example of a page that is dynamic but wouldn’t change quickly based on an end user action is a “view single product” page. We’ll see how to statically generate that after the cart page example.

We create a pages/cart.js file, where we provide the following getServerSideProps, which loads the cart, figures out the relevant product IDs (per cart content), and loads them (in order to display some information about them):

export async function getServerSideProps({ query }) {