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

touch-pad

v1.1.0

Published

Track drags and touches on an element, a bit like a touchpad or trackpad

Downloads

10

Readme

touch-pad

Track drags and touches on an element, a bit like a touchpad or trackpad.

Demo

The best way to understand how touch-pad works is to try it. But the GIF below may give you a quick idea.

demo

Installation

npm install touch-pad

Usage

This package provides a web component and an event processor class. In both cases TouchPadMoveEvents are emitted when the user drags or touches the element. The event detail property contains an x and y property with the current position of the touch or drag relative to the top left corner of the element as a fraction of the element's width and height.

As a Web Component

import 'touch-pad/define'

The touch-pad/define module automatically registers the touch-pad custom element. You can now use it in your HTML.

<touch-pad>
  <interactive-element><interactive-element>
</touch-pad>

If you prefer to do your own registration, you can instead import { TouchPad } from 'touch-pad' to get the class.

Now you can listen for touchpadmove events on the touch-pad element (or on its ancestors).

document.querySelector('touch-pad').addEventListener('touchpadmove', (event) => {
  console.log(event.detail)
})

As a Class

import { TouchPadEventProcessor } from 'touch-pad'
const eventProcessor = new TouchPadEventProcessor(
  document.querySelector('interactive-element')
)
eventProcessor.listen()

The <interactive-element> will now emit touchpadmove events when the user drags or touches it.

document.querySelector('interactive-element').addEventListener('touchpadmove', (event) => {
  console.log(event.detail)
})

If do not want your element to emit touchpadmove events into the DOM, you can specify an EventTarget as the second argument to the constructor.

const touchMoveTarget = new EventTarget()
touchMoveTarget.addEventListener('touchpadmove', (event) => {
  console.log(event.detail)
})

const eventProcessor = new TouchPadEventProcessor(
  document.querySelector('interactive-element'),
  touchMoveTarget
)
eventProcessor.listen()

Cleanup

If the source element is removed from the DOM, you should call eventProcessor.unlisten() to stop listening for events. Failure to do so may result in memory leaks, since it adds event listeners to the element’s document. This is not necessary for the web component usage pattern where this is handled for you.