Bring ReactIntersectionObserver over today, your React children will love it!

React Intersection Observer is a React component, acting as a wrapper for the IntersectionObserver API. It is fully declarative and takes care of all the imperative parts for you.

React Intersection Observer is good at:

• reusing instances: comparing the passed options
• performance: chooses smartly when to re-render and when to re-observe
• being unopinionated: how to handle visibility changes is left entirely up to the developer
• being intuitive: looks like the Native API

Table of Contents

• Getting started
• What does IntersectionObserver do?
• Why use this component?
  • No bookkeeping
  • No extra markup
  • Easy to adopt
• Documentation
  • Demos
  • Recipes
  • Missing DOM nodes when observing
  • Options
  • Notes
• Polyfill
  • Caveats
• IntersectionObserver's Browser Support
  • Out of the box
  • Using polyfill
• Contributing

---

Getting started

1npm install --save @researchgate/react-intersection-observer

:warning: Please make sure you have the minimum node version installed (as defined in the package.json)

Otherwise you run into this build error:

The engine "node" is incompatible with this module. Expected version ">=10.18.1". Got "10.15.3"

Usage

1import React from 'react';
2import 'intersection-observer'; // optional polyfill
3import Observer from '@researchgate/react-intersection-observer';
4
5class ExampleComponent extends React.Component {
6  handleIntersection(event) {
7    console.log(event.isIntersecting);
8  }
9
10  render() {
11    const options = {
12      onChange: this.handleIntersection,
13      root: '#scrolling-container',
14      rootMargin: '0% 0% -25%',
15    };
16
17    return (
18      <div id="scrolling-container" style={{ overflow: 'scroll', height: 100 }}>
19        <Observer {...options}>
20          <div>I am the target element</div>
21        </Observer>
22      </div>
23    );
24  }
25}

Optionally add the polyfill and make sure it's required on your dependendencies for unsupporting browsers:

1npm install --save intersection-observer

What does IntersectionObserver do?

IntersectionObservers calculate how much of a target element overlaps (or "intersects with") the visible portion of a page, also known as the browser's "viewport":

Dan Callahan · 

Why use this component?

The motivation is to provide the easiest possible solution for observing elements that enter the viewport on your React codebase. It's fully declarative and all complexity is abstracted away, focusing on reusability, and low memory consumption.

No bookkeeping

It's built with compatibility in mind, adhering 100% to the native API implementation and DSL, but takes care of all the bookkeeping work for you.

Instances and nodes are managed internally so that any changes to the passed options or tree root reconciliation cleans up and re-observes nodes on-demand to avoid any unexpected memory leaks.

No extra markup

ReactIntersectionObserver does not create any extra DOM elements, it attaches to the only child you'll provide to it. This is done using findDOMNode to retrieve the first DOM node found. If your child already has an existing ref, either a callback or object (from createRef), these will be handled normally in either case.

Easy to adopt

When using ReactIntersectionObserver the only required prop is the onChange function. Any changes to the visibility of the element will invoke this callback, just like in the native API - you’ll receive one IntersectionObserverEntry argument per change. This gives you an ideal and flexible base to build upon.

Some of the things you may want to use ReactIntersectionObserver for:

• Determining advertisement impressions
• Lazy loading - Images, or anything that will enter the viewport
• Occlusion culling - Don't render an object until is close to the viewport edges
• Sentinel Scrolling - Infinite scroller with a recycled Sentinel

Documentation

Demos

Find multiple examples and usage guidelines under: https://researchgate.github.io/react-intersection-observer/

Recipes

Recipes are useful code snippets solutions to common problems, for example, how to use ReactIntersectionObserver within a Higher Order Component.
Here's how to create an element monitoring component:

1import React, { Component } from 'react';
2import PropTypes from 'prop-types';
3import Observer from '@researchgate/react-intersection-observer';
4
5export default class ViewableMonitor extends Component {
6  static propTypes = {
7    tag: PropTypes.node,
8    children: PropTypes.func.isRequired,
9  };
10
11  static defaultProps = {
12    tag: 'div',
13  };
14
15  state = {
16    isIntersecting: false,
17  };
18
19  handleChange = ({ isIntersecting }) => {
20    this.setState({ isIntersecting });
21  };
22
23  render() {
24    const { tag: Tag, children, ...rest } = this.props;
25
26    return (
27      <Observer {...rest} onChange={this.handleChange}>
28        <Tag>{children(this.state.isIntersecting)}</Tag>
29      </Observer>
30    );
31  }
32}

