@researchgate/react-intersection-observer

> 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

---

Getting started

``shell
npm 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

`jsx
import React from 'react';
import 'intersection-observer'; // optional polyfill
import Observer from '@researchgate/react-intersection-observer';

class ExampleComponent extends React.Component {
handleIntersection(event) {
console.log(event.isIntersecting);
}

render() {
const options = {
onChange: this.handleIntersection,
root: '#scrolling-container',
rootMargin: '0% 0% -25%',
};

return (


`shell
npm 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 · 

!Graphic example

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.

$3

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.

$3

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.

$3

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

$3

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

![demo](https://researchgate.github.io/react-intersection-observer/)

$3

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:

`jsx
import React, { Component } from 'react';
import PropTypes from 'prop-types';
import Observer from '@researchgate/react-intersection-observer';

export default class ViewableMonitor extends Component {
static propTypes = {
tag: PropTypes.node,
children: PropTypes.func.isRequired,
};

static defaultProps = {
tag: 'div',
};

state = {
isIntersecting: false,
};

handleChange = ({ isIntersecting }) => {
this.setState({ isIntersecting });
};

render() {
const { tag: Tag, children, ...rest } = this.props;

return (

{children(this.state.isIntersecting)}

);
}
}
`

`jsx
import React from 'react';
import ViewableMonitor from './ViewableMonitor';

export default () => (

{(isViewable) => (isViewable ? 'I am viewable' : 'I am still hiding')}

);
`

Discover more recipes in our examples section.

$3

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

`js
ReactIntersectionObserver: 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 , or to disable the observer until there's one
.

$3

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 | 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.

$3

- 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.

$3

#### 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:

`js
onChange = (entry) => requestIdleCallback(() => this.handleChange(entry));
`

IntersectionObserver's Browser Support

$3

- [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`.

$3

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.