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

@gamebucket/input

v0.0.2

Published

Input handling for games and interactive apps

Readme

@gamebucket/input

Input handling for games and interactive apps.

Note: this is a work in progress! The API is likely to have breaking changes between versions. Please give it a try and leave a GitHub issue if you find something that needs work.

Getting Started

Install

npm install @gamebucket/input

Usage

import { Input, keys, gamepad } from '@gamebucket/input'

// Create the input manager and pass in the mapping, which is an array of 2-
// tuples that map inputs to app-specific intents. You can change the mapping
// at any time by assigning to input.mapping, but TypeScript can infer the
// list of valid intents from what you pass in here.
const input = new Input([
    [Input.keys.Space, 'Jump'],
    [[Input.keys.ArrowUp, Input.keys.ArrowDown], 'WalkY'],
    [[Input.keys.ArrowLeft, Input.keys.ArrowRight], 'WalkX'],
    [Input.gamepad.standard.buttons.RightBottom, 'Jump'],
    [Input.gamepad.standard.axes.LeftStickX, 'WalkX'],
    [Input.gamepad.standard.axes.LeftStickY, 'WalkY'],
])

// Attach event listeners to the given element, typically a canvas. The element
// is mostly relevant to pointer events, as keyboard and gamepad inputs will be
// captured regardless of what element has focus.
input.attach(document.getElementsByTagName('canvas')[0])

// In your update loop:
requestAnimationFrame(loop)
function loop(t) {
    requestAnimationFrame(loop)

    // Poll devices and handle events received since the last call to readDevices()
    input.readDevices()

    // jump will be true if the player pressed the space bar or the "A" button
    // since the last call to readDevices()
    let jump = input.recentlyActivated('Jump')

    // jumpDuration will be the length of time the player has been holding
    // "Jump" if it is at least 30 milliseconds, otherwise 0.
    let jumpDuration = input.heldDuration('Jump', t, 30)

    // dx will be the value of the "WalkX" axis, normalized to the range [-1,1].
    let dx = input.getValue('WalkX')

    // The same APIs can be used for axes and buttons
    if (input.heldDuration('WalkX', t, 10_000)) {
        console.log('Time to take a break')
    }

    // Mouse inputs are current directly attached to the input object. They are
    // updated on each call to readDevices()
    scroll += input.mouseWheelDelta.y
}

Compatibility

The library uses PointerEvents and the code property of KeyboardEvent, so it should work fully on most desktop browsers since 2020; mobile support is iffy.

License

Mozilla Public License 2.0