Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
React Design Patterns and Best Practices

You're reading from   React Design Patterns and Best Practices Build easy to scale modular applications using the most powerful components and design patterns

Arrow left icon
Product type Paperback
Published in Jan 2017
Publisher Packt
ISBN-13 9781786464538
Length 318 pages
Edition 1st Edition
Languages
Tools
Arrow right icon
Author (1):
Arrow left icon
Michele Bertoli Michele Bertoli
Author Profile Icon Michele Bertoli
Michele Bertoli
Arrow right icon
View More author details
Toc

Table of Contents (13) Chapters Close

Preface 1. Everything You Should Know About React FREE CHAPTER 2. Clean Up Your Code 3. Create Truly Reusable Components 4. Compose All the Things 5. Proper Data Fetching 6. Write Code for the Browser 7. Make Your Components Look Beautiful 8. Server-Side Rendering for Fun and Profit 9. Improve the Performance of Your Applications 10. About Testing and Debugging 11. Anti-Patterns to Be Avoided 12. Next Steps

CSS in JS


In the community, everyone agrees that a revolution took place in the styling of React components in November 2014, when Christopher Chedeau gave a talk at the NationJS conference.

Also known as Vjeux on the Internet, Christopher works at Facebook and contributes to React. In his talk, he went through all the problems related to CSS at scale that they were facing at Facebook.

It is worth understanding all of them, because some are pretty common and they will help us introduce concepts such as inline styles and locally scoped class names.

The following slide, taken from the presentation, lists the main issues with CSS:

The first well-known problem of CSS is that all the selectors are global. No matter how we organize our styles, using namespaces or a BEM-like methodology, in the end, we are always polluting the global namespace, which we all know is wrong. It is not only wrong on principle, but it also leads to many errors in big codebases, and it makes maintainability very hard in...

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime
Banner background image