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 🙏

© 2024 – Pkg Stats / Ryan Hefner

@kaliber/use-is-in-viewport

v1.1.1

Published

Returns whether an element intersects with a parent element, using the IntersectionObserver

Downloads

11

Readme

useIsInViewport

Check whether an element is currently (or was at some time) visible inside the viewport

Motivation

Reports wether an element is visible inside the viewport using the IntersectionObserver. This is more performant and easier to use than listening to scroll and resize events and measuring the current offset using getBoundingClientRect.

Polyfill

The IntersectionObserver is supported by most current browsers. If you need wider support, there is a polyfill available through polyfill.io.

Using @kaliberjs/build, you can add the following argument to the polyfill() call.

{polyfill(['default', 'IntersectionObserver'])}

Without, you can manually add the following script to your page (or include it in your build):

https://polyfill.io/v3/polyfill.min.js?features=IntersectionObserver

Installation

yarn add @kaliber/use-is-in-viewport

Usage

function Component() {
  const { ref: isInViewportRef, isInViewport } = useIsInViewport({ rootMargin: '-10%' })
  const { ref: wasInViewportRef, wasInViewport } = useWasInViewport({ rootMargin: '-10%' })

  return (
    <div>
      <div ref={isInViewportRef}>
        {isInViewport 
          ? 'Is in viewport'  
          : 'Is not in viewport'}
      </div>

      <div ref={wasInViewportRef} >
        {wasInViewport 
          ? 'Has been in viewport' 
          : 'Has not yet been in viewport'}
      </div>
    </div>
  )
}

The useIsInViewport hook also returns wether an element has been in the viewport in the past (wasInViewport). The main difference with the dedicated useWasInViewport hook is that the IntersectionObserver doesn't get cleaned up, since the hook still has to track wether the element is currently in the viewport. This can be useful if you want to pause an expensive operation, but also want the element to have a reveal animation.

function Component() {
  const { ref: elementRef, isInViewport, wasInViewport } = useIsInViewport()

  return (
    <div>
      <div ref={elementRef} className={cx(wasInViewport && styles.isRevealed)}>
        {isInViewport ? 'Is in viewport' : 'Is not in viewport'}
      </div>
    </div>
  )
}

Disclaimer

This library is intended for internal use, we provide no support, use at your own risk. It does not import React, but expects it to be provided, which @kaliber/build can handle for you.

This library is not transpiled.