or subscribe with
Join 6,200+ readers for one email each week.
Digests » 176
this week's favorite
You might have heard about features like “Hooks”, “Suspense”, and “Concurrent Rendering” in the previous blog posts and talks. In this post, we’ll look at how they fit together and the expected timeline for their availability in a stable release of React.
This article contains the tips that I wish I got from someone when I started writing this blog with React (yes, it still has a lot of issues!). I have written every single point based on my own experience over the last 2 years. I hope you find these helpful. Let's begin!
React-Redux is conceptually pretty simple. It subscribes to the Redux store, checks to see if the data your component wants has changed, and re-renders your component. However, there's a lot of internal complexity to make that happen, and most people aren't aware of all the work that React-Redux does internally. I'd like to dig through some of the design decisions and implementation details of how React-Redux works, and how those implementation details have changed over time.
React 16.6 adds a new feature that makes code splitting easier: React.lazy(). Let’s see how and why to use this feature with a small demo.