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

viewport-trigger

v2.0.2

Published

Perfomant, light library in pure JS to trigger callback when elements exit or leave viewport, using IntersectionObserver API

Downloads

17

Readme

viewport-trigger

Perfomant, light library in pure JS to trigger callback when elements enter or leave viewport, using IntersectionObserver API

Motivation

There are a lot of libraries which give you opportunity to trigger some actions when element enters and/or leaves viewport, but they use scroll's listeners and getBoundingClientRect calculations, which is not so efficient, because it force browser to synchronously calculate the style and layout (link). IntersectionObserver API lets you know when observed element enters or leaves the browser’s viewport in more efficient way. It was introduced in Chrome 51, and now it's native for Firefox and Opera too.

Install

# npm
npm i -S viewport-trigger 

# yarn
yarn add viewport-trigger

With module bundlers just use

// ES6
import ViewportTrigger from 'viewport-trigger';

// CommonJS
const ViewportTrigger = require('viewport-trigger');

Or include minified script before your scripts in body tag

<script type="text/javascript" src="/path/to/viewport-trigger.min.js"></script>

Usage

First of all, you need an observer with default options

// create observer
const vt = new ViewportTrigger();

or with custom options (you can read about rootMargin on MDN)

// create observer with custom options
const vt = new ViewportTrigger({
  rootMargin: '100px 0 100px 0'
});

Then add target to observe and events to trigger. ViewportTrigger handles two events: enter (target enters viewport) and leave (target leaves viewport)

// add DOM element as target
const target = document.getElementById('target');
vt.observe(target);

// add events handlers
vt
  .on('enter', target, () => {
    console.log('target entered viewport');
   })
  .on('leave', target, () => {
    console.log('target left viewport');
  });

Browser support

IntersectionObserver API is available in the latest browsers. Use polyfill to support others.