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

movver

v0.0.4

Published

The concept of hover on touch devices.

Readme

Movver.js (v0.0.4)

Introduction:

Movver exists solely to provide the concept of a hover on touch devices. It does this by keeping a log of where you're tapping to scroll and then figures out what you're most likely looking at on the remaining viewable portion of the screen. It has no dependencies, and works in all major mobile browsers. Simply attach callbacks to page elements and they'll be executed as they're being looked at.

Usage:

1. Include the library

<script src="your/path/to/movver.min.js"></script> or npm install movver or bower install movver.

2. Create a movver instance

var movver = new Movver(options);

options:

  • "debug": Colors monitored elements according to their focus threshold, and shows you where Movver things your thumb is blocking the screen. Defaults to false. See the debug screenshots section below for an image of what this looks like.
  • "touchAverage": The number of touches used to figure out an average for determining where your thumb is over the screen (1-∞). It has a sensible default, so probably best to leave alone. If you do change, I'd recommend using debug mode in conjunction to see how your changes affect behaviour.
  • "focusThreshold": The percentage amount a given element must be in focus before Movver triggers a movver event on it (0-100). Again, it has a sensible default.
  • "eventTimeout": The number of ms an element must be above the focus threshold before its movver event is triggered. Defaults to 1000ms.

3. Watch elements

movver.watch(element);

element: Can be either a vanilla Javascript DOM element or a jQuery selected DOM element.

4. Listen for a movver event

element.addEventListener('movver', function(e) {
  console.log("Movver thinks you're looking at", e.target);
});

5. Unwatch elements

movver.unwatch(element);

element: Can be either a vanilla Javascript DOM element or a jQuery selected DOM element.

Usage scenarios:

  • Pre-caching of content behind tappable page elements.
  • Lazy loading images.
  • Revealing content as it's viewed.
  • Mobile analytics (what are your users actually looking at?).

Development

  • To build the project npm run build.
  • To run the development demo server npm run server.

PR Wishlist:

  • Tablet format support, with tracking of individual thumbs.
  • Any further improvements to accuracy, usefulness at the singular task of figuring out what users might be looking at on touch devices.