In simple cases, React Hooks will magically do exactly what you meant for, but in other cases, their behavior can feel inconsistent and unpredictable. the next article will try to deeply explain and demonstrate React hooks behavior.
The article consists of three main sections:
- Definitions — This section summarizes important terms in React and web development which necessary for the rest of the article.
- React Hooks — explains what type of hooks exists, what the difference between them, and how they behave.
- Examples — examples that demonstrate everything explained in this article with an increasing difficulty rate.
Which of you that will finish reading the article to the end, and will really understand the latest example, will no longer be surprised by unexpected problems when using hooks in components with a complicated lifecycle.
The article is not for starters, and I will assume that you have some experience with React and React hooks.
code sandbox of all examples: https://codesandbox.io/s/github/Eliav2/how-react-hooks-work
webpage of sandbox(examples on full screen): https://d47vv.csb.app/
GitHub repo: https://github.com/Eliav2/how-react-hooks-work
read in your preferred platform:
For best readability and for most updated version I would strongly recommend read from Home page. Comments and questions can be left on your preferred platform.
If you are not a React expert, It is strongly recommended to read the definitions section. You can start from the example section and then return to this section later if something is not clear.
the more important definitions here are: render, update, react hook and phase.
- browser DOM — a tree of HTML elements. These elements make up everything the user sees in the browser, including this very page.
- React — A library for manipulating React components.
- React component — function(or class) that holds stateful logic managed by React lib, that component usually returns UI elements based on the stateful logic of the same component.
React have class components, and functional components(FC).
- React tree — a tree of React components(like the tree you can see in React devtools). this is not the same as the browser’s DOM tree.
- react renderer — ReactDOM in web(or react-native in mobile) — a library that knows how to manipulate React tree and ‘render’ it into the browser’s DOM in the desired location(in react apps usually to
rootelement). The renderer managing a Virtual DOM (VDOM) which is created and updated based on the given React tree.
- render — this is the moment when React tree is created based on the current state.
then the tree is passed to the renderer that will update the VDOM, and then will flush the changes into the browser’s DOM.
- update — when we say that a component ‘updates’, we are saying that the function component body re-executed (with possibly different props). it is possible that more the one update cycle will occur before a render. examples of the difference between
- react hook — A primitive that shares stateful logic with the parent Component. this is the reason hooks allowed only inside a body of a function component — hook is
hookedto the parent component stateful logic. The hook and the parent component updates are triggers in the same phase, and the effects of the hook and the FC also fire in the same phase.
- a component’s phase — this is not an official term, I’m using this term in this tutorial to describe a different point of time in a React component. update: also React calls this phase.
Note — These definitions were summarized by me and may not be accurate, but they are sufficient to understand the rest of the article.
There 2 types of React hooks:
- State hooks — like
useReducer. these hooks use and possibly manipulates the parent component stateful logic.
- Effect hooks — one of
useLayoutEffect. these hooks receive a callback function and usually a dependency array. the callback function will be scheduled by React to fire on a later phase(see definition above). the exact phase is dependent on the effect that was chosen.
Effects from the same type will be executed in the order of declaration.
- Calling state hook from effect(like useEffect) will schedule another render.
- Calling state hook from FC body will schedule another update call.
these are the phases of a render:
- update call — the moment FC body is executed. this is always the first phase of a render.
- useLayoutEffect — it is triggered immediately after all the scheduled update calls executed, just before flushing changes to the browser’s DOM and before useEffect.
React docs say:
Updates scheduled inside useLayoutEffect will be flushed synchronously before the browser has a chance to paint.
- useEffect — it is triggered after all scheduled updates calls has been executed. this is always the last phase of a render.
after these phases, the ‘render’ step is completed and then ReactDOM will do the ‘commit’ step which basically just saying updating the browser’s DOM based on the virtual DOM created by the render step. the ‘commit’ phase is not relevant for the purpose of this article.
before each effect is fired a cleanup function is fired(if scheduled). the cleanup effects are:
- useLayoutEffect cleanup
- useEffect cleanup
Note — cleanup effect will never fire on the first render(because there is no prior effect to cleanup from).
Render cycle summary:
per render cycle: Each effect fires the most 1 times, excluding update call which fires at least once.
The effects are fired in this order(excluding the first render), and only if was scheduled:
- updateCall — may be called several times for a single render, and will occur one after another before any effect!
- useLayoutEffect cleanup
- useEffect cleanup
the AllPhases example demonstrates this very well.
important Note — each line of the code that will come next are part of the tutorial, even the comments. read them all to follow along. these examples are self-explanatory.
OK enough words. see the next example.
what order of logs would you expect when the component mounts? think for a second and replace the ‘?’:
well, the order is:
as we explained earlier, the function body fire first and then the effects.
what will happen if we will replace the effects, does the order will change?
well, the order does change, and will be:
this is because effect hooks from the same type(here
useEffect) are scheduled by React for the same phase and will be executed in the order of declaration, this is a common mistake to think that useEffect with an empty dependency array will fire on the mount and on a different phase from useEffect with no dependency array.
now let’s create a log helper hook
useLog that will let us keep track of the component phase for later examples:
call.current will 'tick' at the same rate of the parent component because of hooks natures. This is simplified
useLog, you will see different useLog hook in the
if we will trigger unmount after mounting the order of the logs will be:
when a component goes through unmounting step — the update phase does not happen, only the effect fire, in the order of declaration.
Effect vs LayoutEffect
useLayoutEffect is executed before useEffect:
This demonstrates all the different phases combined. after mount another dumy re-render is scheduled, we will use absolute timing for this example to see when each phase is executed:
this example deeply demonstrates all the different possible phases while a component renders. make sure you understand that before proceeding to the next examples.
when you set a state while in the update phase another update phase will be scheduled by React. let’s try to force React to trigger 10 update calls before rendering.
as we can see, we forced React to re-call the function body 10 times before performing the render. we can also notice that the render phase occurred 0.245ms after the last update call.
Ok, so we saw what happens when we update the state while in the update phase, but what happens if we try to update the state when we are no longer in the update state? well, React will schedule an entire re-render cycle for the component. each render cycle will also include at least one update call.
let’s force 5 render cycles:
we can see that each render cycle comes with an update call.
now let's say we want 5 update calls for each render. let’s force 3 renders:
Let’s combine the last 3 examples into the common parent.
now stop. think. what would you expect? does each component will go through her own update-render phases or maybe the update calls will occur one after another and then the effects one after another?
the entire tree goes through the phase of the update, and only then the effects are fired.
phew! that was tough. if you read and understand everything to this point you can confidently say that you understand React hook’s nature.
Component with complicated lifecycle
so why do we need to understand all of this? well, in simple cases you don’t, but when dealing with a component with a complicated lifecycle you can sometimes get confused by the component’s behavior. an example of such a component will be react-xarrow which needs to trigger callback on different phases to get the right dimensions and activate animations callbacks on different phases, for that react-xarrows using react-use-call-onnext-render to schedule callback for later phases.
- on each phase: An entire React Tree goes through each phase in a render cycle one after another, which means that if one component in the tree is in the useEffect phase for example, all the different components in the tree are currently also in the useEffect phase.
- for a React Tree: on the same phase, each Component on React tree will fire each phase in the same order of the declaration of the react component in the React tree. for example: if
Comp1in the tree before
Comp2then the useEffect of
Comp1will fire and only then the useEffect
- On the same React component: on the same phase, each effect from the same type will fire in the order of declaration.
That’s it! you now understand what really going on when you asks React to update some state in some component.
If you liked this tutorial make sure to like it and share it! thank you for reading until the end!
Originally published at http://github.com