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

izitin

v0.6.1

Published

check if elements are in viewport

Downloads

10

Readme

izitin

check if elements are in viewport

Install

With Bower

bower install izitin

With NPM

npm install izitin

Example Setup

Javascript

import Izitin from 'izitin';

// create an instance with default options
const izitin = new Izitin({
  fraction: 0, // fraction of the item that must be in viewport (0 - 1)
  fn: e => {}, // callback function for each individual item
  container: document, // the selector or dom element for the container
  items: '.izitin', // the selector for the items
  stagger: 100, // duration for stagger (in ms)
  css: true, // use css transition-delay for staggering
  remove: false, // remove class when out of viewport
  throttle: 0 // throttle the event listener (in ms)
  detectUp: true // reverse item order if scrolled up
});

The callback function fn receives an object with the following content:

{
  index: // the index of the items
  direction: // the scroll direction
  target: // the DOM element
  izitin: // boolean, true if in viewport
  position: // where in relation to the viewport is the element
  rect: // the bounding client rect of the DOM element
}

You can also trigger a check manually, might be useful for ajax websites:

izitin.check();

Or you can reset the classes on all items:

izitin.reset();

If you don't need it anymore, you can dispose of it properly:

izitin.destroy();
delete izitin;

CSS

Izitin adds the following classes to items:

.itizin {} /* the item is in the viewport */
.izitin-above {} /* the item is above the viewport */
.izitin-below {} /* the item is below the viewport */
.izitin-left {} /* the item is left of the viewport */
.izitin-right {} /* the item is right of the viewport */

HTML

You can add custom values for staggering individual elements:

<div class="izitin" data-izitin-stagger="200"></div>

License

MIT License