You're reading from Real-World Next.js Build scalable, high-performance, and modern web applications using Next.js, the React framework for production

Product type Paperback

Published in Feb 2022

Publisher Packt

ISBN-13 9781801073493

Length 366 pages

Edition 1st Edition

Languages

Typescript

Tools

Next.js

Concepts

Front End Web Development

Author (1):

Michele Riva

View More author details

Table of Contents (19) Chapters

Preface

1. Part 1: Introduction to Next.js

2. Chapter 1: A Brief Introduction to Next.js FREE CHAPTER

3. Chapter 2: Exploring Different Rendering Strategies

4. Chapter 3: Next.js Basics and Built-In Components

5. Part 2: Hands-On Next.js

6. Chapter 4: Organizing the Code Base and Fetching Data in Next.js

7. Chapter 5: Managing Local and Global States in Next.js

8. Chapter 6: CSS and Built-In Styling Methods

9. Chapter 7: Using UI Frameworks

10. Chapter 8: Using a Custom Server

11. Chapter 9: Testing Next.js

12. Chapter 10: Working with SEO and Managing Performance

13. Chapter 11: Different Deployment Platforms

14. Part 3: Next.js by Example

15. Chapter 12: Managing Authentication and User Sessions

16. Chapter 13: Building an E-Commerce Website with Next.js and GraphCMS

17. Chapter 14: Example Projects and Next Steps for Learning More

18. Other Books You May Enjoy

Packt is searching for authors like you

CSS modules

In the previous section, we saw a CSS-in-JS library, meaning that we had to write our CSS definitions in JavaScript, transforming those styling rules to plain CSS at runtime or compile time, depending on which library we choose and how we configure it.

While I personally like the CSS-in-JS approach, I eventually recognized that it has some significant drawbacks to consider when choosing the styling method for a new Next.js app.

Many CSS-in-JS libraries don't provide good IDE/code editor support, making things way harder for developers (no syntax highlighting, autocomplete, linting, and so on). Also, using CSS-in-JS forces you to adopt more and more dependencies, making your application bundle bigger and slower.

Talking about performance, here's another big drawback: even if we pre-generate CSS rules on the server side, we would need to re-generate them after React hydration on the client side. That adds a high runtime cost, making the web application...