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

unityinput

v0.0.30

Published

[![npm version](https://badge.fury.io/js/unityinput.svg)](http://badge.fury.io/js/unityinput) [![Build Status](https://travis-ci.org/digijin/inputjs.svg?branch=master)](https://travis-ci.org/digijin/inputjs) [![Coverage Status](https://coveralls.io/repos/

Downloads

46

Readme

UnityInput

npm version Build Status Coverage Status Code Climate Scrutinizer Code Quality

Intro

This class is heavily inspired by Unity editor's Input class. methods in this class can be used the same way but with a more traditional js nomenclature starting with a lowercase character for function names.

This is intended to be used for gaming. If you're trying to use it for standard web stuff, this might not be the package for you.

Usage of the getKey and getButton functions can be used with no additional setup, but to use the activity functions like getButtonDown and getButtonUp one must invoke the endTick function at the end of each frame loop to flush the internal caches and begin taking in new events.

mouse attaches itself to document, for testing make calls to document

for button configs that include both gamepad and keyboard/mouse, the package returns values relevant to the last device that registered an interaction. So if you define a button or axis to both keyboard/mouse and gamepad, if you use your gamepad the package will return the state of the gamepad and then when it detects input from keyboard or mouse it will swap to keyboard/mouse controls until it hears another event from the gamepad.

This is so the end user can seamlessly swap between gamepad and keyboard/mouse. The user case of a player using a gamepad and keyboard/mouse simultaneously is not covered by this package.

installation

yarn add unityinput

configuration

Please see src/defaults.js. These are the defaults loaded if the package is not given a config object. It shows all the possible options.

basic usage

import Input from "unityinput";

let input = new Input({
	keyboardMapping: {
		ctrl: 17
	},
	buttons: {
		fire: {
			type: "keyboard",
			key: "ctrl"
		}
	}
});

let gameloop = () => {
	if (input.getButton("fire")) {
		console.log("pew pew pew");
	}
	input.endTick();
};

setInterval(gameloop, 100);

checking if a button is currently down

let input = new Input({
	keyboardMapping: {
		ctrl: 17
	},
	buttons: {
		fire: {
			type: "keyboard",
			key: "ctrl"
		}
	}
});

let gameloop = () => {
	if (input.getButton("fire")) {
		console.log("pew pew pew");
	}
	input.endTick();
};

checking if a key is pressed in the last frame

let input = new Input({
	keyboardMapping: {
		ctrl: 17
	}
});

let gameloop = () => {
	if (input.getKeyDown("ctrl")) {
		console.log("pew pew pew");
	}
	input.endTick();
};

Notes

getButtonDown is currently not supporting gamepad.

Dev

Test are written in both jest and karma/jasmine/webpack

One-off tests

yarn test
yarn karma

Watchers

yarn test:watch
yarn karma:watch

Webpack dev server

yarn dev

and then hit up http://localhost:8080/demo/ in your browser. Coverage outputted to console and /coverage/html

Docs

docs can be generated by cloning the repo and running

npm install
npm run docs