Intersection Observer using React

Today we are gonna explore how to use the intersection observer API in React and see some useful examples, you can find the code in the following repository, let's begin.

---

Mozilla web documentation describes the intersection observer API as:

lets code register a callback function that is executed whenever an element they wish to monitor enters or exits another element (or the viewport), or when the amount by which the two intersect changes by a requested amount. This way, sites no longer need to do anything on the main thread to watch for this kind of element intersection, and the browser is free to optimize the management of intersections as it sees fit.

In plain english, it allows us to detect when certain elements are visible in our viewport, this only happens when the element meets your desired intersection ratio.

As you can see, if we scroll down the page the intersection ratio will be going up until it meets the designed threshold and that's when the callback function is executed.

---

Initialization

The intersection observer object constructor requires two arguments:

1. Callback function
2. Options

Just like that we are ready to see some action but first we need to know what each option means, the options argument is an object with the following values:

• root: The element that is used as the viewport for checking visibility of the target. Must be the ancestor of the target. Defaults to the browser viewport if not specified or if null.
• rootMargin: This set of values serves to grow or shrink each side of the root element's bounding box before computing intersections, the options are similar to those of margin in CSS.
• threshold: Either a single number or an array of numbers which indicate at what percentage of the target's visibility the observer's callback should be executed, ranges from 0 to 1.0, where 1.0 means every pixel is visible in the viewport.

---

Using React.js

Now let's see an implementation of the intersection observer API using react.

1. Start with a reference to the element we want to observe, use the react hook useRef.
2. Create a state variable isVisible, we are gonna use it to display a message whenever our box is in the viewport.
3. Declare a callback function that receives an array of IntersectionObserverEntries as a parameter, inside this function we take the first and only entry and check if is intersecting with the viewport and if it is then we call setIsVisible with the value of entry.isIntersecting (true/false).
4. Create the options object with the same values as the image.
5. Add the react hook useEffect and create an observer contructor using the callback function and the options we just created before, it's optional in our case but you can return a cleanup function to unobserve our target when the component unmounts.
6. Set the useRef variable on the element we want to observe.
7. Let's add a background and some properties to our HTML elements
8. It's done, simple and easy!

remember this is just a basic implementation and there are many different ways of doing it.

---

Hooking it up

Let's now implement the same code we just did before but separating all the logic into a new hook called useElementOnScreen.

1. Create a new function called useElementOnScreen with the parameter options
2. Move useRef, useState and the entire useEffect inside our new shiny hook.
3. Now the only thing missing in our hook is the return statement, we pass isVisible and containerRef as an array.
4. okay, we are almost there, we just need to call it in our component and see if it works!

1. Import the recently created hook file into our component.
2. Initialize it with the options object.
3. Just like that we are done.

Congratulations we have successfully used the intersection observer API and we even made a hook for it!

---

Final words

Thanks for reading this, Hopefully it helped someone getting started with the IO API using react, stay safe ❤️!

Comments

[surya_dev]

It's beneficial! I have been thinking about how to implement the IntersectionObserver API in React. It really helps a lot. How can we use Tailwind CSS for DOM manipulation?

[bekdev]

Thank you so much! I spent whole my day and couldn't make it work until I find this article. 🙏❤️

[Igor Sukharev]

Your example is not entirely correct. The containerRef will not trigger the useEffect, and it should not be included in its dependencies. For more details, please refer to this article medium.com/@teh_builder/ref-object...

[jbilee]

This helped me tremendously! Tysm!

[Bjørnar Hagen 🐻]

Great article! :) Though I wish the code was not images

[T]

What kind of person are you if you post code as images? Jsj fk...

[Bayu Rizky Nurseto]

I want to ask something, is it possible to call API only when certain section is visible? use that way? thankyou
Great article btw

[Igor Perzic]

I think there are couple of things worth pointing out:

1. Ref should be removed from the dependency array because refs never change reference (hence their name), thus never triggering useEffect (or any other hook that has a dependency array, for that matter).
2. Options dependency reference is changed on every render, because it's being re-declared as new object.

That being said, we might as well omit the dependency array altogether, it will have the same effect.

[Eduardo Hernández Soto]

if are multiple refs? or elements?

[Amal Vaishnav]

Thanks for this, helped me a great deal!

[almeida.tsx]

Amazing!!!!!!

I use it in a header, it's done well.