1import React from 'react';
2import ViewableMonitor from './ViewableMonitor';
3
4export default () => (
5  <ViewableMonitor>
6    {(isViewable) => (isViewable ? 'I am viewable' : 'I am still hiding')}
7  </ViewableMonitor>
8);

Discover more recipes in our examples section.

Missing DOM nodes when observing

In cases where there isn't a DOM node available to observe when rendering, you'll be seeing an error logged in the console:

1ReactIntersectionObserver: Can't find DOM node in the provided children. Make sure to render at least one DOM node in the tree.

This somewhat helpful and descriptive message is supposed to help you identify potential problems implementing observers early on. If you miss the exception for some reason and ends up in production (prone to happen with dynamic children), the entire tree will unmount so be sensible about placing your error boundaries.

Ultimately the way to avoid this is to either make sure you are rendering a DOM node inside your <Observer>, or to disable the observer until there's one <Observer disabled>.

Options

root: HTMLElement|string | default window object

The element or selector string that is used as the viewport for checking visibility of the target.

rootMargin: string | default 0px 0px 0px 0px

Margin around the root. Specify using units px or % (top, right, bottom left). Can contain negative values.

threshold: number|Array<number> | default: 0

Indicates at what percentage of the target's visibility the observer's callback should be executed. If you only want to detect when visibility passes the 50% mark, you can use a value of 0.5. If you want the callback run every time visibility passes another 25%, you would specify the array [0, 0.25, 0.5, 0.75, 1].

disabled: boolean | default: false

Controls whether the element should stop being observed by its IntersectionObserver instance. Useful for temporarily disabling the observing mechanism and restoring it later.

onChange (required): (entry: IntersectionObserverEntry, unobserve: () => void) => void

Function that will be invoked whenever an observer's callback contains this target in its changes.

children: React.Element<*>|null

Single React component or element that is used as the target (observable). As of v1.0.0, children can be null. Null children won't be observed.

Notes

• According to the spec, an initial event is being fired when starting to observe a non-intersecting element as well.
  • Edge's implementation seems to miss the initial event, although Edge 16 behavior aligns with the spec.
• Changes happen asynchronously, similar to the way requestIdleCallback works.
• Although you can consider callbacks immediate - always below 1 second - you can also get an immediate response on an element's visibility with observer.takeRecords().
• The primitives Map an Set are required. You may need to include a polyfill for browsers lacking ES2015 support. If you're using babel, include "babel-polyfill" somewhere to your codebase.

Polyfill

When needing the full spec's support, we highly recommend using the IntersectionObserver polyfill.

Caveats

Ealier Spec

Earlier preview versions of Edge and prior to version 58 of Chrome, the support for isIntersecting was lacking. This property was added to the spec later and both teams where unable to implement it earlier.

Performance issues

As the above-mentioned polyfill doesn't perform callback invocation asynchronously, you might want to decorate your onChange callback with a requestIdleCallback or setTimeout call to avoid a potential performance degradation:

1onChange = (entry) => requestIdleCallback(() => this.handleChange(entry));

IntersectionObserver's Browser Support

Out of the box

Chrome	51 [1]
Firefox (Gecko)	55 [2]
MS Edge	15
Internet Explorer	Not supported
Opera [1]	38
Safari	12.1
Chrome for Android	59
Android Browser	56
Opera Mobile	37

• [1]reportedly available, it didn't trigger the events on initial load and lacks isIntersecting until later versions.
• [2] This feature was implemented in Gecko 53.0 (Firefox 53.0 / Thunderbird 53.0 / SeaMonkey 2.50) behind the preference dom.IntersectionObserver.enabled.

Using polyfill

Safari	6+
Internet Explorer	7+
Android	4.4+

Contributing

We'd love your help on creating React Intersection Observer!

Before you do, please read our Code of Conduct so you know what we expect when you contribute to our projects.

Our Contributing Guide tells you about our development process and what we're looking for, gives you instructions on how to issue bugs and suggest features, and explains how you can build and test your changes.

Haven't contributed to an open source project before? No problem! Contributing Guide has you covered as well.