MCPcopy
hub / github.com/thebuilder/react-intersection-observer

github.com/thebuilder/react-intersection-observer @v10.0.3 sqlite

repository ↗ · DeepWiki ↗ · release v10.0.3 ↗
64 symbols 180 edges 21 files 3 documented · 5%
README

react-intersection-observer

[![Version Badge][npm-version-svg]][package-url] [![Test][test-image]][test-url] [![License][license-image]][license-url] [![Downloads][downloads-image]][downloads-url] npm package minimized gzipped size

A React implementation of the Intersection Observer API to tell you when an element enters or leaves the viewport. Contains Hooks, render props, and plain children implementations.

Features

  • 🪝 Hooks or Component API - With useInView and useOnInView it's easier than ever to monitor elements
  • ⚡️ Optimized performance - Reuses Intersection Observer instances where possible
  • ⚙️ Matches native API - Intuitive to use
  • 🛠 Written in TypeScript - It'll fit right into your existing TypeScript project
  • 🧪 Ready to test - Mocks the Intersection Observer for easy testing with Jest or Vitest
  • 🌳 Tree-shakeable - Only include the parts you use
  • 💥 Tiny bundle - Around ~1.15kB for useInView and ~1.6kB for <InView> useInView InView useOnInView

Open in StackBlitz

Installation

Install the package with your package manager of choice:

npm install react-intersection-observer --save

Usage

useInView hook

// Use object destructuring, so you don't need to remember the exact order
const { ref, inView, entry } = useInView(options);

// Or array destructuring, making it easy to customize the field names
const [ref, inView, entry] = useInView(options);

The useInView hook makes it easy to monitor the inView state of your components. Call the useInView hook with the (optional) options you need. It will return an array containing a ref, the inView status and the current entry. Assign the ref to the DOM element you want to monitor, and the hook will report the status.

import React from "react";
import { useInView } from "react-intersection-observer";

const Component = () => {
  const { ref, inView, entry } = useInView({
    /* Optional options */
    threshold: 0,
  });

  return (



      <h2>{`Header inside viewport ${inView}.`}</h2>



  );
};

Note: The first false notification from the underlying IntersectionObserver is ignored so your handlers only run after a real visibility change. Subsequent transitions still report both true and false states as the element enters and leaves the viewport.

useOnInView hook

const inViewRef = useOnInView(
  (inView, entry) => {
    if (inView) {
      // Do something with the element that came into view
      console.log("Element is in view", entry.target);
    } else {
      console.log("Element left view", entry.target);
    }
  },
  options // Optional IntersectionObserver options
);

The useOnInView hook provides a more direct alternative to useInView. It takes a callback function and returns a ref that you can assign to the DOM element you want to monitor. Whenever the element enters or leaves the viewport, your callback will be triggered with the latest in-view state.

Key differences from useInView: - No re-renders - This hook doesn't update any state, making it ideal for performance-critical scenarios - Direct element access - Your callback receives the actual IntersectionObserverEntry with the target element - Boolean-first callback - The callback receives the current inView boolean as the first argument, matching the onChange signature from useInView - Similar options - Accepts all the same options as useInView except onChange, initialInView, and fallbackInView

Note: Just like useInView, the initial false notification is skipped. Your callback fires the first time the element becomes visible (and on every subsequent enter/leave transition).

import React from "react";
import { useOnInView } from "react-intersection-observer";

const Component = () => {
  // Track when element appears without causing re-renders
  const trackingRef = useOnInView(
    (inView, entry) => {
      if (inView) {
        // Element is in view - perhaps log an impression
        console.log("Element appeared in view", entry.target);
      } else {
        console.log("Element left view", entry.target);
      }
    },
    {
      /* Optional options */
      threshold: 0.5,
      triggerOnce: true,
    },
  );

  return (



      <h2>This element is being tracked without re-renders</h2>



  );
};

Render props

To use the <InView> component, you pass it a function. It will be called whenever the state changes, with the new value of inView. In addition to the inView prop, children also receive a ref that should be set on the containing DOM element. This is the element that the Intersection Observer will monitor.

If you need it, you can also access the IntersectionObserverEntry on entry, giving you access to all the details about the current intersection state.

import { InView } from "react-intersection-observer";

 const Component = () => (
 <InView>
 {({ inView, ref, entry }) => (



        <h2>{`Header inside viewport ${inView}.`}</h2>



    )}
  </InView>
);

 export default Component;
 ```

> **Note:** `<InView>` mirrors the hook behaviour—it suppresses the very first `false` notification so render props and `onChange` handlers only run after a genuine visibility change.

### Plain children

You can pass any element to the `<InView />`, and it will handle creating the
wrapping DOM element. Add a handler to the `onChange` method, and control the
state in your own component. Any extra props you add to `<InView>` will be
passed to the HTML element, allowing you set the `className`, `style`, etc.

```jsx
import { InView } from "react-intersection-observer";

const Component = () => (
  <InView as="div" onChange={(inView, entry) => console.log("Inview:", inView)}>
    <h2>Plain children are always rendered. Use onChange to monitor state.</h2>
  </InView>
);

