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

detect-pointer-events

v1.0.2

Published

Detect if the browser supports the pointer events api

Downloads

1,176

Readme

Detect Pointer Events

Detect if the browser supports the pointer events api.

Live detection test

Exports a reference to a singleton object (a micro state machine with an update function) with its state set to if the browser supports the pointer events api, (and if so does the api require a prefix, is it running on a touch device, and how many touch points does the device have), as well as an update() function which re-runs the tests and updates the object's state. There is also a prefix(value) function which will return the value and only add a prefix to it if it's required.

Note that detect-pointer-events is one of the micro state machines used by detect-it to determine if a device is mouseOnly, touchOnly, or hybrid.

For more information on the pointer events api, please see MDN's Pointer Events, or the W3C Pointer Events specification.

detectPointerEvents micro state machine

const detectPointerEvents = {
  hasApi: boolean,
  requiresPrefix: boolean,
  hasTouch: boolean,
  maxTouchPoints: whole number,

  // re-run all the detection tests and update state
  update() {...},

  // prefix the passed in value only if requiresPrefix === true
  prefix(value) {...},
}

Installing detect-pointer-events

$ npm install detect-pointer-events

Using detect-pointer-events

import detectPointerEvents from 'detect-pointer-events';
// using the state
detectPointerEvents.hasApi === true; // pointer events api is present in the browser
detectPointerEvents.requiresPrefix === true; // use of pointer events requires the Microsoft prefix
detectPointerEvents.hasTouch === true; // pointer events running on a touch capable device
detectPointerEvents.maxTouchPoints; // maximum number of touch points supported by the device

// updating the state - most apps won't need to use this at all
detectPointerEvents.update();

// prefixing pointer events
detectPointerEvents.prefix(value) // returns the value and only adds the prefix if requiresPrefix

// for example, this will add an event listener for 'MSPointerDown' if requiresPrefix === true,
// otherwise it will add an event listener for 'pointerdown'
element.addEventListener(detectPointerEvents.prefix('pointerdown'), function...)
/*
 * note that in the case of a browser that doesn't support pointer events,
 * including when using a legacy computer and browser, the default state will be:
 */
const detectPointerEvents = {
  hasApi: false,
  requiresPrefix: undefined,
  hasTouch: undefined,
  maxTouchPoints: undefined,
}

For reference, here is the pointer events prefix map used by the prefix() function.

Note that the update() function is run once at the time of import to set the object's initial state, and generally doesn't need to be run again. If it doesn't have access to the window, then the state will be undefined (detect-pointer-events will not throw an error), and you will have to call the update() function manually at a later time to update its state.

Part of the detect-it family