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

vspy

v0.0.10

Published

A simple viewport spy.

Downloads

7

Readme

vspy

A simple viewport spy.

Build Status

Usage

Factory - accepts 2 parameters:

  • callback (required) - function called once for each element, right after it reaches the viewport. It is passed a reference to element as a parameter. Once it's called, the element gets marked as handled and removed from the pool.
  • options (optional) - available configuration options include:
    • offset - custom scroll offset (vertical; default: 0)
    • container - container to listen for scroll events on (default: window)

API:

  • .observe(target) - adds elements to the pool. Duplicates and previously handled elements are removed. It accepts either a CSS selector or instances of Element, NodeList and Array as a parameter.
  • .poke() - triggers targets check
  • .prune() - a target can be detached at any time, successfully preventing the onscroll callback from being deregistered. Use this method to notify the instance, that the DOM structure has changed. It accepts no parameters.
  • .reset(target) - marks target as unhandled in the context of the current spy.

Example

Simple spy:

var spy = require('vspy')(callback);

function callback(el) {
  console.log(el.nodeName + ' reached the viewport!');
}

spy.observe('.foo');

Other examples:

Installation

$ npm install vspy

Test

$ npm test

Browser support

IE9+