In two recent articles, I shared 2 different methods on how to prevent re-renders in React.
I recommend reading those articles first before continuing onto this one.
In React, React components aren’t just built through classes. React component may built in a more function style approach.
React functional components are React components built in a function rather than class.
As you can see above, there are 3 styles of creating a React functional component.
The one that really stands out the most is style #3. Note that in that style, you can’t add any logic into the function.
React functional components are great, because it’s really is to read, and really easy to maintain.
But it does loses some of features that the React.Component class provides. Luckily some of those features, if not, near all, have been provided through there recent addition called React hooks.
React functional components do not have lifecycle methods.
Let’s study the code below.
I will be using the new React hook api in these examples. If you’re not familiar I recommend you reading these articles:
We have 2 React components. One is a greeting component that prints out “Hello [person_name]”, and it also logs in the console when it renders.
The second React component is the App component, and it uses the Greeting component.
But the App component is doing a couple of other things. One it’s creating a new state property called, counter.
And when the App component mounts, it updates the the counter value every 2 seconds.
So what is gonna happen?
Well, anytime a React component prop or state changes, it’s going to get re-rendered. And that React component that has changed, will force any other children React components to re-render as well.
So in the example above, the Greeting component will always get re-rendered.
I want to avoid re-rendering the Greeting component, but how?
Since React functional components don’t have access to shouldComponentUpdate(), and it’s not a React pure component class, I’ll have to use a new strategy to achieve a pure like function behavior.
We’re gonna memorize it! I mean memoize it!
To optimize, and prevent multiple React renders, I’m going to use another React tool called React.memo().
In programming, memoization is an optimization technique. It’s primarily used to speed up computing by story the result of a function and returning the cached result, when the same inputs occur again.
Keyword, same inputs.
If we take a look at the Greeting component, I think it fits the criteria of the definition.
The Greeting component is a function, and it’s receiving the same inputs every single time (name equals “Ruben”).
So let’s put it to use.
All I need to do in the Greeting component is wrap it another function called React.memo().
In the console, you can see that the App component is still rendering, but the Greeting component only rendered once.
Thus avoiding multiple renders, hoorraayyy!
You might run into React.useMemo() and think that it’s the same as React.memo(). In a way, yes but no.
React.memo() is a HOC (higher order component) meant to optimize a React functional component.
React.useMemo() is more generic, and optimizes a value.
React.memo() is a great React tool that lets you optimize performance, and replicate a shouldComponentUpdate and React.PureComponent for functional components.
Don’t confuse it with React.useMemo()!