export default Component;

[!NOTE] When rendering a plain child, make sure you keep your HTML output semantic. Change the as to match the context, and add a className to style the <InView />. The component does not support Ref Forwarding, so if you need a ref to the HTML element, use the Render Props version instead.

API

Options

Provide these as the options argument in the useInView hook or as props on the <InView /> component.

Name Type Default Description
root Element document The Intersection Observer interface's read-only root property identifies the Element or Document whose bounds are treated as the bounding box of the viewport for the element which is the observer's target. If the root is null, then the bounds of the actual document viewport are used.
rootMargin string '0px' Margin around the root. Can have values similar to the CSS margin property, e.g. "10px 20px 30px 40px" (top, right, bottom, left). Also supports percentages, to check if an element intersects with the center of the viewport for example "-50% 0% -50% 0%".
threshold number or number[] 0 Number between 0 and 1 indicating the percentage that should be visible before triggering. Can also be an array of numbers, to create multiple trigger points.
onChange (inView, entry) => void undefined Call this function whenever the in view state changes. It will receive the inView boolean, alongside the current IntersectionObserverEntry.
trackVisibility 🧪 boolean false A boolean indicating whether this Intersection Observer will track visibility changes on the target.
delay 🧪 number undefined A number indicating the minimum delay in milliseconds between notifications from this observer for a given target. This must be set to at least 100 if trackVisibility is true.
skip boolean false Skip creating the IntersectionObserver. You can use this to enable and disable the observer as needed. If skip is set while inView, the current state will still be kept.
triggerOnce boolean false Only trigger the observer once.
initialInView boolean false Set the initial value of the inView boolean. This can be used if you expect the element to be in the viewport to start with, and you want to trigger something when it leaves.
fallbackInView boolean undefined If the IntersectionObserver API isn't available in the client, the default behavior is to throw an Error. You can set a specific fallback behavior, and the inView value will be set to this instead of failing. To set a global default, you can set it with the defaultFallbackInView()

useOnInView accepts the same options as useInView except onChange, initialInView, and fallbackInView.

InView Props

The <InView /> component also accepts the following props:

Name Type Default Description
as IntrinsicElement 'div' Render the wrapping element as this element. Defaults to div. If you want to use a custom component, please use the useInView hook or a render prop instead to manage the reference explictly.
children ({ref, inView, entry}) => ReactNode or ReactNode undefined Children expects a function that receives an object containing the inView boolean and a ref that should be assigned to the element root. Alternatively pass a plain child, to have the <InView /> deal with the wrapping element. You will also get the IntersectionObserverEntry as entry, giving you more details.

Intersection Observer v2 🧪

The new v2 implementation of IntersectionObserver extends the original API, so you can track if the element is covered by another element or has filters applied to it. Useful for blocking clickjacking attempts or tracking a

Extension points exported contracts — how you extend this code

RenderProps (Interface)
(no doc)
src/index.tsx
IntersectionOptions (Interface)
(no doc)
src/index.tsx
IntersectionObserverProps (Interface)
(no doc)
src/index.tsx

Core symbols most depended-on inside this repo

mockAllIsIntersecting
called by 65
src/test-utils.ts
intersectionMockInstance
called by 17
src/test-utils.ts
useInView
called by 14
src/useInView.tsx
useOnInView
called by 10
src/useOnInView.tsx
defaultFallbackInView
called by 6
src/observe.ts
optionsToId
called by 6
src/observe.ts
unobserve
called by 6
src/InView.tsx
useValidateOptions
called by 4
storybook/stories/story-utils.ts

Shape

Function 52
Method 7
Interface 3
Class 2

Languages

TypeScript100%

Modules by API surface

src/test-utils.ts12 symbols
src/InView.tsx10 symbols
storybook/stories/elements.tsx8 symbols
src/__tests__/useOnInView.test.tsx7 symbols
src/__tests__/useInView.test.tsx7 symbols
src/observe.ts5 symbols
src/useOnInView.tsx3 symbols
src/index.tsx3 symbols
storybook/stories/useInView.story.tsx2 symbols
storybook/stories/story-utils.ts2 symbols
storybook/stories/InView.story.tsx2 symbols
storybook/stories/useOnInView.story.tsx1 symbols

Dependencies from manifests, versioned

@arethetypeswrong/cli0.18.2 · 1×
@biomejs/biome2.3.10 · 1×
@mdx-js/react3.1.1 · 1×
@size-limit/preset-small-lib12.0.0 · 1×
@storybook/addon-docs10.1.10 · 1×
@storybook/addon-vitest10.1.10 · 1×
@storybook/builder-vite10.1.10 · 1×
@storybook/react10.1.10 · 1×
@storybook/react-vite10.1.10 · 1×
@testing-library/jest-dom6.9.1 · 1×
@testing-library/react16.3.1 · 1×

For agents

$ claude mcp add react-intersection-observer \
  -- python -m otcore.mcp_server <graph>

⬇ download graph artifact