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

@leejaehyeok/use-intersection-observer

v0.3.0

Published

React hooks for observing element visibility using the Intersection Observer API. Supports single element and multiple elements tracking with lifecycle callbacks.

Readme

@leejaehyeok/use-intersection-observer

English | 한국어

React hooks for observing element visibility using the Intersection Observer API. Provides two hooks: useIntersectionObserver for tracking a single element and useIntersectionObserverGroup for tracking multiple elements. Perfect for lazy loading, infinite scroll, analytics tracking, and scroll-based animations.

📦 Installation

npm install @leejaehyeok/use-intersection-observer

🚀 Quick Start

Single Element Tracking

Track the visibility of a single element:

import React, { useRef } from "react";
import { useIntersectionObserver } from "@leejaehyeok/use-intersection-observer";

export function MyComponent() {
  const { setContainerRef, isVisible, hasEntered, target } = useIntersectionObserver({
    targetSelector: "[data-target]",
    onEntered: (entry) => console.log("Entered!"),
    onExited: (entry) => console.log("Exited!"),
  });

  return (
    <div ref={setContainerRef}>
      <div data-target>{isVisible ? "Visible" : "Hidden"}</div>
      <button onClick={() => target?.scrollIntoView({ behavior: "smooth" })} disabled={!target}>
        Scroll to target
      </button>
    </div>
  );
}

Multiple Elements Tracking

Track visibility of multiple elements:

import React from "react";
import { useIntersectionObserverGroup } from "@leejaehyeok/use-intersection-observer";

export function MyComponent() {
  const { setContainerRef, states } = useIntersectionObserverGroup({
    keyAttribute: "data-key",
    onEntered: (key, entry) => console.log(`Item ${key} entered`),
  });

  return (
    <div ref={setContainerRef}>
      {["item-1", "item-2", "item-3"].map((key) => (
        <div key={key} data-key={key}>
          {states[key]?.isVisible ? "In view" : "Out of view"}
        </div>
      ))}
    </div>
  );
}

🧠 Key Features

  • Single & Multiple Elements: Track one or many elements with dedicated hooks.
  • Lifecycle Callbacks: onEntered, onExited, and onChange callbacks for full control.
  • State Tracking: Know if elements are visible or have been entered.
  • Target Element Access: Get a direct reference to the observed DOM element via target.
  • Once Option: Auto-unobserve after first intersection with once: true.
  • Flexible Root: Use the viewport or a scrollable container as the intersection root.
  • Reset Control: Reset observation state programmatically with reset() method.

🔗 Links

📄 License

MIT © leejh1316