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

warez

v0.1.0

Published

Detects which input devices are being used

Downloads

6

Readme

 __     __     ______     ______     ______     ______
/\ \  _ \ \   /\  __ \   /\  == \   /\  ___\   /\___  \
\ \ \/ ".\ \  \ \  __ \  \ \  __<   \ \  __\   \/_/  /__
 \ \__/".~\_\  \ \_\ \_\  \ \_\ \_\  \ \_____\   /\_____\
  \/_/   \/_/   \/_/\/_/   \/_/ /_/   \/_____/   \/_____/
==========INPUT=HARDWARE=DETECTION=FOR=JAVASCRIPT========

warez - what hardware is the user interacting with right now?

Sometimes it makes sense for a user interface to adapt to the input device being used. For example, in my app KameSame I wanted to expand the input size when the user was interacting with an Apple Pencil as opposed to the touchscreen or a physical keyboard (demo). Unfortunately, browsers don't make it easy to answer the question "what's the most recent input method that's been used?", or "what methods have been used since the page was loaded?"

This tiny package helps answer those questions with a pretty straightforward little API.

Install

$ npm i -S warez

Then const warez = require('warez') or import * as warez from 'warez' or whatever.

Usage

Monitoring input

The package offers start() and stop() functions that govern whether user interactions are being actively monitored. If you intend to track the current input device, just kick things off with:

warez.start()

And you can remove the event handlers with:

warez.stop()

Querying input device information

If you want to know the most recently used input device, you can call:

warez.currentDevice() // will be 'pen', 'keyboard', touch', or 'mouse'

And if you call:

warez.allDevices() // an array of one or more of the above input types

Be notified when the current device changes

You can also register an event handler to respond whenever the input device currently being used by the user changes:

warez.onDeviceChange(e => {
  console.log('Now using device', e.current)
  console.log('Previous device was', e.previous)

  // You might update any nodes in the DOM whose CSS styles ought to reflect
  // the current input device with something like this:
  document.querySelectorAll('[data-warez]').forEach(node => {
    node.setAttribute('data-warez', e.current)
  })
})

If you want to remove the handler, you can pass a reference to the function:

warez.removeDeviceChangeHandler(yourHandlerFunction)

Demo

Here's a little demo of the test page included in this repo: