npm package discovery and stats viewer.

Discover Tips

  • General search

    [free text search, go nuts!]

  • Package details

    pkg:[package-name]

  • User packages

    @[username]

Sponsor

Optimize Toolset

I’ve always been into building performant and accessible sites, but lately I’ve been taking it extremely seriously. So much so that I’ve been building a tool to help me optimize and monitor the sites that I build to make sure that I’m making an attempt to offer the best experience to those who visit them. If you’re into performant, accessible and SEO friendly sites, you might like it too! You can check it out at Optimize Toolset.

About

Hi, 👋, I’m Ryan Hefner  and I built this site for me, and you! The goal of this site was to provide an easy way for me to check the stats on my npm packages, both for prioritizing issues and updates, and to give me a little kick in the pants to keep up on stuff.

As I was building it, I realized that I was actually using the tool to build the tool, and figured I might as well put this out there and hopefully others will find it to be a fast and useful way to search and browse npm packages as I have.

If you’re interested in other things I’m working on, follow me on Twitter or check out the open source projects I’ve been publishing on GitHub.

I am also working on a Twitter bot for this site to tweet the most popular, newest, random packages from npm. Please follow that account now and it will start sending out packages soon–ish.

Open Software & Tools

This site wouldn’t be possible without the immense generosity and tireless efforts from the people who make contributions to the world and share their work via open source initiatives. Thank you 🙏

© 2026 – Pkg Stats / Ryan Hefner

react-bounds.js

v1.0.8

Published

Asynchronous boundary detection

Downloads

31

Readme

React-Bounds.js

react-bounds.js on NPM

Asynchronous boundary detection for react, based on Bounds.js by Christopher Cavalea.

DEMO

Why

Whether you're lazy-loading images, implementing infinite-scroll, or avoiding an ex-lover... it's important to set boundaries.

Historically, boundary detection required a mix of event handlers, loops, and calls to getBoundingClientRect. Since these operations run on the main thread, performance would suffer.

React-Bounds.js defies these expectations, providing a simple and powerful API. It detects intersections between elements asynchronously, keeping complex operations off the main thread and improving performance.

Usage

Follow these steps to get started:

  1. Install
  2. How to Use
  3. Options
  4. Browser Support

Install

Using NPM or yarn, install react-bounds.js, and save it to your package.json dependencies.

$ npm install react-bounds.js
// or
$ yarn add react-bounds.js

Then import, naming it according to your preference.

import bound from "react-bounds.js";

How to Use

The first step is to create a new boundary using react-bounds.js. To do so, call it and pass in your desired options. Each option and its default is explained in the options section below.

const Image = bound.img(); // initialize with default options

class Comp extends React.Component {
    state = {
        imageClass: ''
    };
    handleImage = (el, ratio) => {
        /*
            in onLeave event ratio is equal to 0
        */
        if(ratio){
            this.setState({ imageClass: 'animate' });
        } else {
            this.setState({ imageClass: '' });
        }
    };
    return(
        <div>
            {
                /*
                ...otherItems
                */
            }
            <Image
                className={this.state.imageClass}
                src="src"
                onEnter={this.handleImage}
                onLeave={this.handleImage}
            />
        </div>
    );
};

Now that we've covered the basics, lets delve into the options

Options

You are not required to pass any options during boundary creation. All options come with sensible defaults, shown below:

// default options
{
  root: window,       // the top-level document's viewport
  margins: {
    top: 0,
    right: 0,
    bottom: 0,
    left: 0
  },
  threshold: 0.0,
  onEmit: () => {}
}

Explanation of each option follows:

root

Accepts a DOM node.

The root is the element for which we are creating the boundary. Events will be emitted whenever a watched element enters/exits the root element.

Ex:

class Comp extends Component {
  boxRef = null;
  Circle = null;

  componentDidMount() {
    if (this.boxRef) {
      this.Circle = bound.div({ root: this.boxRef });
    }
  }

  doSomething = (el, ratio) => {};

  render() {
    const { Circle } = this;

    return (
      <div>
        <div ref={el => (this.boxRef = el)} className="box">
          {Circle && (
            <Circle onEnter={this.doSomething} onLeave={this.doSomething} />
          )}
        </div>
      </div>
    );
  }
}

margins

Accepts a mapping, where values are stated in pixels.

You can specify a top, right, bottom, or left margin to add to the root's bounding box. This affects detection, NOT style on the root element. For example:

const Container = bound.div({
  margins: {
    bottom: 100
  }
});

The above boundary will fire a callback for any watched element that gets within 100px of its bottom border.

threshold

Accepts a number between 0.0 and 1.0 or an array with number between 0.0 and 1.0.

The ratio of intersecting area required before a callback is made. A threshold of 0.0 means that if even a single pixel of a watched element enters the boundary, a callback is made. A threshold of 1.0 means that every pixel of a watched element must be inside the boundary before a callback is made.

onEmit

Accepts a function or anonymous function.

The provided callback will be executed whenever any watched element enters or exits the boundary, once all individual callbacks have executed. This is a useful option if you'd like some action to take place no matter what element enters/exits your boundary. Here is an example of how it can be used:

const Link = bound.a({
  onEmit: actions => {
    if (actions.some(action => action.inside)) {
      console.log("At least one element is inside my boundary");
    }
  }
});

As seen above, the onEmit callback will be passed an argument actions, which is an array of objects representing the actions taken directly beforehand. Each object in actions has the following detail:

{
  el, // DOM node
    inside, // boolean
    outside, // boolean
    ratio; // floating number
}

bound

the bound object can return various html element, just using bound.someHtmlElement EX:

const Circle = bound.div();
const Image = bound.img();
const Button = bound.button();
const Link = bound.a();
//etc...

The html returned come with onEnter and onLeave events in "tag", these events come with the element in first param and the ratio in second param.

Browser Support

React-Bounds.js depends on the following browser APIs:

Consequently, it supports the following natively:

  • Chrome 51+
  • Firefox 55+
  • Safari 12.1+
  • Edge 15+
  • iOS Safari 12.2+
  • Chrome for Android 51+
  • Opera - Supported
  • IE - No Support

For browsers that do not currently support IntersectionObserver, consider a popular polyfill that has great browser support.

License

MIT. © 2019 Vitor Cruz