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

keywatch

v1.0.1

Published

A browser library for watching/listening to keyboard events

Downloads

29

Readme

Keywatch - keyboard events for web-apps

What is Keywatch?

Keywatch is a JavaScript browser library that provides helper functions for listening to keyboard events.

What can I do with it?

You can configure page-wide keyboard shortcuts and bind them to handler functions.

Example:

keywatch('^z', undo)

or see the DEMO.

Additionally, it also provides a vue.js mixin to handle keyboard events only while the mixing component is mounted.

Getting Started

Installation

# with npm
npm install --save keywatch
# with yarn
yarn add keywatch

Integration to any HTML Page

Assuming you can use JavaScript Modules you can use the default provided method as a single point of entry. You probably won't need the rest, but can access it nevertheless.

<script type="module">
import { watch } from 'keywatch'
watch('Control KeyS', () => {
  console.log('call save')
})
</script>

Integration with vue.js

For Integration in any vue.js component you can

import Keywatch from 'keywatch'

export default {
  mixins: [
    Keywatch.Mixin({
      'ctrl KeyD' () { this.doStuff() },
    })
  ],
  methods: {
    doStuff () {
      // ...
    }
  }
}

Defining Watchers

In order to actively watch something you have to define what keys should trigger a reaction. This can be done via very simple to rather complex configurations. Let's get to it.

Single Keys

To catch a keyboard input we have to determine either it's key or code. The naive way to do this is to type it:

watch('a', action) // will trigger on pressing key 'A' 
watch('b', action) // will trigger on pressing key 'B' 
watch('c', action) // will trigger on pressing key 'C'
// ... and so on

This is trivial for letters and numbers, but what about other keys, like Enter, Escape or Arrows?

These can be caught by using their Codes. That's especially necessary for chars like ,_#@!?, so when in doubt, stick to the codes.

watch('Enter', action)
watch('Escape', action)
watch('ArrowUp', action)
watch('ArrowDown', action)
watch('Comma', action)
// ...

Modifiers

The Keys can be further specified by selecting one or many Modifier keys of Shift, Alt, Control or Meta. The latter is also known as Command on Mac and Win on Windows, but access to these keys is somewhat restricted.

watch('Shift KeyA', action)
watch('Alt KeyS', action)
watch('Control KeyD', action)
watch('Meta KeyF', action)

These can be combined to be even more specific:

watch("Shift Alt KeyA", action) // will not trigger on Shift-A or Alt-A alone

Ignoring in Input-Fields

If you don't want to execute the shortcut while I'm actively editing an INPUT|TEXTAREA|SELECT, use the NoInput (short :) prefix.

watch('NoInput KeyD', doStuff)
watch(':d', doStuff)

Watch several keys at once

Sequences

You can combine several single watched keys to a sequence, either by providing an Array or in a single String separated by Comma ,. The full sequence has to be matched with no other key in between to trigger the action.

Example:

watch(['^w', '^s'], splitWindow)
watch(['Escape', 'Colon', 'KeyW', 'KeyQ', 'Shift Digit1', 'Enter'], saveAndExit)
watch('i,d,d,q,d', enableGodmode)

All key options

| Option | Short | Description | Example | | ------ |:-----:| ----------- | ------- | | Shift | + or ⇧ | requires the shift key to be down | +ArrowUp or ⇧KeyX | | Alt | # or ⌥ | requires the alt key to be down | #e / ⌥Enter | | Control | ^ or Ctrl | requires the Control key to be down | ^Space | | Meta / Command | @ or ⌘ | requires the Meta/Win/Command key to be down | @KeyQ or ⌘KeyL | | NoInput | : | does not trigger in INPUT or TEXTAREA or SELECT input fields | :Backspace | | NoDefault | ! | Prevents default behaviour (when applicable) if the whole sequence has been matched | !⌘F |

Handling Events

In most cases you won't care much for the event, that triggered the key sequence, but in case you do, you can access it in the

Unwatching

In order to clean up after you have used a watcher the watch function will return itself return a function, that disposes all watchers it has created.

// setUp
const unwatch = watch({
  Control_KeyS: () => this.save()
})

// tearDown
unwatch()

Alternatively you can specify a reference to which the watcher is bound on creation and unwatchAll of that reference.

import { watch, unwatchAll } from 'keywatch'

// setUp
const reference = {}
watch('^z', () => this.undo(), reference)


// tearDown
unwatchAll(reference)

Vue Mixin

When working with Vue, you can utilize the Keywatch.Mixin to specify KeySequences, which should only be watched while a component is rendered.

import Keywatch from 'keywatch'

new Vue({
  mixins: [
    Keywatch.Mixin({
      'Alt KeyS' () {
        // 'this' is the vue instance 
        this.doStuff()
      } 
    }),
  ],
  methods: {
    doStuff () {
      // work, work 
    }
  }
})

All watchers created like this will be disposed automatically during the components beforeDestroy method.

Limitations

It is restricted to your browser

Some browsers may not allow you to rebind keys, especially when you would overwrite core browser functions. Some operating systems may as well catch the keys and prevent the browser from receiving them. In these cases you'd have to use different shortcuts.

Conflicting Keys

How do I work with conflicting keys?

Troubleshooting

Function is unused (IntelliJ / WebStorm)

When defining the keys for a Vue mixin via object syntax, IntelliJ denoes the funcitons as unused. This is tecnically correct as the functions may never be used with that name. You can avoid this behaviour by using a quoted name:

  mixins: [Keywatch.Mixin({
    ArrowUp () { },
    ArrowDown () { },
  })]
  mixins: [Keywatch.Mixin({
    'ArrowUp' () { },
    'ArrowDown' () { },
  })]

F.A.Q.

What is it good for?

It emerged from several work projects where we created intranet web apps, that replaced old terminal alls. These original apps made heavy use of keyboard shortcuts, wich we wanted to do as well. The multi-key part of it came by accident when the need for a 2-key sequence came up. So here we are.

Does it work with Hot Module Replacement (HMR)?

It should. If not feel free to open an issue.

Why is it called Keywatch?

It's short, describes what's primarily done by the library and last, but not least, the npm name was available. When I stared working on it, the name was Shortcuts.

Is this all?

This README and the DEMO are a work-in-progress, but I hope to update it soon.